Capabilities / Start here

How Unity Intelligence works

Connect data, build native and HTML reports, use report-wide context, and share the result.

X4 Tech SolutionsUpdated September 10, 20264 min read
  1. Your dataDatabases · CSVs · Public data
  2. Data modelEntities, relationships, measures
  3. AI + contextReport, model, instructions, files
  4. Query + verifyExecution and rendered previews
  5. Editable reportsNative and HTML pages

Unity Intelligence turns questions about your data into reports you can use and keep editing. Connect a database or import a CSV, describe the result you want, and let the assistant query the data, build pages, inspect the result, and refine it.

A report can combine native charts and tables with complete HTML pages. One report conversation can work across both, using the data model, report instructions, reference files, and the pages already in the report.

Build your first report

  1. From Reports, click Create New Report, enter a name, and click Create Report.
  2. Add a database connection or import a CSV. Open Data to review its model.
  3. Open Data Chat and describe the question, audience, and output.
  4. Follow the assistant's activity as it inspects the model, runs queries, and saves pages and visuals.
  5. Review the page, inspect its SQL, and ask for a specific refinement.
  6. Open Manage Access when you are ready to share it.

Try this prompt after connecting your data:

Example prompt
Inspect the data model and the current report. Build an HTML overview
page for our operations team with key metrics, a monthly trend,
a category breakdown, and a searchable detail table.

Use the model's existing metric definitions. Explain any assumptions.
Render the page, inspect the result, and fix issues before finishing.

The assistant resolves actual entities and columns from your model. An example prompt does not create a missing business definition or source field.

Understand the pieces

ObjectPurpose
ConnectionAuthenticates a data source and makes it available to authorized reports.
Semantic modelDescribes queryable entities, fields, relationships, and reusable calculations.
ReportHolds pages, attached connections, instructions, reference files, conversations, and access settings.
Report pageA native canvas with positioned charts, cards, tables, text, and shapes.
HTML pageA custom HTML layout containing registered live visuals, datasets, and browser code.
ConversationA named thread of questions, tool activity, answers, and build requests within a report.
Organization and teamManage membership, company report ownership, and explicit team access.

An active organization owns newly created reports, but each report stays private until shared. Existing personal reports keep their ownership when you join an organization. See Organizations.

Follow the build loop

The assistant gathers context, chooses operations, reads their results, and continues until it can complete the request or explain what remains unresolved. A request can create an entire page through several queries and saves.

For HTML, the loop includes the real page renderer: save source and registrations, check execution, capture a browser preview, inspect the image, and repair problems. It can also test individual controls. A successful save alone does not establish that a page renders correctly or answers the business question.

Read the report-building quickstart for a complete example.

Supply the right context

You want to providePut it here
Reusable metric or derived fieldSemantic model
Report terminology and analytical conventionsReport instructions
A brand guide, report template, workbook, PDF, or imageReport files
The task and the intended scope of this changeData Chat
A particular set of visuals to changeSelect them and name the change in your message.

Files are available across conversations in the same report. The assistant retrieves relevant sections and previews when needed; it does not automatically load every document in full.

Keep control of the result

Saved visuals retain their queries and field mappings. Native objects have direct layout and appearance controls. HTML pages expose their layout, visual HTML, CSS, JavaScript, and datasets. You can change either through chat or the relevant editor.

Filters make reports interactive. History records supported changes. Background work can continue while you navigate elsewhere.

Unity queries connected sources when data is requested. Results may be cached, and historical chat answers retain the data from their original run. Refreshing a report is different from refreshing an old answer.

Continue building

Start with HTML pages for custom report layouts, native visuals for canvas controls, or sharing and access for collaboration. Developers can use the API quickstart and the complete agent tool reference.

Demonstrations

See these capabilities in a recorded product workflow.

  1. Dashboard creation and SQL inspection · recorded walkthrough

Questions about your environment? Contact us.