Analyze
Analyze is where you go to actually query a cube. The page lists every cube across every schema in your tenant, shows whether each one is healthy, and provides a Open in Saiku button that drops you into the Saiku UI with the cube preloaded.
It’s the most-clicked dashboard page once your cubes are set up. Analysts come here for ad-hoc questions, share workbook links from the Saiku UI, and use the health status as a quick sanity check when something feels off.
Open a cube
Click Open in Saiku on the cube row. You’re signed into the Saiku UI automatically — same identity as the dashboard, no separate login. The cube is preloaded in the workbench; drag dimensions onto rows or columns, drag measures into the data area, and the pivot updates as you go. Save the workbook from the toolbar (File → Save as) if you want to come back to it.
The Saiku UI handles the usual OLAP toolkit: drill-down through hierarchies, filters, sorts, totals and sub-totals, export to Excel / CSV / PDF, and MDX editing for power users who’d rather write the query than drag.
Cube health
Each row shows a status:
- Active (green) — cube loaded cleanly, ready to query.
- Broken (red) — engine couldn’t attach the cube. Almost always one of two things: the underlying connection is misconfigured, or the schema XML has a problem (a column name in the cube doesn’t match the warehouse). Fix it in the source page and the status updates within a few seconds.
- Unconfigured (grey) — schema exists but no connection is wired. Set one on the connection’s detail page.
Broken cubes still show the launch button — clicking it opens the Saiku UI without a usable cube. Useful for confirming the error is on our side vs. yours, less useful for getting work done.
Saiku UI vs. the API
The Saiku UI is for humans — interactive, point-and-click, the right tool for analysts and ad-hoc reporting. For machine-driven query — an agent, a custom dashboard, a scheduled report — use the API instead. Both hit the same engine and read the same cubes, so the choice is just which front-end fits your workflow.
Related
- Schemas — where the cube XML lives.
- Connections — fix
Brokencubes here. - API authentication — query cubes from code instead of the UI.