How the assistant understands your data and report
Use the model, entire report, selected visuals, instructions, files, and execution feedback in one conversation.
Unity's assistant works with the current report and its data model. It can discover pages and visuals throughout that report, inspect their saved definitions, read relevant reference files, and use the conversation to understand the next change.
The active page and selected visuals provide focus. They do not turn the assistant into a separate page-only or visual-only product.
Give the assistant a clear starting point
- Open the report and select the intended connection or page.
- Review the connection's model and save any missing definitions.
- Add lasting conventions in Instructions.
- Attach relevant files or choose them from Report files.
- Select particular visuals when you want to focus an edit.
- State the task, intended scope, and what a successful result should show.
Inspect the entire report and the sales model. Use the report's brand
guide as the design reference. Create a new HTML executive summary,
reusing the existing revenue definition and the report's saved filters.
Keep the existing pages intact.
What the assistant can use
| Context | How it is used |
|---|---|
| Current connection and model | Discover entities, exact fields, relationships, data types, definitions, and lineage. |
| Report catalogue | Find native and HTML pages, visuals, datasets, and attached connections. |
| Detailed object inspection | Read current SQL, mappings, source, properties, filters, and revisions before editing. |
| Report instructions | Apply persistent report-level terminology and conventions. |
| Conversation | Understand your request, earlier decisions, tool results, and follow-up intent. |
| Current selection | Identify one or several user-selected visuals and the active page at submission time. |
| Report reference files | Discover files across the report, then inspect relevant text, sheets, slides, images, or previews. |
| Execution and browser feedback | Diagnose query errors, missing bindings, renderer failures, and visible HTML layout issues. |
The assistant retrieves detailed information through tools. A large report or model can require several paginated searches; the entire database and every source file are not permanently loaded into one prompt.
Work across the whole report
InspectReport can discover both native and HTML pages. The assistant can find a chart on another page, reuse a model definition, and apply changes to an explicit set of targets.
For native visuals it inspects saved visual properties and SQL. For HTML visuals it inspects page registrations, datasets, HTML, CSS, and JavaScript. The same conversation can use both sets of operations.
Find every visual that uses the revenue definition. List the affected
pages, then update their displayed currency formatting consistently.
Include both native and HTML visuals.
A report-wide request is bounded by the report and permissions available to the caller. Organization membership does not give the assistant access to every company report.
Use selections and follow-ups
Selecting multiple visuals sends a set of targets with the message. Name the intended change, such as “Update the titles of these three visuals.” Selection alone is not an instruction to edit.
The submission captures the selection then in effect. Clicking another object while a background run is working does not retarget the already submitted request.
A follow-up can refer to the objects created in the previous answer. Be explicit when changing focus: “Now apply the same style to the selected table on Details.”
An inline chart in chat has a conversation/message identity, distinct from a saved report visual. The assistant can inspect and revise that preview in place without automatically creating a canvas object.
Use files across conversations
Files attached in one conversation remain in the same report's library. Another conversation can discover them without another upload. Attach a file to the current message when you want to identify it directly.
Find the quarterly-report template in this report's files. Inspect its
layout and preview the relevant pages. Use its typography and spacing
for the current HTML page, with our live data in place of sample numbers.
The assistant can read excerpts, search text, preview pages, and reuse original embedded images. See Reference files.
Keep context reliable
The assistant should inspect current state before editing. It can retrieve more context during a long task, but that does not guarantee perfect recall of every older message.
Put durable rules in report instructions or model definitions. Use stable page names, exact visual identities, and specific file references for work that may continue later.
Conflicting definitions, ambiguous business terms, unavailable files, and permission restrictions can require clarification. A missing source field cannot be supplied by context alone.
Respect access boundaries
Queries, file reads, report inspection, and mutations use the caller's permissions. Hidden pages are excluded from viewer-visible report content, and sensitive history access can be restricted when a report contains invisible pages.
Page visibility explains those boundaries. Data and AI explains which information is stored and sent through the AI workflow.
Questions about your environment? Contact us.