Make changes across a report — Unity Intelligence

Ask the assistant to inspect and update an explicit set of pages or visuals throughout a report. One conversation can work across native canvases and HTML pages, including content on pages you are not currently viewing.

The report catalogue establishes available targets. Your request determines which of them should change.

Make a change across pages

Identify the report and the pages or visual set you want to update.
Describe the specific presentation, calculation, filter, or structural change.
Ask the assistant to inspect current definitions before editing.
Follow the saved operations in the activity.
Review every affected page, including HTML previews where relevant.

Inspect Overview, Trends, and Customer Detail. Standardize date labels
and currency formatting across their native and HTML visuals.
Keep calculations, filters, and page structure unchanged.
List every affected visual and preview the changed HTML sections.

For a selected set, select the visuals first and explicitly ask the assistant to include all of them.

Choose the kind of change

Change	What the assistant needs to inspect
Presentation	Titles, labels, formats, colors, native properties, or HTML/CSS.
Layout	Native page bounds and object positions, or HTML composition and responsive styles.
Analysis	Source connection, SQL, grain, model definitions, and output bindings.
Filter scope	Field identity, relationships, and visual/page/report or HTML registration scope.
Page structure	Which pages to create, duplicate, rename, or remove.
Template adoption	Reference file source, previews, original assets, and current live registrations.

Changing a font and changing the definition of revenue have different consequences. State the analytical meaning when the change affects values.

Inspect before applying

The assistant can search the current report and inspect particular objects in detail. Large reports can require multiple catalogue pages.

Targets should be resolved by identity and page membership, not just the first matching title. Two pages can each contain a chart called “Revenue.”

Find all visuals that use the existing revenue definition. Show which
pages contain them and inspect their current queries and bindings.
Apply the new display format to that complete set.

The active page provides focus without preventing inspection of other authorized pages.

Preserve data while changing design

For a reference-driven redesign, specify whether the change should affect presentation alone.

Apply the report's uploaded template to the two existing HTML pages.
Reuse its original logo and inspect its CSS and preview. Preserve
dataset SQL, registered visual identities, saved filters, and interactions.
Compare the changed pages with the reference at matching viewport sizes.

Source patches can preserve unrelated HTML. Native appearance updates can preserve SQL. Replacing a visual type may require different field mappings and should be reviewed as a representation change.

Understand save boundaries

A report-wide task produces multiple operations. Each can have a result, revision check, and history entry.

The whole task is not one transaction. Earlier saves remain if a later query, visual, or preview fails. A conflict means the target changed since inspection and needs a fresh look.

This matters when another conversation or collaborator edits the same report. Give concurrent work distinct targets where practical.

Review at the same scope

Use the operation receipts to identify what changed. Check every affected page rather than only the page open when the request started.

For analysis changes, compare SQL, grain, bindings, and effective filters. For HTML, inspect the rendered result and relevant controls. For native layouts, check page bounds, overlap, clipping, and readable labels.

If only part of the set was completed, ask the assistant to continue from the saved state. Use Change history for supported undo and Background work for execution and cancellation.