MicroStrategy lineage configuration

Last updated: Apr 15, 2025

To import lineage metadata from MicroStrategy, create a connection, data source definition and metadata import job.

To import lineage metadata for MicroStrategy, complete these steps:

Creating a data source definition

Create a data source definition. Select MicroStrategy as the data source type. In the Hostname or IP address field, skip the library path, for example 12.345.678.90.

Creating a connection to MicroStrategy

Create a connection to the data source in a project. For connection details, see MicroStrategy connection.

Creating a metadata import

Create a metadata import. Learn more about options that are specific to MicroStrategy data source:

Include and exclude lists
External inputs

Include and exclude lists

You can include or exclude assets up to the project level. Assets which are added later in the data source will also be included or excluded if they match the conditions specified in the lists. Example values:

myProject: all reports in myProject

External inputs

You can provide an exported MicroStrategy project as external input. The file can have the following structure:

<project_id> - A folder with the project ID.
  cubes - A folder with cubes.
    [cube_id].json - A file with an exported cube.
  datasets - A folder with datasets.
    [dataset_id].json - A file with an exported dataset.
  dossiers - A folder with dossiers.
    [dossier_id] - A folder with dossier ID.
      dossierDefintion.json - A file with an exported definition of the dossier.
      visualisations - A folder with dossier visualisations.
        [visualisation_key].json - A file with an exported visualisation.
  reports - A folder with reports.
    [report_id].json - A file with an exported report.
  attributes.json - A file with attributes.
  facts.json - A file with facts.
  logicalTables.json - A file with logicalTables.
  metrics.json - A file with metrics.
  project.json - A file with project information.