Create and adjust native data visuals

A native data visual is a saved analytical object on a report canvas. It retains its visual query (the report fields it groups and shows, by field ID), its presentation, position, and size, so you can inspect it and edit its presentation after an agent creates it.

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

Create a native visual

1. Select a native page under Report Pages.
2. Confirm that the required queries and definitions are saved in the report model.
3. Ask Data Chat (or any agent connected over MCP) to create the object, or drag a table from the Data panel onto the page for a table of its columns; the toolbar adds a rectangle or a text box.
4. Describe the calculation, grouping, and intended display.
5. Inspect the result, its query and generated 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

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

Bar, line, pie, and scatter are presets of one saved declarative chart kind. Changing its marks or adding a reference line can update that same object. Native tables and matrices also support cell formatting, conditional icons, badges, data bars, color scales, and sparklines through their supported properties. These effects format returned values; SQL owns business calculations.

Understand the saved definition

A visual holds no SQL of its own. Anything beyond grouping, aggregating, filtering, sorting and Top N (a ratio, a running total, a share, a year-over-year comparison, a ranking) lives in the report model as a measure, a typed measure, a calculated field or a calculated table, so it is visible and reusable. Clicking a value filters other visuals by the fields the visual's query groups by.

A visual saved as SQL before visual queries shows "This visual was saved as SQL, which visuals no longer use; rebuild it." The assistant can still read its old SQL; ask it to rebuild the visual on the model.

A matrix query supplies every hierarchy level, including its grand total. The renderer does not calculate a parent average or distinct count by combining visible children. A hierarchy can have any number of rows, down to every customer or order: Unity keeps the complete result on the server, and expanding, sorting and paging read only the rows on screen. Tables also use server result windows; see Query processing.

Adjust a visual manually

Select the visual and open Adjust. Edit its title and supported presentation properties. For a chart, card or matrix, Fields reads its query in plain language, with the table and field names the Data panel shows: what it is grouped by, its values (such as Sum of Orders › Amount), how it is sorted and its Top N. A table's columns are its fields, so a table has no Fields section. Fields are read-only here; ask the assistant to change them. A chart's Chart specification is its own section, collapsed until you open it.

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. Change the visual's query or the model's 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 its query, filters and fields.

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 query's outputs, 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. A click filters by the visual's group values; 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

Use Query inspection and Version history to investigate and recover.