How to write good requests for Hubviz AI

This page gathers ready-made requests for the Hubviz Studio AI assistant and explains what to put in them so the answer comes out right. The examples use the Sales Results 2026 project, with the Sales cube (fields date, unit, revenue, cost, target and the calculated gross profit) and the Executive view dashboard.

Suggestions on the home screen

With an empty conversation, the assistant shows How can I help with this project? and four suggestions. Clicking a suggestion sends the request in whichever mode is selected, so switch the mode first if you need to.

Suggestion	Best mode	Note
Create a complete sales dashboard	Planning	It is a big request. The plan lets you review before it creates anything.
Explain this project's cubes	Question	Only reads the project.
Build a regional analysis	Agent	Only works if the cube has a region field (or a similar category).
Suggest charts to track performance	Question	Good for finding ideas before you ask it to create.

What to include in the request

The assistant works with the project objects: cube, fields, measures, charts and dashboards. The more the request speaks the language of those objects, the better.

Include	Why	Example
The cube, measure or dashboard by name	The assistant reuses what exists. The exact name avoids creating a copy.	“Use the Revenue measure from the Sales cube.”
The number you want to see	Sets the measure and the calculation (sum, average, count, maximum, minimum).	“Sum of revenue”, “average ticket”.
How to break the number down	“By unit” or “by seller” becomes a grouping field in the measure and drill-down on the chart.	“Revenue by unit, with drill-down.”
The chart type	Without a type, it picks one. Types: columns, stacked columns, lines, stacked lines, area, card, pie, donut, funnel, horizontal bars, table and data table.	“As stacked columns.”
Where to put it	Dashboard, tab and view. You can also ask for a folder for the chart in the chart list.	“On the Executive view dashboard, in the Details tab.”
The value format	Currency, number, number without decimals, percentage or hours.	“Show it as a percentage.”
A fixed restriction, if any	Becomes a filter inside the measure.	“A measure with the Retail unit only.”

Examples by task

Task	Mode	Request
Complete dashboard	Planning	“Build a dashboard of targets by unit, with actual against target, revenue by month and the ranking of the units.”
Understand the project	Question	“Explain what each cube in this project holds and which measures exist.”
Check a number	Question	“Show the total of the Revenue measure and tell me which fields it uses.”
Calculated field	Agent	“In the Sales cube, create the calculated field Result over target: revenue minus target.”
Measure	Agent	“Create an average cost measure by month: average of the cost field, by date, broken down by unit.”
Measure with a filter	Agent	“Create a Retail revenue measure: sum of revenue for the Retail unit only.”
Simple chart	Agent	“Create a column chart with revenue by month, with drill-down by unit.”
Math between measures	Agent	“Create a line chart with gross margin by month: gross profit divided by revenue, as a percentage.”
Card	Agent	“Create a card with the gross profit for the period.”
Pivot table	Agent	“Create a pivot table with the units in the rows, the months in the columns and the sum of revenue in the values.”
Filter	Agent	“Create a chart filter by unit, multiple selection, and put it at the top of the Executive view dashboard.”
Organize the dashboard	Agent	“On the Executive view dashboard, create the Details tab and put the pivot table in it, with a section title Result by unit.”
Text on the dashboard	Agent	“Add a text at the top of the Summary tab explaining that the values are in reais.”
Organize the charts	Agent	“Put the revenue charts in a folder called Revenue.”
Database	Question	“On the ERP connection, list the order tables and show a sample of the columns.”
SQL query	Agent	“Update the query of the Orders cube to bring the total by customer and by month in 2026.”
Reproduce a sketch	Agent	Attach the image and write: “Build a dashboard similar to this sketch, using the data of the Sales cube.”

For charts that show a number by category, such as revenue by unit, the assistant creates the measure with a grouping field and turns on drill-down on the chart. If your request only says “revenue”, it creates the measure without grouping.

Good practices

• One goal per request. “Create the revenue by month chart” works better than five tasks in one sentence. For big requests, use Planning mode.
• Look before you create. In Question mode, ask which charts make sense for your data. Then ask it to create in Agent mode.
• Name the fields the way you see them. The assistant sees the mapped fields, the unmapped ones and the calculated ones. If a field is not checked in the cube, ask it to map the field first.
• Fix it right after. If the result came out different, say what to change in the same conversation: “switch to a line” or “use cost, not target”.
• Ask for the summary. At the end, ask “what did you create and what was left out?”. The assistant reports what it created, updated, validated or did not run.
• Check the numbers. Open the measures it created and look at the calculation type, the value field and the date field. See Measures.
• Start over when you need to. For a new subject, open a new conversation (New conversation). It starts without the history of the previous one and does not use AI credits.

What the assistant does not do

• Create connections to databases, files or APIs. Register the connection first and give its name.
• Create financial statements, cohort tables, relationships between cubes, refresh schedules or smart analysis blocks. Do those on the Hubviz Studio screen.
• Choose the period the reader will see. That belongs to the dashboard calendar.
• Guarantee that a number is right. It builds the calculation you asked for. Checking it is up to you.
• Guarantee that a database query only reads data. It is instructed to run read-only queries, but Hubviz Studio does not block other commands. Use a connection with a read-only database user.

Requests for AI analysis

The smart analysis block on the dashboard and the AI icon in Hubviz Web also accept a written request. It is a different feature: it explains a chart, it does not create anything. In the Hubviz Studio block, choose the Advanced mode and write in AI prompt. Requests that work well say what to compare, the period and the format of the answer:

• “Compare each unit’s revenue in the last quarter with the previous quarter. Answer in up to three bullet points and end with a recommendation.”
• “Point out the months when revenue fell below target and the difference in reais.”

Save the requests that worked in Prompt Gallery. See How to generate an AI analysis on a dashboard.

When the result is not what you expected

What you saw	Likely cause	What to ask for
Empty chart	Chart without a series, or a series without a measure	“Add to chart X the series with the Revenue measure.”
Number at zero	Wrong date in the measure, or a filter that matches no rows	“Show the Revenue measure and tell me which date field it uses.”
A new chart identical to an existing one	The request did not name it	“Edit the Revenue by month chart instead of creating another.”
The chart does not break down by unit	Measure without a grouping field, or drill-down off	“Turn on drill-down by unit on chart X.”
The AI stopped midway	Limit of 12 rounds or 3 errors in a row	Ask only for what is missing, in a new message.
AI request too big	Too many tasks in one sentence	Use Planning mode and run the plan.