> For the complete documentation index, see [llms.txt](https://docs.ovaledge.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ovaledge.com/release8.1/connectors/connector-repositories/reporting-tool/microstrategy.md).

# MicroStrategy

The MicroStrategy connector integrates MicroStrategy with OvalEdge to enable metadata management through crawling, report preview, and lineage building (automatic and manual). It crawls metadata from MicroStrategy projects, reports, dossiers, documents, pages, and visualizations, and maps these objects to the corresponding OvalEdge assets for governance and lineage analysis.

The connector connects to MicroStrategy using REST APIs and JDBC. REST APIs retrieve metadata from the MicroStrategy Library, while JDBC provides access to the MicroStrategy Metadata Repository for object definitions and dependencies. An optional Intelligence Server connection through MSTR.jar extracts metric formulas and SQL from reports, cubes, and dossiers to support complete lineage generation. Authentication uses MicroStrategy user credentials for REST API access and Metadata Repository database credentials for JDBC connectivity.

<img src="https://1121831267-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FFZv5WsZmBfXjiJfMU2zR%2Fuploads%2F3JC9gwf3D82eLMzWz4HE%2Funknown.png?alt=media&amp;token=e720a4c3-41c1-429f-a746-90a60dda7406" alt="" height="329" width="624">

## Overview

### Connector Details

| Connector Category                                                                | Reporting Tools                             |
| --------------------------------------------------------------------------------- | ------------------------------------------- |
| OvalEdge Release Supported                                                        | Release7.2.x and later                      |
| <p>Connectivity</p><p>\[How the connection is established with MicroStrategy]</p> | REST APIs and JDBC                          |
| Verified MicroStrategy Version                                                    | MicroStrategy 10.11 and later (on-premises) |

{% hint style="info" %}
The MicroStrategy connector has been validated with the mentioned "Verified MicroStrategy Versions" and is expected to be compatible with other supported MicroStrategy versions. If there are any issues with validation or metadata crawling, please submit a support ticket for investigation and feedback.
{% endhint %}

#### Connector Features

| Feature                                      |                                                                       Availability                                                                       |
| -------------------------------------------- | :------------------------------------------------------------------------------------------------------------------------------------------------------: |
| Crawling                                     |                                                                             ✅                                                                            |
| Profiling                                    |                                                                            NA                                                                            |
| Query Sheet                                  |                                                                            NA                                                                            |
| Report Preview                               |                                                                             ✅                                                                            |
| Auto Lineage                                 | <p>✅<br>To learn more, click <a href="/release8.1/connectors/connector-repositories/reporting-tool/microstrategy/microstrategy-lineage.md">here</a>.</p> |
| Manual Lineage                               |                                                                             ✅                                                                            |
| Secure Authentication via Credential Manager |                                                                             ✅                                                                            |
| Data Quality                                 |                                                                             ❌                                                                            |
| DAM (Data Access Management)                 |                                                                             ❌                                                                            |
| Bridge                                       |                                                                             ✅                                                                            |

{% hint style="info" %}
'NA' indicates that the respective feature is 'Not Applicable.'
{% endhint %}

### Metadata Mapping

The following objects are crawled from MicroStrategy and mapped to the corresponding UI assets.

| MicroStrategy Object | MicroStrategy Attribute | OvalEdge Attribute | OvalEdge Category | OvalEdge Type      |
| -------------------- | ----------------------- | ------------------ | ----------------- | ------------------ |
| Project              | Name of the Project     | Report Group       | Report Group      | Report Group       |
| Report               | name                    | Report             | Report            | Report Name        |
| Report               | Type                    | Report Type        | Report            | Report             |
| Report               | description             | Source Description | Report            | Source Description |
| Dossier              | name                    | Report             | Report            | Dossier Name       |
| Dossier              | Type                    | Report Type        | Report            | Dossier            |
| Dossier              | description             | Source Description | Report            | Source Description |
| Chapters             | name                    | Report             | Report            | Chapter Name       |
| Chapters             | Type                    | Report Type        | Report            | Chapter            |
| Pages                | name                    | Report             | Report            | Page Name          |
| Pages                | Type                    | Report Type        | Report            | Page               |
| Visualizations       | name                    | Report             | Report            | Visualization Name |
| Visualizations       | Type                    | Report Type        | Report            | Page               |
| Documents            | name                    | Report             | Report            | Document Name      |
| Documents            | Type                    | Report Type        | Report            | Document           |
| Documents            | description             | Source Description | Report            | Source Description |

## Set up a Connection

### Prerequisites

The prerequisites to establish a connection:

#### **External Supporting Files**

{% hint style="info" %}
The required external JAR files are included as part of the OvalEdge installation artifacts. For driver installation and configuration details, refer to the [Connector Drivers Setup Guide](https://docs.ovaledge.com/connectors/additional-requirements/connector-drivers-setup-guide). Please contact the OvalEdge Team for assistance related to the driver files and configuration setup.
{% endhint %}

#### **Service Account User Permissions**

{% hint style="warning" %}
It is recommended to use a separate service account to establish the connection to the data source, configured with the following minimum set of permissions.
{% endhint %}

{% hint style="info" %}
👨‍💻 Who can provide these permissions? The MicroStrategy administrator grants these permissions, since users may not have sufficient access to assign them.
{% endhint %}

<table><thead><tr><th width="115.3333740234375">Operation</th><th width="112">Objects</th><th width="230.6666259765625">Sys Tables</th><th width="195.98944091796875">Access Permissions</th></tr></thead><tbody><tr><td>Connector Validation</td><td>-</td><td>None - only JDBC connectivity test (SELECT 1 / SELECT 'Hello world' FROM DUAL); no DSSMD* tables queried</td><td>Valid Library user; login to MicroStrategy Library; list projects (GET /api/projects); read access to Metadata Repository DB (JDBC SELECT)</td></tr><tr><td>Crawling</td><td>-</td><td>DSSMDOBJDEPN, DSSMDOBJINFO - used for dependencies, document fields, and source code during crawl</td><td>All validation permissions; access to each target project; browse/search objects in project; read object definitions (Reports, Cubes, Dossiers, Documents); answer dossier prompts if prompted dossiers exist; Metadata DB read for Documents and source code; IServer access if MSTR.jar is used for metric formulas</td></tr><tr><td>Lineage</td><td>-</td><td>DSSMDOBJDEPN, DSSMDOBJINFO - used during crawl to build source code; lineage runs on stored source code (no additional metadata tables at lineage time)</td><td>Same as crawl for objects being processed; Metadata DB read for dependencies; crawled source code must exist; IServer + MSTR.jar for full metric SQL lineage</td></tr><tr><td>-</td><td>Reports</td><td>DSSMDOBJDEPN, DSSMDOBJINFO (dependencies + source code); report/cube definition comes from REST API, not metadata tables</td><td>Project access; Browse and View/Execute (read definition) on reports and intelligent cubes; REST search (type=768,769,774,3) and /api/v2/reports/ or /api/v2/cubes/</td></tr><tr><td>-</td><td>Dossiers</td><td><p><br></p><p>DSSMDOBJDEPN, DSSMDOBJINFO (dependencies + source code); dossier structure/fields from REST API</p></td><td>Project access; Browse and View dossiers; create dossier instance and read visualizations (prompted dossiers need prompt answer rights); REST /api/dossiers, /api/v2/dossiers/{id}/definition, instance APIs</td></tr><tr><td>-</td><td>Documents</td><td>DSSMDOBJDEPN, DSSMDOBJINFO (fields + dependencies); document list from REST API</td><td>Project access; Browse and View documents via Library API (/api/documents); Metadata DB read for fields and dependencies</td></tr></tbody></table>

### Connection Configuration Steps

{% hint style="warning" %}
Users must have the Connector Creator role to configure a new connection.
{% endhint %}

1. Log into **OvalEdge**, go to **Administration** > **Connectors**, click **+ (New Connector)**, search for **MicroStrategy**, and enter the required parameters.

{% hint style="info" %}
Fields marked with an asterisk (\*) are mandatory for establishing a connection.
{% endhint %}

<table><thead><tr><th width="220.33331298828125">Field Name</th><th>Description</th></tr></thead><tbody><tr><td>Connector Type</td><td>By default, "MicroStrategy" is displayed as the selected connector type.</td></tr><tr><td>Credential Manager*</td><td><p>Select the desired credentials manager from the drop-down list. Relevant parameters will be displayed based on the selection.</p><p>Supported Credential Managers:</p><ul><li>OE Credential Manager</li><li>AWS Secrets Manager</li><li>HashiCorp</li><li>Azure Key Vault</li></ul><p>For more details, click <a href="https://docs.ovaledge.com/connectors/additional-requirements/credential-manager-configuration">here</a>.</p></td></tr><tr><td>License Add-On</td><td><p>Select the Auto Lineage Add-On checkbox to build data lineage automatically.</p><p>For more details, click <a href="https://docs.ovaledge.com/connectors/introduction-to-connectors/setup-and-connectivity/license-types-and-add-ons">here</a>.</p></td></tr><tr><td>Connector Name*</td><td><p>Enter a unique name for the MicroStrategy connection              </p><p>(Example: "MicroStrategy_Prod").</p></td></tr><tr><td>Connector Environment</td><td><p>Select the environment (Example: PROD, STG) configured for the connector.</p><p>For more details, click <a href="https://docs.ovaledge.com/connectors/introduction-to-connectors/setup-and-connectivity/prerequisites#connector-environment">here</a>.</p></td></tr><tr><td>Connector Description</td><td>Enter the description related to the connector.</td></tr><tr><td>Host Name*</td><td>Enter the hostname or IP address of the MicroStrategy Library or Web server used to establish REST API communication with MicroStrategy.</td></tr><tr><td>Alias Host Name</td><td>Enter an alternate public hostname used to open reports in the MicroStrategy Library web application. If left blank, the value specified in Host Name is used.</td></tr><tr><td>Connection String*</td><td><p>Configure the connection string for the Oracle database:</p><ul><li>Automatic mode: The system generates a connection string based on the provided credentials.</li><li>Manual mode: Enter a valid connection string manually.</li></ul><p>Replace placeholders with actual database details.</p><p>{sid} refers to the database name.</p></td></tr><tr><td>Username*</td><td>Enter the username of the MicroStrategy account used to authenticate with the MicroStrategy Library REST API.</td></tr><tr><td>Password*</td><td>Enter the password associated with the specified MicroStrategy user account. This password is used to authenticate REST API requests to the MicroStrategy Library.</td></tr><tr><td>IServer</td><td>Enter the MicroStrategy Intelligence Server connection string. This is used to extract metric formulas and SQL from reports, cubes, and dossiers, enabling complete lineage generation.</td></tr><tr><td>MetaDB URL*</td><td>Enter the JDBC connection URL for the MicroStrategy Metadata Repository database. Supported databases include SQL Server, MySQL, and Oracle JDBC URLs.</td></tr><tr><td>Database Name*</td><td>Enter the name of the MicroStrategy Metadata Repository database (catalog, SID, or service name). This value is appended to the JDBC URL if it is not already included.</td></tr><tr><td>MetaDatabase UserName*</td><td>Enter the username for the MicroStrategy Metadata Repository database. This account is used to connect to the metadata repository through JDBC.</td></tr><tr><td>MetaDatabase Password*</td><td>Enter the password associated with the specified Metadata Repository database user account.</td></tr><tr><td>Proxy Enabled*</td><td>Select Yes to enable proxy settings or No to connect directly without a proxy.</td></tr></tbody></table>

<table data-header-hidden><thead><tr><th width="220.33331298828125"></th><th></th></tr></thead><tbody><tr><td><strong>Default Governance Roles</strong></td><td></td></tr><tr><td>Default Governance Roles*</td><td>Select the appropriate users or teams for each governance role from the drop-down list. All users and teams configured in OvalEdge Security are displayed for selection.</td></tr><tr><td><strong>Admin Roles</strong></td><td></td></tr><tr><td>Admin Roles*</td><td>Select one or more users from the drop-down list for Integration Admin and Security &#x26; Governance Admin. All users configured in OvalEdge Security are available for selection.</td></tr><tr><td><strong>No of Archive Objects</strong></td><td></td></tr><tr><td>No Of Archive Objects*</td><td><p>This shows the number of recent metadata changes to a dataset at the source. By default, it is off. To enable it, toggle the Archive button and specify the number of objects to archive.</p><p>Example: Setting it to 4 retrieves the last four changes, displayed in the 'Version' column of the 'Metadata Changes' module.</p></td></tr><tr><td><strong>Bridge</strong></td><td></td></tr><tr><td>Select Bridge*</td><td><p>If applicable, select the bridge from the drop-down list.</p><p>The drop-down list displays all active bridges configured in OvalEdge. These bridges enable communication between data sources and OvalEdge without altering firewall rules.</p></td></tr></tbody></table>

2. After entering all connection details, the following actions can be performed:
   1. Click **Validate** to verify the connection.
   2. Click **Save** to store the connection for future use.
   3. Click **Save & Configure** to apply additional settings before saving.
3. The saved connection will appear on the Connectors home page.

## Manage Connector Operations

### Crawl

{% hint style="warning" %}
To perform crawl operations, users must be assigned the Integration Admin role.
{% endhint %}

The **Crawl/Profile** button allows users to select one or more Report Groups/Reports for crawling.&#x20;

1. Navigate to the Connectors page and click **Crawl/Profile**.
2. Select the report groups/Reports to crawl.
3. Click **Run** to collect metadata from the connected source and load it into the Data Catalog.
4. After a successful crawl, the information appears in the Data Catalog > Report / Report Column tab.

The Schedule checkbox allows automated crawling for a selected timeframe, from a minute to a year.

1. Click the **Schedule** checkbox to enable the Select Period drop-down.
2. Select a time period for the operation from the drop-down menu.
3. Click **Schedule** to initiate metadata collection from the connected source.
4. The system will automatically execute the **crawl** operation at the scheduled time.

#### Other Operations

The Connectors page provides a centralized view of all configured connectors and their health status.

**Managing connectors includes:**

* **Connectors Health**: Displays the current status of each connector, with a green icon for active connections and a red icon for inactive connections, helping monitor connectivity to data sources.
* **Viewing**: Click the **Eye** icon next to the connector name to view connector details, including Reports, Report Columns, and Report Group.

**Nine Dots Menu Options:**

To view, edit, validate, build lineage, configure, or delete connectors, click on the **Nine Dots** menu.

* **Edit Connector**: Update and revalidate the data source.
* **Validate Connector**: Check the integrity of the connection.
* **Settings**: Modify connector settings.
  * **Crawler**: Configure data extraction.
  * **Access Instructions:** Add notes on how data can be accessed.
  * **Business Glossary Settings**: Manage term associations at the connector level.
  * **Lineage**: Select the parsing method (Regular or AI-Augmented) for generating lineage, and set a confidence threshold to control when AI-generated lineage is accepted or held for review. For more details, click [here](https://docs.ovaledge.com/release8.1/connectors/introduction-to-connectors/setup-and-connectivity/connector-settings#lineage-applicable-for-supported-connectors).
  * **Others**: Configure notification recipients for metadata changes.
* **Build Lineage**: Automatically build data lineage using source code parsing.
* **Delete Connector**: Remove a connector with confirmation.

For more details on connector settings, click [here](https://docs.ovaledge.com/connectors/introduction-to-connectors/setup-and-connectivity/connector-settings).

## Troubleshooting

If incorrect parameters are entered, error messages may appear. Ensure all inputs are accurate to resolve these issues. If issues persist, contact the assigned support team.

{% tabs %}
{% tab title="Connectivity" %}

<table data-search="true"><thead><tr><th width="58.9375">S. No</th><th width="188.95703125">Error Message</th><th width="476.37109375">Error Description &#x26; Resolution</th></tr></thead><tbody><tr><td>1</td><td>Error while validating connection: unable to access REST API</td><td><p>Validation starts with the REST API, which returns the session token and cookies and lists the projects. It fails when the REST API cannot be reached or the account lacks permission to use it.</p><p><strong>Resolution</strong>:</p><ul><li>Confirm the host name and connection string match the MicroStrategy library server.</li><li>Confirm the username and password are valid and the login mode matches the account type.</li><li>Confirm the user has permission to make REST API requests from the application.</li></ul></td></tr><tr><td>2</td><td>Error while validating connection: unable to connect to the metadata database</td><td><p>After the REST API check, validation tests the JDBC connection to the MicroStrategy metadata database. It fails when the URL is incorrect or the database name does not match.</p><p><strong>Resolution</strong>:</p><ul><li>Confirm the metadata database URL and database name (the SID) match the MicroStrategy metadata database.</li><li>Confirm the database type is one of those supported, such as Oracle, MySQL, or SQL Server.</li><li>Confirm the metadata database username and password are correct, and the server is reachable.</li></ul></td></tr><tr><td>3</td><td>Metadata database authentication fails for Windows or Azure Active Directory options</td><td><p>The authentication option selected does not match how the metadata database is configured.</p><p><strong>Resolution</strong>:</p><ul><li>For SQL Server authentication, confirm the metadata database URL, database name, username, and password.</li><li>For Windows authentication, confirm the metadata database is SQL Server-based and the domain user name and password are correct.</li><li>For Azure Active Directory, confirm the metadata database is Azure SQL or SQL Server enabled for Azure Active Directory, and confirm the URL, database name, and credentials.</li></ul></td></tr><tr><td>4</td><td>Validation succeeds, but the required projects are not available</td><td><p>The MicroStrategy user must have access to the required projects on the server. Without it, projects are not returned during validation.</p><p><strong>Resolution</strong>:</p><ul><li>Confirm the user has access to every project that needs to be catalogued.</li><li>Ask the MicroStrategy administrator to grant project access where it is missing.</li><li>Revalidate the connection after access is granted.</li></ul></td></tr><tr><td>5</td><td>Connection fails when the proxy option is enabled</td><td><p>When a proxy is enabled, each request first reaches the proxy server, which checks the requester and the resources requested before allowing access to the network.</p><p><strong>Resolution</strong>:</p><ul><li>Confirm the proxy details entered in the connection attributes are correct.</li><li>Confirm the proxy server allows requests to the MicroStrategy library server and the metadata database.</li><li>Disable the proxy option if the environment does not use one.</li></ul></td></tr><tr><td>6</td><td>Global domain or global authentication token error during connection</td><td><p>This error was seen often in earlier versions and has been handled in later versions.</p><p><strong>Resolution</strong>:</p><ul><li>Confirm the application is running a version that includes the fix.</li><li>Revalidate the connection to obtain a fresh token.</li><li>Escalate to the support team with the job log if the error continues.</li></ul></td></tr></tbody></table>
{% endtab %}

{% tab title="Crawling" %}

<table data-search="false"><thead><tr><th width="58.828125">S. No</th><th width="189.84375">Error Message</th><th width="481.87890625">Error Description &#x26; Resolution</th></tr></thead><tbody><tr><td>1</td><td>401 unauthorized during crawling</td><td><p>The authentication token expired while the crawl was running.</p><p><strong>Resolution</strong>:</p><ul><li>Revalidate the connection to obtain a new token.</li><li>Refresh the page and trigger the crawl again.</li><li>Confirm the user account is still active and has project access.</li></ul></td></tr><tr><td>2</td><td>Columns are not displayed for reports</td><td><p>Report columns are crawled only when the report columns option is enabled in the crawler options.</p><p><strong>Resolution</strong>:</p><ul><li>Open the crawler options and enable the report columns option.</li><li>Run the crawl again for the required projects.</li><li>Open the report to confirm the columns are now listed.</li></ul></td></tr><tr><td>3</td><td>Delta crawl not picking only the updated reports</td><td><p>Delta crawl is a separate option. When it is disabled, all reports in the selected projects are crawled again.</p><p><strong>Resolution</strong>:</p><ul><li>Enable the delta crawl option in the crawler options.</li><li>Select only the projects that need the delta crawl.</li><li>Run the crawl so that only updated reports are processed.</li></ul></td></tr><tr><td>4</td><td>Dossier sub reports such as chapters, pages, or visualizations are missing in the Data Catalog</td><td><p>The system setting that hides subreports may be enabled. This setting applies to all report type connectors, not only MicroStrategy.</p><p><strong>Resolution</strong>:</p><ul><li>Open the system settings and check whether hiding subreports is enabled (Key: <strong>exclude.datacatalog.subreport</strong>).</li><li>Disable the setting if the sub-reports need to be visible.</li><li>Once the setting is disabled, subreports are displayed in the Data Catalog.</li></ul></td></tr><tr><td>5</td><td>Sub reports missing for a prompted dossier</td><td><p>Prompted dossiers depend on internal prompt handling in the crawling logic, which cannot be verified from the application screens.</p><p><strong>Resolution</strong>:</p><ul><li>Confirm whether the dossier uses prompts.</li><li>Confirm that the hide sub-reports setting is not enabled.</li><li>Escalate the dossier to the support team with the crawl log for review.</li></ul></td></tr><tr><td>6</td><td>Expected reports or dossiers are not catalogued</td><td><p>Include or exclude rules configured in the crawler options may be filtering them out, or the user may lack access to the project that holds them.</p><p><strong>Resolution</strong>:</p><ul><li>Review the include and exclude rules in the crawler options.</li><li>Confirm the MicroStrategy user has access to the project.</li><li>Recrawl after the rules or access are corrected.</li></ul></td></tr></tbody></table>
{% endtab %}

{% tab title="Lineage" %}

<table data-search="true"><thead><tr><th width="58.90234375">S. No</th><th width="189.7421875">Error Message</th><th width="505.55078125">Error Description &#x26; Resolution</th></tr></thead><tbody><tr><td>1</td><td>No SQL available in lineage</td><td><p>Report SQL, metric formulas, and prompt details are extracted through the MSTR jar and the intelligence server connection. Lineage cannot be built from SQL when the JAR is missing or the intelligence server is not configured.</p><p><strong>Resolution</strong>:</p><ul><li>Confirm the MSTR JAR is placed in the required path on the server where the application or bridge is installed.</li><li>Confirm the application has permission to read the JAR from that folder.</li><li>Confirm the intelligence server details are configured and reachable, then rebuild the lineage.</li></ul></td></tr><tr><td>2</td><td>Lineage shows as built but no source tables are linked for a report</td><td><p>The SQL for that report was not picked up correctly. Without the SQL, the semantic and physical tables cannot be identified.</p><p><strong>Resolution</strong>:</p><ul><li>Review the lineage job log and check whether the report was processed with or without a cube.</li><li>Confirm the MSTR jar and intelligence server settings are working.</li><li>Rerun the lineage job and escalate the report if no source is linked.</li></ul></td></tr><tr><td>3</td><td>SQL not parsed correctly or wrong tables assigned</td><td><p>The SQL dialect matching the source database is not selected in the lineage settings.</p><p><strong>Resolution</strong>:</p><ul><li>Select the dialect that matches the source database in the lineage settings.</li><li>Confirm that the dialect matches the database used by the MicroStrategy reports.</li><li>Rebuild the lineage after saving the settings.</li></ul></td></tr><tr><td>4</td><td>Lineage linked to an unexpected source when several connectors hold the same tables</td><td><p>More than one connector may hold objects matching the same source tables.</p><p><strong>Resolution</strong>:</p><ul><li>Set the connector priority in the lineage settings so the intended connector is matched first.</li><li>Confirm the intended source connector is catalogued and current.</li><li>Rebuild the lineage after the priority is saved.</li></ul></td></tr><tr><td>5</td><td>Source database tables missing at the end of the lineage</td><td><p>Lineage connects to actual source tables only when the source connection has already been catalogued in the application.</p><p><strong>Resolution</strong>:</p><ul><li>Confirm the source database connector, such as SQL Server or MySQL, has been crawled.</li><li>Confirm the source tables used by the report appear in the catalog.</li><li>Rebuild the lineage once the source objects are available.</li></ul></td></tr></tbody></table>
{% endtab %}
{% endtabs %}

## FAQs

{% tabs %}
{% tab title="First Tab" %}

<table data-search="true"><thead><tr><th width="58.9921875">S. No</th><th width="189.23828125">Question</th><th width="472.90625">Answer</th></tr></thead><tbody><tr><td>1</td><td>What is the MicroStrategy connector used for?</td><td><p>MicroStrategy is a business intelligence and analytics platform used to create reports and dossiers. The connector brings that metadata into the application.</p><ul><li>Projects, reports, dossiers, documents, datasets, metrics, and attributes are discovered and catalogued.</li><li>Business glossary and custom fields are supported.</li><li>Lineage is built from the source databases through to reports and dossiers.</li></ul></td></tr><tr><td>2</td><td>How does the application connect to MicroStrategy?</td><td><p>Three integration channels are used.</p><ul><li>The MicroStrategy library REST API handles authentication and discovery of projects, reports, dossiers, and documents.</li><li>The metadata database is accessed through JDBC to read object dependencies.</li><li>The MSTR jar connects to the intelligence server (I server) to extract report SQL, metric formulas, and prompt details.</li></ul><p>The MSTR jar runs as a Java process through the bridge.</p></td></tr><tr><td>3</td><td>What details are needed to create the connection?</td><td><p>The following fields are used:</p><ul><li>Connection name, which is a label chosen for the connector</li><li>Host name or IP address of the MicroStrategy library server</li><li>Connection string, which is filled in automatically once the host name is entered</li><li>User name and password of the MicroStrategy account</li><li>Metadata database URL and database name</li><li>Username and password of the metadata database</li></ul></td></tr><tr><td>4</td><td>Which fields are optional?</td><td><p>Some fields are optional.</p><ul><li>The intelligence server connection string is optional when the MSTR JAR is available on the server where the application runs.</li><li>The source name field is optional.</li><li>Enable proxy is optional.</li></ul><p>Bridge and credential manager options apply only when those setups are used.</p></td></tr><tr><td>5</td><td>What is the password of the MicroStrategy account used for?</td><td>The password is used for REST API authentication. It is also used when the MSTR jar needs authentication to connect to the intelligence server.</td></tr><tr><td>6</td><td>What authentication types are supported?</td><td><p>Two layers of authentication apply.</p><ul><li>REST API authentication uses a username, password, and login mode to obtain a session token and cookies.</li><li>Metadata database authentication can be SQL Server authentication, Windows authentication, or Azure Active Directory password.</li></ul><p>Windows authentication needs a SQL Server-based metadata database and domain credentials. Azure Active Directory needs an Azure SQL or SQL Server metadata database.</p></td></tr><tr><td>7</td><td>What must be in place before creating the connection?</td><td><p>The following prerequisites apply:</p><ul><li>A live MicroStrategy environment with permission to use REST APIs</li><li>A metadata database that is reachable, such as Oracle, MySQL, or SQL Server</li><li>A valid MicroStrategy user with access to the required projects</li><li>The MSTR jar placed in a folder on the server where the application is installed, with permission to read it</li><li>An intelligence server reachable for SQL extraction, which lineage needs</li></ul></td></tr><tr><td>8</td><td>What does connection validation check?</td><td><p>Validation follows a fixed order.</p><ul><li>The REST API is accessed, and a token and cookies are obtained.</li><li>All projects in MicroStrategy are listed.</li><li>The metadata database is checked for reachability through JDBC.</li><li>The connection is marked valid once all required permissions are available.</li></ul></td></tr><tr><td>9</td><td>What is a proxy and when is it enabled?</td><td><p>A proxy is an additional server placed in front of the MicroStrategy network.</p><ul><li>Every request first reaches the proxy server.</li><li>The proxy checks who is requesting and which resources are requested.</li><li>Only after that is access to the network server allowed.</li></ul><p>The option can be enabled through the connection attributes, and the proxy details must then be provided.</p></td></tr><tr><td>10</td><td>Can credentials be stored in a credential manager?</td><td><p>Yes.</p><p>The database, HashiCorp, Azure Key Vault, and AWS Secrets Manager options are supported.</p></td></tr><tr><td>11</td><td>Is bridge deployment supported?</td><td><p>Yes.</p><p>The bridge is supported for environments that need it, and the MSTR jar runs through the bridge when the intelligence server is reached this way.</p></td></tr><tr><td>12</td><td>Which capabilities are supported?</td><td><p>The following are supported:</p><ul><li>Crawling of projects and report objects</li><li>Delta crawl</li><li>Restricted time zone and schedule options</li><li>Business glossary and custom fields</li><li>Auto lineage</li></ul><p>Data access management and data quality are not supported, and their options appear to be disabled.</p></td></tr><tr><td>13</td><td>Is the MicroStrategy cloud (SaaS) version supported?</td><td><p>Support is partial.</p><ul><li>Crawling, cataloguing, and preview are supported because the same REST APIs are used.</li><li>Lineage is not available at present because the metadata database and MSTR JAR are not accessible in the cloud version.</li><li>An enhancement to use newer APIs for SQL and lineage is planned, with no database connection or JAR needed. Its timeline is not fixed.</li></ul></td></tr></tbody></table>
{% endtab %}

{% tab title="Crawling" %}

<table data-search="true"><thead><tr><th width="58.73828125">S. No</th><th width="189.203125">Question</th><th width="476.06640625">Answer</th></tr></thead><tbody><tr><td>1</td><td>Which objects are crawled?</td><td><p>The following are crawled and shown under reports in the Data Catalog:</p><ul><li>Documents and dossiers</li><li>Folders</li><li>Chapters and pages</li><li>Report visualizations</li><li>Reports, datasets, and cubes</li></ul></td></tr><tr><td>2</td><td>How are MicroStrategy projects shown?</td><td><p>Each MicroStrategy project is treated as a domain in the application.</p><p>For example, Enterprise Manager is shown as a domain. All folders and objects inside a project appear under it after the crawl.</p></td></tr><tr><td>3</td><td>What is the hierarchy of a dossier?</td><td><p>A dossier holds chapters; each chapter holds pages, and each page holds one or more visualizations.</p><ul><li>Chapters and pages appear on the subreports tab of the dossier.</li><li>Visualizations are shown under the page they belong to.</li></ul></td></tr><tr><td>4</td><td>What crawler options are available?</td><td><p>The main options are:</p><ul><li>Report columns: see columns in the application</li><li>Delta crawl: process only updated reports</li><li>Restricted time zone</li><li>Include and exclude rules using regex</li><li>Business glossary</li><li>Lineage dialect and connector priority, which are optional</li></ul></td></tr><tr><td>5</td><td>What is delta crawl?</td><td><p>The first crawl reads the entire connection. Later, only reports that were updated in MicroStrategy need to be read again.</p><ul><li>Enable the delta crawl option.</li><li>Select only the projects that need it.</li><li>Only the updated reports are then crawled instead of all reports.</li></ul></td></tr><tr><td>6</td><td>Can sub reports be hidden from the Data Catalog?</td><td><p>Yes.</p><p>A system setting hides sub-reports such as chapters, pages, and visualizations. It applies to every report-type connector, not only MicroStrategy.</p></td></tr><tr><td>7</td><td>What appears in the crawl log?</td><td><p>The log shows the crawl settings and progress.</p><ul><li>Whether reports and report columns are enabled</li><li>Whether the restricted time zone and delta crawl are disabled or enabled</li><li>Include and exclude rules that were configured</li><li>The lineage dialect and connector priority list</li><li>A workbook count for each project</li></ul></td></tr><tr><td>8</td><td>What does the workbook count in the log mean?</td><td>The count covers all assets in the project, including reports, dossiers, documents, datasets, and cubes. It does not include sub reports. Default reports supplied with MicroStrategy are also counted.</td></tr><tr><td>9</td><td>Which customers or project sizes need delta crawl most?</td><td>Delta crawl is most useful for projects that hold thousands of reports, where crawling everything each time takes long.</td></tr></tbody></table>
{% endtab %}

{% tab title="Lineage" %}

<table data-search="true"><thead><tr><th width="58.5390625">S. No</th><th width="189.1953125">Question</th><th width="472.76953125">Answer</th></tr></thead><tbody><tr><td>1</td><td>How is lineage built for a report?</td><td><p>Lineage follows the data from the source to the report.</p><ul><li>Datasets link to a cube or directly to semantic tables.</li><li>Semantic tables provide semantic columns, which link to physical tables and columns.</li><li>The physical tables connect to the source connection, such as SQL Server or MySQL.</li></ul></td></tr><tr><td>2</td><td>Is a cube always part of lineage?</td><td><p>No.</p><p>A cube is optional. Some reports connect directly to semantic tables through the dataset.</p></td></tr><tr><td>3</td><td>How is lineage shown for dossiers?</td><td>A dossier links to its chapters, chapters link to pages, and pages link to visualizations. Reports and datasets used by the dossier link further back to the sources.</td></tr><tr><td>4</td><td>Where does the SQL for lineage come from?</td><td>The SQL comes from the MSTR jar through the intelligence server, together with details from the metadata database. Lineage depends on this SQL, so it cannot be built if the jar or server is unavailable.</td></tr><tr><td>5</td><td>What is the lineage dialect setting?</td><td>The dialect helps parse the SQL and assign the correct sources and targets. It is set in the lineage settings based on the source database.</td></tr><tr><td>6</td><td>What is the connector priority setting?</td><td>When several connectors hold tables from the same source, the priority decides which connector is matched first. It is optional.</td></tr><tr><td>7</td><td>How does the lineage log show cube usage?</td><td>The log states whether a report is processed with a cube or without a cube. This helps confirm how the report SQL and dependencies were resolved.</td></tr><tr><td>8</td><td>Why might lineage be missing after a crawl completes successfully?</td><td>Crawling and lineage use different sources. Crawling uses the REST API, while lineage also needs SQL from the MSTR jar and the metadata database. A working crawl does not guarantee that SQL was extracted.</td></tr></tbody></table>
{% endtab %}
{% endtabs %}

***

Copyright © 2026, OvalEdge LLC, Peachtree Corners GA USA


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.ovaledge.com/release8.1/connectors/connector-repositories/reporting-tool/microstrategy.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.