Conversion builds a custom visual from a chart that already exists. The new tile keeps the chart's fields, and the assistant starts from its configuration and, when the app can capture one, a picture of how the chart renders today. Use it when one of the built-in visuals almost fits and you would rather continue from what you see than start from an empty tile.
The source chart is not changed or replaced; it stays where it was. The confirmation is headed Custom visual created, with the description "A sibling tile with the same fields was added and its studio is open. The AI thread starts with the captured screenshot and the chart configuration."
| Role | What it holds in the new tile |
|---|---|
| Category | Grouping dimension(s) of the source chart |
| Series | Legend / split dimension of the source chart |
| Value | Measures plotted by the source chart |
| Tooltip | Extra measures shown on hover |
A field that appeared in more than one place is kept once, and a measure found among the chart's columns counts as a measure. Each role takes the fields found for it, up to eight.
A refused conversion shows a warning headed Cannot convert this tile, with one of these reasons:
| Reason | What it applies to |
|---|---|
This tile is already a custom visual. | A tile that is already a custom visual. |
Slicers cannot be converted into a custom visual. | A slicer. |
Containers cannot be converted into a custom visual. | A container. |
Filter-canvas tiles cannot be converted. | A tile placed in the filter canvas. |
The preview tile cannot be converted. | The preview tile. |
The Convert to custom visual item is not shown when the report is not in edit mode, when you do not hold the DataPrism Custom Visual Author permission, or on a tile that is already a custom visual. See Who can do what in DataPrism.
No. The app adds a new sibling tile and leaves the source chart as it was. Remove the new tile like any other tile if you do not want it.
On the same page as the source chart, added as its sibling, and it is selected when it is added. Its title is the source chart's title with (custom) added at the end, or Custom visual when the source has no title.
Yes. Native chart tiles can be converted, including tables and matrices, and their grouping and measure fields become the four roles in the same way. Slicers, containers, filter-canvas tiles and the preview tile are refused.
Grouping and axis fields become Category; legend and split fields become Series; plotted measures become Value; measures shown on hover become Tooltip. A field that appeared twice is kept once, and each role takes the fields found for it, up to eight. The roles and their bindings appear in the tile's Data well.
The chart's type and title, a prompt to reproduce the chart and then improve it, and a block with its fields and configuration; a small JPEG of the tile is attached when the capture worked. From there it is the normal assistant flow, described in Author a custom visual with AI.
Nothing about the conversion: the new tile is still created, and the thread starts from the configuration alone. Its first message says "The source tile could not be captured, so work from the configuration below."
You need edit access to the report and the DataPrism Custom Visual Author permission, and the report must be in edit mode. On a tile that is already a custom visual, use Edit code instead. See Who can do what in DataPrism.
No. Convert while the report is open in edit mode, and the new tile joins the report right away. Save the report to write the change into a version other people can open.
Yes. After conversion the tile is a custom visual like any other: copy it onto another page or report, and add it to your organisation's visual library. See Copy and share custom visuals and Custom visuals and the visual library.