Build an entire report page with chat

Ask Unity to build a complete report page from your data model and reference material. The assistant can discover the data, create queries, save individual visuals, compose a native or HTML page, and inspect the result through a sequence of tool calls.

This quickstart builds an HTML operations report. The same conversation can also create and refine native report pages.

Before you begin

Open a report with editing access and attach a usable data connection. Review the model so important entities and metrics have clear meanings.

If you have a reference report, brand guide, or example layout, add it to Report files. Put lasting analytical conventions in Report instructions.

Describe the complete result

Open Data Chat and send a request that names the audience, data scope, page structure, and review expectations.

Build a new HTML page named Operations Overview for our weekly review.

First inspect the entire report, the active connection's model, existing
metric definitions, and the reference report in the file library.

Include:
- A headline summary of the period and key changes.
- Live KPI visuals using the existing model measures.
- A monthly trend and a category comparison.
- A searchable, sortable detail table with record-level selection.
- Clear labels, units, empty states, and a responsive layout.

Use the reference report's design and original logo. Keep each live
component separately registered. Preserve the existing pages.
Render and inspect the page, test relevant controls, and repair problems.
Finish by identifying the page, sources, assumptions, and anything
you could not verify.

Replace the requested sections with what your audience needs. The assistant should discover actual fields and definitions instead of inventing a matching schema.

Follow the agentic build loop

The loop can continue without you approving every routine step. It is bounded: an unresolved failure can produce an incomplete result with an explanation instead of unlimited retries.

A saved page, a page that executes, an attractive layout, and a correct business answer are separate things to review.

Inspect the saved page

Open the created page under HTML Pages. Each live KPI, chart, narrative, and table should have its own registered visual identity.

Use Source to inspect layout and visual code. Select a visual and open Adjust to inspect its dataset SQL. Use Data for the selected data context and inspect effective filters before comparing totals.

For a long report, review the lower sections as well as the first viewport. For a detail table, check search, sorting, additional rows, and record selection. An isolated preview cannot prove every interaction in the live host workspace.

Refine the result

Give a narrow follow-up when you want to preserve the working analysis:

On Operations Overview, make the KPI row more compact and improve the
trend chart's labels. Keep all queries, measures, bindings, and filters.
Preview both the top section and the detail table after the change.

For an analytical change, name its meaning:

Use completed months only for the comparison. Inspect the existing
date convention and update the calculation and labels together.
Explain which visuals changed.

The assistant can edit the existing source and visual registrations. It does not need to replace the whole report to change one component.

Build a native report page

Use a native page when you want Unity's canvas and standard visual controls:

Create a native report page named Sales Detail with a revenue card,
a monthly line chart, a region bar chart, and a detail table.
Use the existing model definitions and fit the objects inside the page.

Native objects can be moved, resized, and adjusted directly. You can mix native and HTML pages within the same report and continue using the same conversation.

Recover from partial completion

A multi-step build is not one report-wide transaction. Earlier saves can remain if a later operation fails or you stop the run.

Read the activity, inspect the current page, and ask the assistant to continue from what is saved. Use Change history for supported restoration.

Share the result

Use Preview page to review presentation and Manage Access to share the report with individuals or teams. Consider Page visibility for pages that should remain available only to editors.

Continue with HTML pages for source and history controls, or HTML visuals and data for the renderer contract and working code examples.