MicroStrategy source configuration

Updated:

Note This topic is only relevant if you are creating technical lineage via Edge. If you are using the CLI lineage harvester (deprecated), you need to create a <source ID> configuration file. The CLI harvester will officially reach its End of Life on July 31, 2026.

The Source configuration field in the MicroStrategy technical lineage Edge capability allows you to:

  • Specify the default domain, meaning the domain in Collibra in which the corresponding assets of MicroStrategy metadata will be ingested if domain mapping is not configured.
    If you do configure domain mapping, the default domain is still the destination domain of the MicroStrategy Server asset.
  • Optionally, specify from which MicroStrategy projects you want to ingest metadata, and into which domains you want to ingest the corresponding assets.
  • Optionally, configure data source mapping, to map the name of a data source returned by the lineage harvester to the true name of the data source.
    Note Mapping doesn't work for custom SQL.

The value of the Source configuration field must be a valid block of JSON code, for example:

Copy 
{
    "default_domain_id": "66ab7911-d84a-43d6-b9f7-40130jd84ds98",
    "filters": [
        {
            "domainId": "3ae946ec-9030-46b8-ad86-a217b8f99bab",
            "projectIDs": ["3FF7CF7D4C5A2AEBF14D8B9802698B27"]
        },
        {
            "domainId": "21cfb3ae-0616-478e-9060-114130540be5",
            "projectNames": ["Human Resources Analysis Module"]
        }
    ],
    "datasourceMapping": [
     {
         "found_datasource": "REDSHIFT",
         "found_project": "*",
         "mapping": {
             "dbname": "RD_pearl",
              "schema_name": "Default_North",
              "dialect": "spark",
              "collibraSystemName": "TV_dev"
         }
     }
    ]
}

The following table describes the various properties you can use in your JSON code block.

Property

Description

Mandatory

default_domain_id

The domain in which you want the corresponding assets of MicroStrategy metadata to be ingested.

If you configure filtering, only the MicroStrategy Server asset is ingested into this default domain.

Yes

filters

This section allows you to specify:

  • From which MicroStrategy projects you want to harvest metadata.
  • Into which domains in Collibra you want to ingest the corresponding assets.

If you don't want to filter on projects, don't include this section in your <source ID> configuration file.

No
domainId

The unique resource ID of the domain (or domains) in Collibra in which you want to ingest the MicroStrategy assets.

Tip If you use a filters section, you must include the domainId property in the section. If, by chance, you want to filter on certain projects, but you want to ingest all assets into the default domain, then the value of the domainId property must match the value of the default_domain_id property.

For example:
"default_domain_id": "1234567890",
    "filters": [
        {
            "domainId": "1234567890",
            "projectNames": ["MicroStrategy Tutorial","Testing_MSTR"]
        },

To find a domain reference ID, open the relevant domain in Collibra. The URL looks like: https://<yourcollibrainstance>/domain/22258f64-40b6-4b16-9c08-c95f8ec0da26?view=00000000-0000-0000-0000-000000040001. In this example, the reference ID is in bold.

Yes
projectIds
 The IDs of the MicroStrategy projects from which you want to ingest metadata.

No
projectNames
 The project names of the MicroStrategy projects from which you want to ingest metadata.

No

datasourceMapping

This optional section allows you to configure data source mapping. Include this section only if you need to differentiate between multiple data sources that have the same name.

Note Mapping doesn't work for custom SQL.

No
found_datasource

The name of the data source that was returned by the lineage harvester, as shown in the technical lineage.

Note The data source name is case-sensitive.

Yes
found_project

The name of the project in which the data source information resides. You can specify an asterisk (*) to search for data source information across all projects.

Yes
mapping

Use this section to map the data source name that was returned by the lineage harvester to the true name of the data source.

Example You have a Redshift data source named "RD_pearl", but the lineage harvester has returned the name "Redshift_connection". You can configure the datasourceMapping section as follows:
Copy
{
    "datasourceMapping": [
     {
         "found_datasource": "REDSHIFT",
         "found_project": "*",
         "mapping": {
          "dbname": "RD_pearl",
          "collibraSystemName": "TV_dev"
         }
     }
    ]
}

Yes
dbname

The name of the database to which you want to map the found data source.

Yes
schema_name

The name of the schema in MicroStrategy.

No
dialect

The dialect of the data source in MicroStrategy.

No
collibraSystemName

The system or server name of a database.

Warning The values of this property must exactly match the name of your System asset in Collibra.

If you set the useCollibraSystemName property to true in your lineage harvester configuration file, but you either don't create a <source ID> configuration file, or don't specify a value for the collibraSystemName property in your <source ID> configuration file, the system name in the technical lineage is "DEFAULT".

If you set the useCollibraSystemName property to false in your lineage harvester configuration file, leave this property empty as follows: "collibraSystemName": "".

How to configure this property if you have two databases with the same name

Let's assume that you have a data source named Customers. You use this data source connection in two different projects, Project_A and Project_B, but they are actually two different databases. When you prepare the physical data layer in Data Catalog, you create a System asset for each of these databases. Let's say you named them Customers-North and Customers-South. You can then configure this property as follows.

Copy 
"datasourceMapping": [
        {
            "found_datasource": "Customers",
            "found_project": "Project_A",
            "mapping": {
                "dbname": "Customers",
                "collibraSystemName": "Customers_North"
            }
        },
        {
            "found_datasource": "Customers",
            "found_project": "Project_B",
            "mapping": {
                "dbname": "Customers",
                "collibraSystemName": "Customers_South"
            }
        }
    ]

Yes