MicroStrategy Collected Data
This page lists what Sifflet imports from MicroStrategy and how it builds lineage.
Imported Assets
Sifflet imports the following assets from every project the Sifflet user can access:
| Asset type | Description |
|---|---|
| Dashboards | MicroStrategy dashboards (dossiers), including dashboards not published to the MicroStrategy Library |
| Reports | Reports used as a dataset by a dashboard |
| Intelligent Cubes | Cubes used as a dataset by a dashboard or a report |
| Physical tables | The tables read by these cubes, used to link cubes to your warehouse tables |
Dashboards and reports appear in the Data Catalog and in the lineage. Physical tables appear in the lineage only.
Sifflet doesn't import other MicroStrategy objects, such as standalone reports that no dashboard uses, documents, attributes, facts, or metrics. If you need support for other objects, contact Sifflet support.
Collected Metadata
- Dashboards: name, description, and the datasets (reports and cubes) they use.
- Reports: name, and the cube they are based on.
- Cubes: name, and the logical tables they use.
- Physical tables: name, schema, and the database type of their MicroStrategy data source.
Sifflet doesn't collect usage statistics (views) for MicroStrategy assets.
Lineage
Sifflet builds lineage from the MicroStrategy REST API: physical tables → Intelligent Cubes → reports → dashboards. For each cube, Sifflet reads the physical tables behind the logical tables the cube uses, and links each physical table to the matching table of your other Sifflet sources, by schema and table name.
Lineage to warehouse tables is supported when the MicroStrategy data source is one of:
- Snowflake
- Google BigQuery
- Amazon Redshift
Data Freshness
Sifflet refreshes MicroStrategy metadata on the source's schedule. See Integrations Management for default frequencies and scheduling.
Limitations
- Sifflet builds upstream lineage from Intelligent Cubes only. Dashboards and reports whose datasets aren't Intelligent Cubes appear in Sifflet without links to warehouse tables.
- Physical tables of logical tables defined by a SQL statement aren't linked to warehouse tables.
- Only the primary data source of each logical table is used for lineage.
- Datasets that use the "Connect Live" access mode aren't accessible through the APIs Sifflet uses, so they have no lineage.
- When MicroStrategy can't return the definition of a dashboard (for example when one of its dataset reports fails), Sifflet imports the dashboard without its datasets.
Sifflet Insights Browser Extension
The Sifflet Insights browser extension supports the following MicroStrategy asset types, when opened from the MicroStrategy Library:
- Dashboards
- Reports
Data Exposure
Sifflet only reads MicroStrategy object definitions: it never reads or stores the data of your reports, cubes, or dashboards. See Security for more details on the data Sifflet stores.
Updated about 2 hours ago

