Create and adjust native data visuals

A native data visual is a saved analytical object on a report canvas. It retains its query, source connection, field mappings, presentation, position, and size, so you can inspect and edit it after the assistant creates it.

Unity also supports custom HTML visuals. Their source and runtime are covered in HTML visuals and data.

Create a native visual

Select a native page under Report Pages.
Choose the intended connection and confirm the model is available.
Use a visual button in the toolbar or ask Data Chat to create the object.
Describe the calculation, grouping, and intended display.
Inspect the result, SQL, labels, and filters.

Create a monthly revenue line chart on the current native page.
Use the model's existing revenue definition, show calendar months
in order, and label the currency and date coverage.

The result is a saved report object, not only an image in a conversation.

Choose a visual

Type	Typical use
Line graph	Trends over an ordered category or time field.
Bar graph / Bar chart	Comparisons across categories using their supported layouts and properties.
Pie chart	A category's contribution to a whole.
Scatter plot	Relationships between numeric fields.
Data card	A summary measure.
Table	Multiple fields and detail records.
Declarative chart	A structured chart specification for supported advanced representations.
Text box	Explanatory content without a data query.
Rectangle or shape	Backgrounds, grouping, and canvas structure.

Not every type exposes the same property controls. The assistant can inspect a type's supported authoring properties before changing it.

Understand the saved definition

Part	What it controls
Connection	Where the query executes.
Authored SQL	The calculation and its row grain.
Output contract	Returned columns mapped to category, value, time, series, or other supported roles.
Filters	Effective visual, page, report, and runtime context.
Appearance	Titles, labels, axes, colors, legends, and value formatting supported by the type.
Layout	Page, position, dimensions, and stacking order.
Revision	Current saved identity/state used for inspection and checked edits.

Valid SQL alone is insufficient. The result must have the columns and types required by the visual's output contract.

Adjust a visual manually

Select the visual and open Adjust. Edit the supported presentation properties or inspect, copy, and change its query.

You can move and resize native objects directly on the canvas. Keep them inside the page bounds and review overlap, readable labels, and text wrapping.

Use appearance controls for a presentation change. Use SQL and model definitions when the analytical calculation should change.

Refine through chat

For the selected chart, improve the title and axis labels and show
currency without fractional digits. Keep the existing SQL, filter scope,
and field mappings.

The assistant should inspect the current saved visual and update that object. A style-only change can preserve the existing query result.

You can select multiple visuals for a common change. Their identities accompany the submitted request, and the assistant can also inspect other pages when the task requires it.

Change the representation

A different chart type may require different columns, roles, or specification. Ask the assistant to preserve the analytical meaning while changing the representation.

Replace the selected category chart with a table of the same categories
and measures. Preserve the connection and effective filters, and verify
that the returned fields are mapped correctly.

Review the new output contract, labels, and grain. A visually plausible replacement can still answer a different question if its aggregation changed.

Explore detail records

Tables and bound chart marks can participate in cross-filtering. Record-level selection needs complete source-key lineage; a non-unique displayed value does not necessarily identify a single row.

Inspect Data and the filter indicators to understand the selected context. Clear a temporary selection to return to the saved baseline.

See Filters and interactions.

Distinguish inline previews and saved objects

A chart shown inside a conversation belongs to a message unless it has been explicitly saved to a page. The assistant can revise an inline preview in place without overwriting a canvas visual.

Name the saved page/visual or the relevant chat preview when asking for a follow-up.

Troubleshoot a visual

Problem	Check
No rows	Query result, effective filters, source availability, and date range.
Wrong labels or series	Output mappings and current SQL aliases.
Misleading total	Query grain, join duplication, row limits, and model measure.
Clipped or overlapping objects	Page dimensions, position, and size.
Edit conflict	Current revision and intervening manual or assistant changes.
Missing customization control	The selected visual type's supported properties, or whether an HTML visual better fits the request.

Use Query inspection and Change history to investigate and recover.