You can reuse a custom visual without rebuilding it. Copy the tile to another page or report, or export it as a . file and import it into the visual library as a new draft.
A copy carries the visual's definition, the fields bound to it and the names of its asset files. When you paste onto the page the tile came from, the copy is nudged slightly, so it does not sit exactly on top of the original.
When you paste into a different report, the visual's asset files are copied too, and the paste reports the result, counting the files copied, already present and missing at the source. If the files cannot be copied, it reads Assets not copied and explains: "The visual was pasted, but its assets could not be copied from the source report."
A few refusals to know:
A . file carries one version of a library visual, with an integrity check built in. Export it from the library and import it as a new draft.
sankey-flow-q3-v2., and a confirmation shows the exported file's name, for example Exported sankey-flow-q3-v2..Imported "<name>" as a draft. Review it and publish it like any other library visual, as described in Visual library.visual. and visual., plus visual. for an HTML + JS visual.options., with the visual's options schema.definition., with the visual's definition.sample., with the sample rows stored for previews, when the version has them.An import that does not pass its checks reports Import failed and the reason:
The file is not valid JSON. The file is damaged, or it is not a . bundle.Unsupported . The file was written by a different format version.The bundle has no readable visual definition.The sample rows are malformed.The bundle carries no integrity block.Integrity check failed for visual. (or another file), and Integrity check failed for the bundle manifest. Something inside the bundle changed after export.A bundle that fails its checks cannot be imported. Export the version again from the library and use that file.
No. The commands work on custom visual tiles only. On any other tile, Copy visual answers Not a custom visual with "Copy visual works on custom visual tiles only."
On the page you paste onto. If the tile you copied lives on that same page, the copy is nudged slightly so it does not sit exactly on top of the original.
Yes. A copy can be pasted onto any page of this report or another one. When the target is a different report, the visual's asset files are copied too, and the paste reports how many were copied, already present and missing at the source. If they cannot be copied, it reads Assets not copied and explains that the visual was pasted, but its assets could not be copied from the source report.
Your browser did not allow a write to the system clipboard, so the copy was kept in this tab's memory instead. The message "The system clipboard is unavailable; paste works in this tab only." says the rest: paste in this tab, because another tab will not have the copy.
There is nothing to paste: no custom visual copy is on the clipboard or remembered in this tab. Copy a custom visual tile first, then paste.
A single file that holds one version of a library visual: its code files, its options schema, its definition, the sample rows and an integrity block. Export it from the library; importing it adds the visual to the library as a new draft.
Yes. Export it from the visual in the library and send the file. The person who receives it needs the Author DataPrism Custom Visuals permission; they click Import on the Visuals tab, and the visual arrives as a new draft.
The file did not pass its checks, and the app reports Import failed with the reason. It may not be valid JSON, its format version may be unsupported, it may have no readable definition, its sample rows may be malformed, or its integrity block may be missing or failing because the file was edited or damaged after export. A file larger than 8 MB is refused with Bundle too large. Use a file exported fresh from the library.
No. Every file in the bundle carries a checksum, and so does the bundle itself, and import verifies them all. A hand edit makes the import fail with an integrity check error. Edit the visual in the Studio instead, then export a new bundle.
In the visual library, as a new draft. It appears on a report only when someone inserts it from the library. Review the draft, then publish it like any other library visual. See Visual library.