Cubes are analytical models built on top of structured data. They define the measures you want to calculate, the dimensions you want to group and filter by, and the SQL logic that generates the data. This guide walks you through creating cubes and executing queries.Documentation Index
Fetch the complete documentation index at: https://docs.ideaboxai.com/llms.txt
Use this file to discover all available pages before exploring further.
Understanding cubes
A cube defines three things.| Component | Description | Example |
|---|---|---|
| Measures | Metrics to calculate. | Total revenue, average price, record count. |
| Dimensions | Attributes to group or filter by. | Date, category, region, status. |
| SQL Logic | The underlying query that generates the cube data. | A SELECT statement joining relevant tables. |
Access the cube configuration interface
In the structured knowledge base view, the cube interface shows:- A list of existing cubes in the left panel.
- The measures and dimensions of the selected cube.
- Query execution controls and a result preview.

Create a new cube

AI Generate (recommended)
Let AI automatically generate the base SQL, measures, and dimensions from a natural language description.Enter a cube name
Provide a unique, descriptive identifier, for example
ORDER_SUMMARY or MONTHLY_REVENUE.Describe the analytics in natural language
Tell the AI what you want to analyse, for example “Show total revenue by region and product category, with month-over-month trends.”

Manual query
For advanced users who want to author SQL directly.
- Clearly document the business intent in the description and context fields.
- Test generated SQL before deploying to production workflows.
- Start with simple cubes and iterate based on feedback.
Execute queries and view results
Once a cube is created, you can query it using the cube selection panel.
View results in multiple formats
Query results are available in several formats via tabs.| Tab | Description |
|---|---|
| Results | Interactive table or chart view of the query output. |
| Generated SQL | The SQL query powering the results. |
| SQL API | An endpoint for SQL-based integrations. |
| REST API | A RESTful endpoint for application integrations. |
| GraphQL API | A GraphQL endpoint for data fetching. |
- Start with a limited number of dimensions for better performance.
- Reuse generated API endpoints instead of re-running UI queries.
- Validate results against source systems for critical analytics.
- Export and share results with your team.