MicroStrategy lineage configuration

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

MicroStrategy is a reporting and data analytics platform.

Supported MicroStrategy versions

  • MicroStrategy 11.3.6 (2021 Update 6)

Processed metadata

The following MicroStrategy metadata is processed and displayed on lineage:

  • Projects
  • Dossiers
  • Reports
  • Cubes
  • Attributes
  • Metrics
  • Facts
  • Logical tables

Limitations

The following data is not processed:

  • Documents
  • Free-form SQL
  • Datasources
    • Connection to a file
  • Embedded metrics

Prerequisite configuration

Before you import lineage metadata, ensure that the following prerequisites are met:

  • MicroStrategy server must be reachable over the network.
  • You must have the System administrator or Platform administrator role.

Creating a metadata import asset

Data source connection

To connect to the data source from which you want to import lineage metadata, you need to select a data source definition and a connection. You can create them before you start creating the metadata import, or you can create them when you create and configure the metadata import asset.

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.

Connection

When you create the connection, use the following details:

  • MicroStrategy Library URL. For example, http://microstrategy.my-company.com:8080/MicroStrategyLibrary.
  • Username and password

For connection details, see MicroStrategy connection.

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.

Learn more