This section shows the BI tool operating models and related information.
Note Keep in mind, it is possible that your organization has renamed the out-of-the-box asset types and characteristics.
Steps
|
Select a BI tool. Currently, the information is shown for: |
Looker
MicroStrategy
Power BI
SAP Analytics Cloud
SSRS-PBRS
Tableau
|
|
Overview and diagram view
Synchronizing means refreshing the assets that are currently in Data Catalog as a result of a previous ingestion or synchronization job. After synchronizing Tableau, the assets in Data Catalog accurately reflect the metadata as it exists at the time of synchronization.
- The assets have the same names as their counterparts in Tableau.
- Some asset types are only created if the Tableau user has specific permissions.
- Relations that were created between Tableau assets and other assets via a relation type in the Tableau operating model, are deleted upon synchronization. The same is true of any attribute types in the operating model that you add to Tableau assets. To ensure that the characteristics you add to Tableau assets are not deleted upon synchronization, be sure to use characteristics that are not part of the Tableau operating model.
The following image shows the relations between Tableau asset types.
You can easily recreate this diagram view in your Collibra environment. See Create a Tableau operating model diagram view.
Harvested metadata per asset type
This table shows the metadata for each Tableau asset type and the resource ID for each asset type and metadata.
|
Asset type |
Synchronized metadata |
Resource ID |
|---|---|---|
|
Tableau Server Resource ID: 00000000-0000-0000-0000-110000000005 |
Description |
00000000-0000-0000-0000-000000003114 |
| Server hosts / is hosted in Business Dimension | 00000000-0000-0000-0000-120000000000 | |
| URL: The link to the data in Tableau | 00000000-0000-0000-0000-000000000258 | |
|
Tableau Site Resource ID: 00000000-0000-0000-0000-110000000000 |
Description | 00000000-0000-0000-0000-000000003114 |
|
BI Folder assembles / Is assembled in BI Folder |
00000000-0000-0000-0000-120000000001 | |
| Server hosts / is hosted in Business Dimension | 00000000-0000-0000-0000-120000000000 | |
| URL: The link to the data in Tableau | 00000000-0000-0000-0000-000000000258 | |
|
Tableau Project Resource ID: 00000000-0000-0000-0000-110000000001 |
Description |
00000000-0000-0000-0000-000000003114 |
|
Owner in source The only harvested metadata are email addresses. To harvest this metadata, you need to enable the Metadata API by setting the For additional rules and limitations, see Additional information, further down in this topic. |
00000000-0000-0000-0000-200000000001 | |
|
BI Folder assembles / is assembled in BI Folder |
00000000-0000-0000-0000-120000000001 | |
| Business Dimension groups / is grouped into Report | 00000000-0000-0000-0000-120000000002 | |
|
BI Folder contains / contained in Data Asset |
00000000-0000-0000-0000-120000000014 | |
|
Tableau Workbook Resource ID: 00000000-0000-0000-0000-110000000002 |
Description |
00000000-0000-0000-0000-000000003114 |
| Document creation date | 00000000-0000-0000-0000-000000000260 | |
| Document modification date | 00000000-0000-0000-0000-000000000261 | |
| Document size | 00000000-0000-0000-0000-000000000259 | |
|
Owner in source The only harvested metadata are email addresses. To harvest this metadata, you need to enable the Metadata API by setting the For additional rules and limitations, see Additional information, further down in this topic. |
00000000-0000-0000-0000-200000000001 | |
| URL: The link to the data in Tableau | 00000000-0000-0000-0000-000000000258 | |
|
This is the amount of times the workbook was viewed in Tableau. |
00000000-0000-0000-0000-000000000264 | |
| Report groups / is grouped into Report | 00000000-0000-0000-0000-120000000004 | |
| Tableau Workbook contains / contained in Tableau Data Model | 00000000-0000-0000-0000-120000000020 | |
| Business Dimension groups / is grouped into Report | 00000000-0000-0000-0000-120000000002 | |
|
Tableau Dashboard Resource ID: 00000000-0000-0000-0001-110000000301 Assets of this type are only created if the Tableau user has the Download/Save As permission on the workbook. |
||
| Document creation date | 00000000-0000-0000-0000-000000000260 | |
|
Document modification date |
00000000-0000-0000-0000-000000000261 | |
|
Owner in source The only harvested metadata are email addresses. To harvest this metadata, you need to enable the Metadata API by setting the For additional rules and limitations, see Additional information, further down in this topic. |
00000000-0000-0000-0000-200000000001 |
|
|
Report image: The image of the report.
Images are downloaded and attached to the assets in Data Catalog. You can configure the maximum file size and content types of the Tableau images in the Collibra DGC service settings.
|
00000000-0000-0000-0000-000000000262 | |
| URL: The link to the data in Tableau | 00000000-0000-0000-0000-000000000258 | |
| Visible on server | 00000000-0000-0000-0000-000000000265 | |
|
This is the amount of times the dashboard was viewed in Tableau. |
00000000-0000-0000-0000-000000000264 | |
| Report groups / is grouped into Report | 00000000-0000-0000-0000-120000000004 | |
| Report uses / used in Data Attribute | 00000000-0000-0000-0000-120000000021 | |
| Report uses / used in Report | 00000000-0000-0000-0000-120000000007 | |
|
Tableau Worksheet Resource ID: 00000000-0000-0000-0001-110000000300 Assets of this type are only created if the Tableau user has the Download/Save As permission on the workbook. |
||
| Document creation date | 00000000-0000-0000-0000-000000000260 | |
|
Document modification date |
00000000-0000-0000-0000-000000000261 | |
|
Report image: The image of the report.
Images are downloaded and attached to the assets in Data Catalog. You can configure the maximum file size and content types of the Tableau images in the Collibra DGC service settings.
|
00000000-0000-0000-0000-000000000262 | |
| URL: The link to the data in Tableau | 00000000-0000-0000-0000-000000000258 | |
| Visible on server | 00000000-0000-0000-0000-000000000265 | |
|
This is the amount of times the worksheet was viewed in Tableau. |
00000000-0000-0000-0000-000000000264 | |
| Report groups / is grouped into Report | 00000000-0000-0000-0000-120000000004 | |
|
Report uses / used in Data Attribute |
00000000-0000-0000-0000-120000000021 | |
| Report uses / used in Report | 00000000-0000-0000-0000-120000000007 | |
|
Tableau Data Attribute Resource ID: 00000000-0000-0000-0000-110000000010 Assets of this type are only created if the Tableau user has the Download/Save As permission on the data source. |
Description |
00000000-0000-0000-0000-000000003114 |
|
Calculation Rule |
00000000-0000-0000-0000-000000003117 | |
| Data Type: The data type of a data asset, as it is declared by the data source. | 00000000-0000-0000-0001-000500000005 | |
| Role in Report | 00000000-0000-0000-0000-000000000266 | |
| BI Data Model contains / is part of BI Data Attribute | 00000000-0000-0000-0000-000000007196 | |
| Data Element targets / sources Data Element | 00000000-0000-0000-0000-000000007069 | |
|
Report uses / used in Data Attribute |
00000000-0000-0000-0000-120000000021 | |
|
Tableau Data Model Resource ID: 00000000-0000-0000-0000-110000000008 Assets of this type are only created if the Tableau user has the Download/Save As permission on the data source. |
Description |
00000000-0000-0000-0000-000000003114 |
|
Certified Note Certification is only possible for published Tableau data sources. |
00000000-0000-0000-0001-000500000001 | |
|
Document creation date |
00000000-0000-0000-0000-000000000260 | |
|
Document modification date |
00000000-0000-0000-0000-000000000261 | |
|
Original Name: The name of the data source in Tableau |
00000000-0000-0000-0001-000500000032 | |
|
Owner in source The only harvested metadata are email addresses. To harvest this metadata, you need to enable the Metadata API by setting the For additional rules and limitations, see Additional information, further down in this topic. |
00000000-0000-0000-0000-200000000001 | |
| BI Data Model contains / is part of BI Data Attribute | 00000000-0000-0000-0000-000000007196 | |
| Business Dimension source / is source of System | 00000000-0000-0000-0000-120000000003 | |
| Tableau Workbook contains / contained in Tableau Data Model | 00000000-0000-0000-0000-120000000020 | |
| Data Asset contained in / contains BI Folder | 00000000-0000-0000-0000-120000000014 |
Additional information
For the Owner in source attribute, the following rules apply:
- If the system creates a
- If the user who created a
Note The Owner is source metadata (email address) is only returned if the user is the owner of the data inside the project. If the user is the owner of the project, but not the data in the project, the metadata is not returned. This is a known issue that is specific to the Tableau Metadata API.
Example of ingested Tableau metadata
The following image shows an example structure after synchronizing Tableau.
In Collibra 2024.05, we launched a new user interface (UI) for Collibra Data Intelligence Platform! You can learn more about this latest UI in the UI overview.
Use the following options to see the documentation in the latest UI or in the previous, classic UI:
Recommended hierarchy within a domain
You can enable hierarchies for the domain (or domains) in which your Tableau assets were ingested. Doing so makes it easier to understand the relation between your Tableau assets, when viewing the assets on the domain page.
Follow these steps to enable and configure the recommended hierarchy.
Steps
- Open the domain page of the relevant BI Catalog domain.
- On the content toolbar, click
.
The Configure Hierarchy dialog box appears. - Select Enable Hierarchy.
- Select Multipath.
- Start typing and select each of the following relation types:
- Server hosts Business Dimension
- BI Folder assembles BI Folder
- Business Dimension groups Report
- Report groups Report
- Report uses Report
- Report uses Data Attribute
- BI Folder contains Data Asset
- BI Data Model contains BI Data Attribute
- Tableau Workbook contains Tableau Data Model
- Click Apply.
- In an asset view, if any asset is deleted, for example via synchronization or manual deletion, the view is recreated and the hierarchy is lost. In this case, you can again enable and configure the recommended hierarchy.
- When viewing the hierarchy for a community or domain, if the parent of a node that is in the community or domain belongs to a different community or domain, that node is not shown in the hierarchy.
Create a Tableau operating model diagram view
You can create a Tableau-specific diagram view, to visualize the operating model. The following procedure provides instruction on how to quickly create a new diagram view by copying and pasting the JSON code in the diagram view text editor.
Steps
- Open an asset page.
- Click the
Diagram tab.
The diagram is shown in the default diagram view. - Click
to add a new view. - Click the Text tab, to switch to the diagram view text editor.
- Click Show me the JSON code below this procedure, to expand the code.
- Click
in the top-right of the expanded code, to copy the code.
The code is copied to your clipboard. - Paste the code in diagram view text editor.
- Click Save.
- Edit the name and description of the diagram view, to suit your needs.
{
"nodes": [
{
"id": "Tableau Workbook",
"type": {
"id": "00000000-0000-0000-0000-110000000002"
},
"layoutRegion": "context"
},
{
"id": "Tableau Dashboard",
"type": {
"id": "00000000-0000-0000-0001-110000000301"
},
"layoutRegion": "context"
},
{
"id": "Tableau Worksheet",
"type": {
"id": "00000000-0000-0000-0001-110000000300"
},
"layoutRegion": "context"
},
{
"id": "Tableau Data Model",
"type": {
"id": "00000000-0000-0000-0000-110000000008"
},
"layoutRegion": "context",
"editorSettings": {
"nodePropsExpanded": false
}
},
{
"id": "Tableau Project",
"type": {
"id": "00000000-0000-0000-0000-110000000001"
},
"layoutRegion": "context"
},
{
"id": "Tableau Site",
"type": {
"id": "00000000-0000-0000-0000-110000000000"
},
"layoutRegion": "context"
},
{
"id": "Tableau Server",
"type": {
"id": "00000000-0000-0000-0000-110000000005"
},
"layoutRegion": "context"
},
{
"id": "Tableau Data Attribute",
"type": {
"id": "00000000-0000-0000-0000-110000000010"
},
"layoutRegion": "context"
},
{
"id": "Column",
"type": {
"id": "00000000-0000-0000-0000-000000031008"
},
"layoutRegion": "context"
},
{
"id": "Table",
"type": {
"id": "00000000-0000-0000-0000-000000031007"
},
"layoutRegion": "context"
},
{
"id": "Schema",
"type": {
"id": "00000000-0000-0000-0001-000400000002"
},
"layoutRegion": "context"
},
{
"id": "Database",
"type": {
"id": "00000000-0000-0000-0000-000000031006"
},
"layoutRegion": "context"
}
],
"edges": [
{
"from": "Tableau Project",
"to": "Tableau Workbook",
"label": "",
"style": "arrow",
"type": {
"id": "00000000-0000-0000-0000-120000000002"
},
"roleDirection": true
},
{
"from": "Tableau Site",
"to": "Tableau Project",
"label": "",
"style": "arrow",
"type": {
"id": "00000000-0000-0000-0000-120000000001"
},
"roleDirection": true
},
{
"from": "Tableau Server",
"to": "Tableau Site",
"label": "",
"style": "arrow",
"type": {
"id": "00000000-0000-0000-0000-120000000000"
},
"roleDirection": true
},
{
"from": "Tableau Data Model",
"to": "Tableau Data Attribute",
"label": "",
"style": "arrow",
"type": {
"id": "00000000-0000-0000-0000-000000007196"
},
"roleDirection": true
},
{
"from": "Tableau Data Attribute",
"to": "Tableau Data Attribute",
"label": "",
"style": "arrow",
"type": {
"id": "00000000-0000-0000-0000-000000007069"
},
"roleDirection": false
},
{
"from": "Tableau Workbook",
"to": "Tableau Data Model",
"label": "",
"style": "arrow",
"type": {
"id": "00000000-0000-0000-0000-120000000020"
},
"roleDirection": true
},
{
"from": "Tableau Project",
"to": "Tableau Data Model",
"label": "",
"style": "arrow",
"type": {
"id": "00000000-0000-0000-0000-120000000014"
},
"roleDirection": true
},
{
"from": "Column",
"to": "Column",
"label": "",
"style": "boxing",
"type": {
"id": "00000000-0000-0000-0000-000000007069"
},
"roleDirection": false
},
{
"from": "Column",
"to": "Table",
"label": "",
"style": "boxed",
"type": {
"id": "00000000-0000-0000-0000-000000007042"
},
"roleDirection": true
},
{
"from": "Table",
"to": "Schema",
"label": "",
"style": "boxed",
"type": {
"id": "00000000-0000-0000-0000-000000007043"
},
"roleDirection": false
},
{
"from": "Schema",
"to": "Database",
"label": "",
"style": "boxed",
"type": {
"id": "00000000-0000-0000-0000-000000007024"
},
"roleDirection": false
},
{
"from": "Tableau Data Attribute",
"to": "Tableau Worksheet",
"label": "",
"style": "arrow",
"type": {
"id": "00000000-0000-0000-0000-120000000021"
},
"roleDirection": false
},
{
"from": "Tableau Workbook",
"to": "Tableau Worksheet",
"label": "",
"style": "arrow",
"type": {
"id": "00000000-0000-0000-0000-120000000004"
},
"roleDirection": true
},
{
"from": "Tableau Workbook",
"to": "Tableau Dashboard",
"label": "",
"style": "arrow",
"type": {
"id": "00000000-0000-0000-0000-120000000004"
},
"roleDirection": true
},
{
"from": "Tableau Worksheet",
"to": "Tableau Dashboard",
"label": "",
"style": "arrow",
"type": {
"id": "00000000-0000-0000-0000-120000000007"
},
"roleDirection": false
},
{
"from": "Tableau Data Attribute",
"to": "Column",
"label": "",
"style": "arrow",
"type": {
"id": "00000000-0000-0000-0000-000000007069"
},
"roleDirection": false
},
{
"from": "Tableau Project",
"to": "Tableau Project",
"label": "",
"style": "boxed",
"type": {
"id": "00000000-0000-0000-0000-120000000001"
},
"roleDirection": true
},
{
"from": "Tableau Dashboard",
"to": "Tableau Data Attribute",
"label": "",
"style": "arrow",
"type": {
"id": "00000000-0000-0000-0000-120000000012"
},
"roleDirection": true
}
],
"showOverview": false,
"enableFilters": true,
"showLabels": true,
"showFields": true,
"showLegend": true,
"showPreview": true,
"visitStrategy": "directed",
"layout": "HierarchyTopBottom",
"maxNodeLabelLength": 50,
"maxEdgeLabelLength": 30,
"layoutOptions": {
"compactGroups": false,
"componentArrangementPolicy": "topmost",
"edgeBends": true,
"edgeBundling": true,
"edgeToEdgeDistance": 5,
"minimumLayerDistance": "auto",
"nodeToEdgeDistance": 5,
"orthogonalRouting": true,
"preciseNodeHeightCalculation": true,
"recursiveGroupLayering": true,
"separateLayers": true,
"webWorkers": true,
"nodePlacer": {
"barycenterMode": true,
"breakLongSegments": true,
"groupCompactionStrategy": "none",
"nodeCompaction": false,
"straightenEdges": true
}
}
}
Overview and diagram view
The lineage harvester collects Power BI metadata and sends it to the Collibra Data Lineage service instances. Collibra processes the metadata and creates new Power BI assets and relations in Data Catalog. You can see them on the asset page overview or visualize them in a diagram or in a technical lineage.
- The assets have the same names as their counterparts in Power BI. Full names and Display names cannot be changed in Data Catalog.
- Asset types are only created if you have all specific Power BI and Data Catalog permissions.
- The Power BI assets are created in the domain (or domains) that you specify in the lineage harvester configuration file.
- Relations that were created between Power BI assets and other assets via a relation type in the Power BI operating model, are deleted upon synchronization. The same is true of any attribute types in the operating model that you add to Power BI assets. To ensure that the characteristics you add to Power BI assets are not deleted upon synchronization, be sure to use characteristics that are not part of the Power BI operating model.
The following image shows the relations between Power BI asset types.
Harvested metadata per asset type
This table shows the harvested Power BI metadata for each Power BI asset type. This table also shows the resource ID for each asset type, attribute, and relation.
Note The metadata that is shown on the assets' pages depends on the asset type's assignment. As a result, you might not see all harvested metadata on the asset's page by default.
Additional information
For the Owner in source attribute, the following rules apply:
- If the system creates a
- If the user who created a
URLs to reports and dashboards that can't be found in Power BI
When you add a report or dashboard to an app in Power BI, what happens is that copies of the original report or dashboard is created in the app. The URL on the corresponding asset page in Collibra links directly to the copied report or dashboard in the app. However, if the name of the original report or dashboard changes, or if it has been deleted in Power BI, the copies in the app remain unchanged. Therefore, to remedy what would otherwise be links to outdated copies of reports or dashboards in Power BI, the URLs on the asset pages instead link to the Power BI app.
Example of ingested Power BI metadata
The following image shows an example structure after Power BI ingestion.
In Collibra 2024.05, we launched a new user interface (UI) for Collibra Data Intelligence Platform! You can learn more about this latest UI in the UI overview.
Use the following options to see the documentation in the latest UI or in the previous, classic UI:
Recommended hierarchy within a domain
You can enable hierarchies for the domain (or domains) in which your Power BI assets are ingested. Doing so makes it easier to understand the relation between your Power BI assets, when viewing the assets on the domain page.
Follow these steps to enable and configure the recommended hierarchy.
Steps
- Open the domain page of the relevant BI Catalog domain.
- On the content toolbar, click .
The Configure Hierarchy dialog box appears. - Select Enable Hierarchy.
- Select Multipath.
- Start typing and select each of the following relation types:
- Server hosts Business Dimension
- BI Folder assembles BI Folder
- Business Dimension groups Report
- BI Report source Data Asset
- Data Model contains Data Entity
- Data Entity contains Data Attribute
- Click Apply.
- In an asset view, if any asset is deleted, for example via synchronization or manual deletion, the view is recreated and the hierarchy is lost. In this case, you can again enable and configure the recommended hierarchy.
- When viewing the hierarchy for a community or domain, if the parent of a node that is in the community or domain belongs to a different community or domain, that node is not shown in the hierarchy.
Create a Power BI operating model diagram view
You can create a Power BI-specific diagram view, to visualize the operating model. The following procedure provides instruction on how to quickly create a new diagram view by copying and pasting the JSON code in the diagram view text editor.
Steps
- Open an asset page.
- Click the
Diagram tab.
The diagram is shown in the default diagram view. - Click to add a new view.
- Click the Text tab, to switch to the diagram view text editor.
- Click Show me the JSON code below this procedure, to expand the code.
- Click in the top-right of the expanded code, to copy the code.
The code is copied to your clipboard.
- Paste the code in diagram view text editor.
- Click Save.
- Edit the name and description of the diagram view, to suit your needs.
{
"nodes": [
{
"id": "Power BI Server",
"type": {
"id": "00000000-0000-0000-0000-100000000001"
},
"fields": []
},
{
"id": "Power BI Capacity",
"type": {
"id": "00000000-0000-0000-0000-100000000002"
}
},
{
"id": "Power BI Workspace",
"type": {
"id": "00000000-0000-0000-0000-100000000003"
}
},
{
"id": "Power BI Dashboard",
"type": {
"id": "00000000-0000-0000-0000-100000000004"
}
},
{
"id": "Power BI Report",
"type": {
"id": "00000000-0000-0000-0000-100000000006"
}
},
{
"id": "Power BI Tile",
"type": {
"id": "00000000-0000-0000-0000-100000000005"
}
},
{
"id": "Power BI Data Model",
"type": {
"id": "00000000-0000-0000-0000-100000000007"
}
},
{
"id": "Power BI Data Flow",
"type": {
"id": "00000000-0000-0000-0000-100000000010"
}
},
{
"id": "Power BI Table",
"type": {
"id": "00000000-0000-0000-0000-100000000009"
}
},
{
"id": "Power BI Column",
"type": {
"id": "00000000-0000-0000-0000-100000000008"
},
"fields": [
{
"key": "stringAttribute_00000000-0000-0000-0000-000000003117",
"label": "Calculation Rule"
}
]
},
{
"id": "Column",
"type": {
"id": "00000000-0000-0000-0000-000000031008"
}
},
{
"id": "Table",
"type": {
"id": "00000000-0000-0000-0000-000000031007"
}
},
{
"id": "Schema",
"type": {
"id": "00000000-0000-0000-0001-000400000002"
}
},
{
"id": "Database",
"type": {
"id": "00000000-0000-0000-0000-000000031006"
}
},
{
"id": "Power BI Data Mart",
"type": {
"id": "00000000-0000-0000-0000-100000000052"
}
}
],
"edges": [
{
"from": "Power BI Server",
"to": "Power BI Capacity",
"label": "",
"style": "arrow",
"type": {
"id": "00000000-0000-0000-0000-120000000000"
},
"roleDirection": true
},
{
"from": "Power BI Capacity",
"to": "Power BI Workspace",
"label": "",
"style": "boxing",
"type": {
"id": "00000000-0000-0000-0000-120000000001"
},
"roleDirection": true
},
{
"from": "Power BI Workspace",
"to": "Power BI Dashboard",
"label": "",
"style": "arrow",
"type": {
"id": "00000000-0000-0000-0000-120000000002"
},
"roleDirection": true
},
{
"from": "Power BI Workspace",
"to": "Power BI Report",
"label": "",
"style": "arrow",
"type": {
"id": "00000000-0000-0000-0000-120000000002"
},
"roleDirection": true
},
{
"from": "Power BI Workspace",
"to": "Power BI Tile",
"label": "",
"style": "arrow",
"type": {
"id": "00000000-0000-0000-0000-120000000002"
},
"roleDirection": true
},
{
"from": "Power BI Workspace",
"to": "Power BI Data Model",
"label": "",
"style": "arrow",
"type": {
"id": "00000000-0000-0000-0000-120000000014"
},
"roleDirection": true
},
{
"from": "Power BI Workspace",
"to": "Power BI Data Flow",
"label": "",
"style": "arrow",
"type": {
"id": "00000000-0000-0000-0000-120000000014"
},
"roleDirection": true
},
{
"from": "Power BI Dashboard",
"to": "Power BI Tile",
"label": "",
"style": "boxing",
"type": {
"id": "00000000-0000-0000-0000-120000000007"
},
"roleDirection": true
},
{
"from": "Power BI Data Model",
"to": "Power BI Tile",
"label": "",
"style": "arrow",
"type": {
"id": "00000000-0000-0000-0000-120000000013"
},
"roleDirection": true
},
{
"from": "Power BI Data Model",
"to": "Power BI Report",
"label": "",
"style": "arrow",
"type": {
"id": "00000000-0000-0000-0000-120000000013"
},
"roleDirection": true
},
{
"from": "Power BI Data Flow",
"to": "Power BI Report",
"label": "",
"style": "arrow",
"type": {
"id": "00000000-0000-0000-0000-000000007196"
},
"roleDirection": true
},
{
"from": "Power BI Data Flow",
"to": "Power BI Table",
"label": "",
"style": "arrow",
"type": {
"id": "00000000-0000-0000-0000-120000000014"
},
"roleDirection": true
},
{
"from": "Power BI Tile",
"to": "Power BI Report",
"label": "",
"style": "arrow",
"type": {
"id": "00000000-0000-0000-0000-120000000007"
},
"roleDirection": true
},
{
"from": "Power BI Data Flow",
"to": "Power BI Data Flow",
"label": "",
"style": "arrow",
"type": {
"id": "00000000-0000-0000-0000-120000000022"
},
"roleDirection": true
},
{
"from": "Power BI Column",
"to": "Column",
"label": "",
"style": "arrow",
"type": {
"id": "00000000-0000-0000-0000-000000007069"
},
"roleDirection": false
},
{
"from": "Column",
"to": "Table",
"label": "",
"style": "boxed",
"type": {
"id": "00000000-0000-0000-0000-000000007042"
},
"roleDirection": true
},
{
"from": "Table",
"to": "Schema",
"label": "",
"style": "boxed",
"type": {
"id": "00000000-0000-0000-0000-000000007043"
},
"roleDirection": false
},
{
"from": "Schema",
"to": "Database",
"label": "",
"style": "boxed",
"type": {
"id": "00000000-0000-0000-0000-000000007024"
},
"roleDirection": false
},
{
"from": "Power BI Data Flow",
"to": "Power BI Data Mart",
"label": "",
"style": "arrow",
"type": {
"id": "00000000-0000-0000-0000-120000000022"
},
"roleDirection": false
},
{
"from": "Power BI Data Mart",
"to": "Power BI Data Mart",
"label": "",
"style": "arrow",
"type": {
"id": "00000000-0000-0000-0000-120000000022"
},
"roleDirection": true
},
{
"from": "Power BI Data Mart",
"to": "Power BI Table",
"label": "",
"style": "arrow",
"type": {
"id": "00000000-0000-0000-0000-120000000014"
},
"roleDirection": true
},
{
"from": "Power BI Data Mart",
"to": "Power BI Data Model",
"label": "",
"style": "arrow",
"type": {
"id": "00000000-0000-0000-0000-120000000022"
},
"roleDirection": true
},
{
"from": "Power BI Data Model",
"to": "Power BI Data Model",
"label": "",
"style": "arrow",
"type": {
"id": "00000000-0000-0000-0000-120000000022"
},
"roleDirection": false
},
{
"from": "Power BI Table",
"to": "Power BI Data Model",
"label": "",
"style": "boxed",
"type": {
"id": "00000000-0000-0000-0000-000000007046"
},
"roleDirection": true
},
{
"from": "Power BI Column",
"to": "Power BI Table",
"label": "",
"style": "boxed",
"type": {
"id": "00000000-0000-0000-0000-000000007047"
},
"roleDirection": false
},
{
"from": "Power BI Column",
"to": "Power BI Column",
"label": "",
"style": "arrow",
"type": {
"id": "00000000-0000-0000-0000-000000007069"
},
"roleDirection": true
}
],
"showOverview": false,
"enableFilters": true,
"showLabels": true,
"showFields": true,
"showLegend": true,
"showPreview": true,
"visitStrategy": "directed",
"layout": "HierarchyTopBottom",
"maxNodeLabelLength": 50,
"maxEdgeLabelLength": 30,
"layoutOptions": {
"compactGroups": false,
"componentArrangementPolicy": "topmost",
"edgeBends": true,
"edgeBundling": true,
"edgeToEdgeDistance": 5,
"minimumLayerDistance": "auto",
"nodeToEdgeDistance": 5,
"orthogonalRouting": true,
"preciseNodeHeightCalculation": true,
"recursiveGroupLayering": true,
"separateLayers": true,
"webWorkers": true,
"nodePlacer": {
"barycenterMode": true,
"breakLongSegments": true,
"groupCompactionStrategy": "none",
"nodeCompaction": false,
"straightenEdges": true
}
}
}
Overview and diagram view
When you integrate MicroStrategy, Collibra Data Lineage creates new MicroStrategy assets and relations in Data Catalog. You can see them on the asset page overview or visualize them in a diagram.
- The assets have the same names as their corresponding data objects in MicroStrategy.
- Asset types are only created if you have all specific MicroStrategy and Data Catalog permissions.
- All MicroStrategy assets are created in the same domain.
- Relations that were manually created between MicroStrategy assets and other assets via a relation type in the MicroStrategy operating model, are deleted after synchronizing the MicroStrategy metadata.
The following image shows the relations between MicroStrategy asset types.
Note Currently, relations between MicroStrategy Documents, MicroStrategy Dossiers, and MicroStrategy Reports cannot be shown.
Harvested metadata per asset type
This table shows the harvested MicroStrategy metadata for assets of each MicroStrategy asset type, assuming you have the necessary subscriptions and configurations for a full ingestion.
Important To access MicroStrategy data, you have to use the In-memory Dataset connection method in MicroStrategy, not the Live Connect connection method. If the data is not stored in memory, the MicroStrategy APIs can't access it.
- Object Templates
- System Objects
- Version Update History
| Asset type | Harvested MicroStrategy metadata in Data Catalog |
Resource ID |
|---|---|---|
|
MicroStrategy Data Attribute Resource ID: 00000000-0000-0000-0000-100000000047 |
Description |
00000000-0000-0000-0000-000000003114 |
|
Source Type |
00000000-0000-0000-0000-000000000230 |
|
|
Technical Data Type |
00000000-0000-0000-0000-000000000219 |
|
|
Data Element targets / sources Data Element |
00000000-0000-0000-0000-000000007069 |
|
|
Data Entity contains / is part of Data Attribute |
00000000-0000-0000-0000-000000007047 |
|
|
Data Attribute used in / uses Report |
00000000-0000-0000-0000-120000000021 |
|
|
MicroStrategy Data Entity Resource ID: 00000000-0000-0000-0000-100000000048 |
Description |
00000000-0000-0000-0000-000000003114 |
|
Source Type |
00000000-0000-0000-0000-000000000230 |
|
|
Data Entity contains / is part of Data Attribute |
00000000-0000-0000-0000-000000007047 |
|
|
Data Entity is part of / contains Data Model |
00000000-0000-0000-0000-000000007046 |
|
|
Data Asset is source for / sources BI Report |
00000000-0000-0000-0000-120000000013 |
|
|
MicroStrategy Data Model Resource ID: 00000000-0000-0000-0000-100000000046 Note If the data model is embedded in the project, the data model inherits the name of the project. |
Description |
00000000-0000-0000-0000-000000003114 |
|
Certified |
00000000-0000-0000-0001-000500000001 | |
|
Owner in source The only harvested metadata are email addresses. |
00000000-0000-0000-0000-200000000001 | |
|
Source Type |
00000000-0000-0000-0000-000000000230 |
|
| BI Folder contains / contained in Data Asset | 00000000-0000-0000-0000-120000000014 | |
|
Data Asset is source for / sources BI Report |
00000000-0000-0000-0000-120000000013 |
|
|
Data Model contains / is part of Data Entity |
00000000-0000-0000-0000-000000007046 |
|
|
MicroStrategy Document Resource ID: 00000000-0000-0000-0000-100000000049 |
Description |
00000000-0000-0000-0000-000000003114 |
|
Certified |
00000000-0000-0000-0001-000500000001 | |
|
Owner in source The only harvested metadata are email addresses. |
00000000-0000-0000-0000-200000000001 | |
|
URL Note You can specify the platform on which you run MicroStrategy, in your lineage harvester configuration file, to ensure the correct URL. |
00000000-0000-0000-0000-000000000258 | |
|
Business Dimension groups / is grouped into Report |
00000000-0000-0000-0000-120000000002 | |
|
BI Report contains / contained in BI Data Model |
00000000-0000-0000-0000-120000000015 | |
|
MicroStrategy Dossier Resource ID: 00000000-0000-0000-0000-100000000043 |
Description |
00000000-0000-0000-0000-000000003114 |
|
Certified |
00000000-0000-0000-0001-000500000001 | |
|
Owner in source The only harvested metadata are email addresses. |
00000000-0000-0000-0000-200000000001 | |
|
Business Dimension groups / is grouped into Report |
00000000-0000-0000-0000-120000000002 | |
|
Report uses / used in Report |
00000000-0000-0000-0000-120000000007 | |
|
MicroStrategy Folder Resource ID: 00000000-0000-0000-0000-100000000042 |
Description |
00000000-0000-0000-0000-000000003114 |
|
BI Folder assembles / is assembled in BI Folder |
00000000-0000-0000-0000-120000000001 | |
|
Business Dimension groups / is grouped into Report |
00000000-0000-0000-0000-120000000002 | |
|
BI Folder contains / contained in Data Asset |
00000000-0000-0000-0000-120000000014 |
|
|
MicroStrategy Project Resource ID: 00000000-0000-0000-0000-100000000041 |
Description |
00000000-0000-0000-0000-000000003114 |
|
BI Folder assembles / is assembled in BI Folder |
00000000-0000-0000-0000-120000000001 | |
|
Server hosts / is hosted in Business Dimension |
00000000-0000-0000-0000-120000000000 | |
|
MicroStrategy Report Resource ID: 00000000-0000-0000-0000-100000000044 |
Description |
00000000-0000-0000-0000-000000003114 |
|
Certified |
00000000-0000-0000-0001-000500000001 | |
|
URL |
00000000-0000-0000-0000-000000000258 | |
|
Owner in source The only harvested metadata are email addresses. |
00000000-0000-0000-0000-200000000001 | |
|
Report groups / is grouped into Report |
00000000-0000-0000-0000-120000000004 | |
|
Business Dimension groups / is grouped into Report |
00000000-0000-0000-0000-120000000002 | |
|
Data Asset is source for / sources BI Report |
00000000-0000-0000-0000-120000000013 |
|
|
MicroStrategy Server Resource ID: 00000000-0000-0000-0000-100000000040 |
Server hosts / is hosted in Business Dimension |
00000000-0000-0000-0000-120000000000 |
Recommended hierarchy within a domain
You can enable hierarchies for the domain in which your MicroStrategy assets are ingested. Doing so makes it easier to understand the relation between your MicroStrategy assets, when viewing the assets on the domain page.
Follow these steps to enable and configure the recommended hierarchy.
Steps
- Open the domain page of the relevant BI Catalog domain.
- On the content toolbar, click .
The Configure Hierarchy dialog box appears. - Select Enable Hierarchy.
- Select Single path.
- Start typing and select each of the following relation types:
- Server hosts Business Dimension
- BI Folder assembles BI Folder
- Business Dimension groups Report
- BI Report source Data Asset
- BI Folder contains Data Asset
- Data Model contains Data Entity
- Data Entity contains Data Attribute
- Click Apply.
- In an asset view, if any asset is deleted, for example via synchronization or manual deletion, the view is recreated and the hierarchy is lost. In this case, you can again enable and configure the recommended hierarchy.
- When viewing the hierarchy for a community or domain, if the parent of a node that is in the community or domain belongs to a different community or domain, that node is not shown in the hierarchy.
Create a MicroStrategy operating model diagram view
You can create a MicroStrategy-specific diagram view, to visualize the operating model. The following procedure provides instruction on how to quickly create a new diagram view by copying and pasting the JSON code in the diagram view text editor.
Steps
- Open an asset page.
- Click the
Diagram tab.
The diagram is shown in the default diagram view. - Click to add a new view.
- Click the Text tab, to switch to the diagram view text editor.
- Click Show me the JSON code below this procedure, to expand the code.
- Click in the top-right of the expanded code, to copy the code.
The code is copied to your clipboard.
- Paste the code in diagram view text editor.
- Click Save.
- Edit the name and description of the diagram view, to suit your needs.
{
"nodes": [
{
"id": "MicroStrategy Report",
"type": {
"id": "00000000-0000-0000-0000-100000000044"
}
},
{
"id": "MicroStrategy Data Attribute",
"type": {
"id": "00000000-0000-0000-0000-100000000047"
},
"editorSettings": {
"edgePropsExpanded": true
}
},
{
"id": "BI Folder",
"type": {
"id": "00000000-0000-0000-0000-090000000002"
},
"display": "expanded"
},
{
"id": "MicroStrategy Dossier",
"type": {
"id": "00000000-0000-0000-0000-100000000043"
}
},
{
"id": "MicroStrategy Document",
"type": {
"id": "00000000-0000-0000-0000-100000000049"
}
},
{
"id": "BI Report Attribute",
"type": {
"id": "00000000-0000-0000-0000-090000000004"
}
},
{
"id": "BI Data Entity",
"type": {
"id": "00000000-0000-0000-0000-090000000007"
}
},
{
"id": "BI Data Model",
"type": {
"id": "00000000-0000-0000-0000-090000000008"
}
},
{
"id": "Column",
"type": {
"id": "00000000-0000-0000-0000-000000031008"
}
},
{
"id": "Table",
"type": {
"id": "00000000-0000-0000-0000-000000031007"
}
},
{
"id": "Schema",
"type": {
"id": "00000000-0000-0000-0001-000400000002"
}
},
{
"id": "Database",
"type": {
"id": "00000000-0000-0000-0000-000000031006"
}
},
{
"id": "Business Term",
"type": {
"id": "00000000-0000-0000-0000-000000011001"
}
}
],
"edges": [
{
"from": "MicroStrategy Report",
"to": "MicroStrategy Data Attribute",
"label": "",
"style": "arrow",
"type": {
"id": "00000000-0000-0000-0000-120000000021"
},
"roleDirection": true
},
{
"from": "BI Folder",
"to": "MicroStrategy Report",
"label": "",
"style": "arrow",
"type": {
"id": "00000000-0000-0000-0000-120000000002"
},
"roleDirection": true
},
{
"from": "BI Folder",
"to": "BI Folder",
"label": "",
"style": "boxing",
"type": {
"id": "00000000-0000-0000-0000-120000000001"
},
"roleDirection": true
},
{
"from": "BI Folder",
"to": "MicroStrategy Dossier",
"label": "",
"style": "arrow",
"type": {
"id": "00000000-0000-0000-0000-120000000002"
},
"roleDirection": true
},
{
"from": "BI Folder",
"to": "MicroStrategy Document",
"label": "",
"style": "arrow",
"type": {
"id": "00000000-0000-0000-0000-120000000002"
},
"roleDirection": true
},
{
"from": "MicroStrategy Dossier",
"to": "BI Report Attribute",
"label": "",
"style": "arrow",
"type": {
"id": "00000000-0000-0000-0000-000000007058"
},
"roleDirection": false
},
{
"from": "MicroStrategy Document",
"to": "BI Report Attribute",
"label": "",
"style": "arrow",
"type": {
"id": "00000000-0000-0000-0000-000000007058"
},
"roleDirection": false
},
{
"from": "BI Report Attribute",
"to": "MicroStrategy Data Attribute",
"label": "",
"style": "arrow",
"type": {
"id": "00000000-0000-0000-0000-120000000010"
},
"roleDirection": true
},
{
"from": "BI Data Entity",
"to": "MicroStrategy Data Attribute",
"label": "",
"style": "boxing",
"type": {
"id": "00000000-0000-0000-0000-000000007047"
},
"roleDirection": true
},
{
"from": "BI Data Model",
"to": "BI Data Entity",
"label": "",
"style": "boxing",
"type": {
"id": "00000000-0000-0000-0000-000000007046"
},
"roleDirection": false
},
{
"from": "MicroStrategy Report",
"to": "MicroStrategy Report",
"label": "",
"style": "arrow",
"type": {
"id": "00000000-0000-0000-0000-120000000013"
},
"roleDirection": false
},
{
"from": "MicroStrategy Report",
"to": "BI Data Model",
"label": "",
"style": "arrow",
"type": {
"id": "00000000-0000-0000-0000-120000000013"
},
"roleDirection": false
},
{
"from": "MicroStrategy Document",
"to": "BI Data Model",
"label": "",
"style": "arrow",
"type": {
"id": "00000000-0000-0000-0000-120000000013"
},
"roleDirection": false
},
{
"from": "MicroStrategy Dossier",
"to": "BI Data Model",
"label": "",
"style": "arrow",
"type": {
"id": "00000000-0000-0000-0000-120000000013"
},
"roleDirection": false
},
{
"from": "MicroStrategy Data Attribute",
"to": "Column",
"label": "",
"style": "arrow",
"type": {
"id": "00000000-0000-0000-0000-000000007069"
},
"roleDirection": false
},
{
"from": "MicroStrategy Dossier",
"to": "BI Data Model",
"label": "",
"style": "arrow",
"type": {
"id": "00000000-0000-0000-0000-120000000015"
},
"roleDirection": true
},
{
"from": "MicroStrategy Document",
"to": "BI Data Model",
"label": "",
"style": "arrow",
"type": {
"id": "00000000-0000-0000-0000-120000000015"
},
"roleDirection": true
},
{
"from": "MicroStrategy Report",
"to": "BI Data Model",
"label": "",
"style": "arrow",
"type": {
"id": "00000000-0000-0000-0000-120000000015"
},
"roleDirection": true
},
{
"from": "MicroStrategy Report",
"to": "BI Data Entity",
"label": "",
"style": "arrow",
"type": {
"id": "00000000-0000-0000-0000-000000007038"
},
"roleDirection": true
},
{
"from": "Column",
"to": "Table",
"label": "",
"style": "boxed",
"type": {
"id": "00000000-0000-0000-0000-000000007042"
},
"roleDirection": true
},
{
"from": "Table",
"to": "Schema",
"label": "",
"style": "boxed",
"type": {
"id": "00000000-0000-0000-0000-000000007043"
},
"roleDirection": false
},
{
"from": "Schema",
"to": "Database",
"label": "",
"style": "boxed",
"type": {
"id": "00000000-0000-0000-0000-000000007024"
},
"roleDirection": false
},
{
"from": "MicroStrategy Report",
"to": "Business Term",
"label": "",
"style": "arrow",
"type": {
"id": "00000000-0000-0000-0000-000000007021"
},
"roleDirection": false
},
{
"from": "MicroStrategy Report",
"to": "BI Data Entity",
"label": "",
"style": "arrow",
"type": {
"id": "00000000-0000-0000-0000-120000000013"
},
"roleDirection": false
}
],
"showOverview": false,
"enableFilters": true,
"showLabels": false,
"showFields": true,
"showLegend": true,
"showPreview": true,
"visitStrategy": "directed",
"layout": "HierarchyLeftRight",
"maxNodeLabelLength": 50,
"maxEdgeLabelLength": 30,
"layoutOptions": {
"compactGroups": false,
"componentArrangementPolicy": "topmost",
"edgeBends": true,
"edgeBundling": true,
"edgeToEdgeDistance": 5,
"minimumLayerDistance": "auto",
"nodeToEdgeDistance": 5,
"orthogonalRouting": true,
"preciseNodeHeightCalculation": true,
"recursiveGroupLayering": true,
"separateLayers": true,
"webWorkers": true,
"nodePlacer": {
"barycenterMode": true,
"breakLongSegments": true,
"groupCompactionStrategy": "none",
"nodeCompaction": false,
"straightenEdges": true
}
}
}
Overview and diagram view
The Looker scanner collects Looker metadata and sends it to the Collibra Data Lineage service. Collibra processes the metadata and creates new Looker assets and relations in Data Catalog. You can see them on the asset page overview or visualize them in a diagram or in a technical lineage.
- The assets have the same names as their counterparts in Looker. Full names and Display names cannot be changed in Data Catalog.
- Asset types are only created if you have all specific Looker and Data Catalog permissions.
- All Looker asset types are created in the same domain.
- Relations that were manually created between Looker assets and other assets via a relation type in the Looker operating model are deleted after a refresh of the Looker metadata.
The following image shows the relations between Looker asset types.
Harvested metadata per asset type
The following table shows the harvested Looker metadata for each Looker asset type. This table also shows the resource ID for each asset type and metadata.
|
Asset type |
Synchronized metadata |
Resource ID |
|---|---|---|
|
Looker Dashboard Resource ID: 00000000-0000-0000-0000-100000000013 |
Full name |
|
| Display name | ||
| Description | 00000000-0000-0000-0000-000000003114 | |
| Document creation date | 00000000-0000-0000-0000-000000000260 | |
| Document last accessed date |
00000000-0000-0000-0000-000000000268 |
|
| Favorites count |
00000000-0000-0000-0000-000000000269 |
|
|
Owner in source The only harvested metadata are email addresses. |
00000000-0000-0000-0000-200000000001 | |
| Technical Data Type | 00000000-0000-0000-0000-000000000219 | |
| URL | 00000000-0000-0000-0000-000000000258 | |
| Visit count |
00000000-0000-0000-0000-000000000264 |
|
| Business Dimension groups / is grouped into Report | 00000000-0000-0000-0000-120000000002 | |
| Report groups / is grouped into Report | 00000000-0000-0000-0000-120000000004 | |
| Report related to / is impacted by Business Asset | 00000000-0000-0000-0000-120000000006 | |
| Report uses / used in Report | 00000000-0000-0000-0000-120000000007 | |
|
Looker Data Set Resource ID: 00000000-0000-0000-0000-100000000017 |
Full name |
|
| Display name | ||
| Description | 00000000-0000-0000-0000-000000003114 | |
| Data Set contains / is part of Data Element |
00000000-0000-0000-0000-000000007062 |
|
| Technology Asset source system for / source system Data Asset | 00000000-0000-0000-0000-000000007050 | |
|
Looker Data Set Column Resource ID: 00000000-0000-0000-0000-100000000018 |
Full name |
|
| Display name | ||
| Description | 00000000-0000-0000-0000-000000003114 | |
| Data Set contains / is part of Data Element |
00000000-0000-0000-0000-000000007062 |
|
| Report Attribute sourced from / is source of Data Attribute | 00000000-0000-0000-0000-120000000010 | |
|
Looker Folder Resource ID: 00000000-0000-0000-0000-100000000012 |
Full name |
|
| Display name | ||
|
Document creation date |
00000000-0000-0000-0000-000000000260 | |
|
Owner in source The only harvested metadata are email addresses. |
00000000-0000-0000-0000-200000000001 | |
| BI Folder assembles / is assembled in BI Folder | 00000000-0000-0000-0000-120000000001 | |
| Business Dimension groups / is grouped into Report | 00000000-0000-0000-0000-120000000002 | |
| Server hosts / is hosted in Business Dimension | 00000000-0000-0000-0000-120000000000 | |
|
Looker Look Resource ID: 00000000-0000-0000-0000-100000000014 |
Full name |
|
| Display name | ||
| Description | 00000000-0000-0000-0000-000000003114 | |
| Document creation date | 00000000-0000-0000-0000-000000000260 | |
| Document last accessed date |
00000000-0000-0000-0000-000000000268 |
|
| Document modification date | 00000000-0000-0000-0000-000000000261 | |
| Favorites count |
00000000-0000-0000-0000-000000000269 |
|
|
Owner in source The only harvested metadata are email addresses. |
00000000-0000-0000-0000-200000000001 | |
| Report image | 00000000-0000-0000-0000-000000000262 | |
| URL | 00000000-0000-0000-0000-000000000258 | |
| Visit count |
00000000-0000-0000-0000-000000000264 |
|
| Business Dimension groups / is grouped into Report | 00000000-0000-0000-0000-120000000002 | |
| Report groups / is grouped into Report | 00000000-0000-0000-0000-120000000004 | |
| Report uses / used in Report | 00000000-0000-0000-0000-120000000007 | |
|
Looker Report Attribute Resource ID: 00000000-0000-0000-0000-100000000019 |
Full name |
|
| Display name | ||
|
Report Attribute contained in / contains Report |
00000000-0000-0000-0000-000000007058 | |
| Report Attribute sourced from / is source of Data Attribute | 00000000-0000-0000-0000-120000000010 | |
|
Looker Query Resource ID: 00000000-0000-0000-0000-100000000016 |
Full name |
|
| Display name | ||
|
URL |
00000000-0000-0000-0000-000000000258 | |
|
Business Dimension groups / is grouped into Report |
00000000-0000-0000-0000-120000000002 | |
| Report Attribute contained in / contains Report | 00000000-0000-0000-0000-000000007058 | |
|
Report uses / used in Report |
00000000-0000-0000-0000-120000000007 | |
|
Looker Tenant Resource ID: 00000000-0000-0000-0000-100000000011 |
Full name |
|
| Display name | ||
| Description | 00000000-0000-0000-0000-000000003114 | |
| Server hosts / is hosted in Business Dimension | 00000000-0000-0000-0000-120000000000 | |
| Technology Asset source system for / source system Data Asset | 00000000-0000-0000-0000-000000007050 | |
|
Looker Tile Resource ID: 00000000-0000-0000-0000-100000000015 |
Full name |
|
|
Display name |
||
| Business Dimension groups / is grouped into Report | 00000000-0000-0000-0000-120000000002 | |
| Report uses / used in Report | 00000000-0000-0000-0000-120000000007 |
Note The metadata that is shown on the assets' pages depends on the asset type's assignment. As a result, you might not see all harvested metadata on the asset's page by default.
Additional information
For the Owner in source attribute, the following rules apply:
- If the system creates a
- If the user who created a
Example of ingested Looker metadata
The following image shows an example structure after Looker ingestion.
In Collibra 2024.05, we launched a new user interface (UI) for Collibra Data Intelligence Platform! You can learn more about this latest UI in the UI overview.
Use the following options to see the documentation in the latest UI or in the previous, classic UI:
Recommended hierarchy within a domain
You can enable hierarchies for the domain in which your Looker assets were ingested. Doing so makes it easier to understand the relation between your Looker assets, when viewing the assets on the domain page.
Follow these steps to enable and configure the recommended hierarchy.
Steps
- Open the domain page of the relevant BI Catalog domain.
- On the content toolbar, click .
The Configure Hierarchy dialog box appears. - Select Enable Hierarchy.
- Select Multipath.
- Start typing and select each of the following relation types:
- Server hosts Business Dimension
- Business Dimension groups Report
- Report contains Report Attribute
- Technology Asset source system for Data Asset
- Data Set contains Data Element
- Data Attribute is source of Report Attribute
- Click Apply.
- In an asset view, if any asset is deleted, for example via synchronization or manual deletion, the view is recreated and the hierarchy is lost. In this case, you can again enable and configure the recommended hierarchy.
- When viewing the hierarchy for a community or domain, if the parent of a node that is in the community or domain belongs to a different community or domain, that node is not shown in the hierarchy.
Create a Looker operating model diagram view
You can create a Looker-specific diagram view, to visualize the operating model. The following procedure provides instruction on how to quickly create a new diagram view by copying and pasting the JSON code in the diagram view text editor.
Steps
- Open an asset page.
- Click the
Diagram tab.
The diagram is shown in the default diagram view. - Click to add a new view.
- Click the Text tab, to switch to the diagram view text editor.
- Click Show me the JSON code below this procedure, to expand the code.
- Click in the top-right of the expanded code, to copy the code.
The code is copied to your clipboard.
- Paste the code in diagram view text editor.
- Click Save.
- Edit the name and description of the diagram view, to suit your needs.
{
"nodes": [
{
"id": "Looker Tenant",
"type": {
"id": "00000000-0000-0000-0000-100000000011"
}
},
{
"id": "Looker Folder",
"type": {
"id": "00000000-0000-0000-0000-100000000012"
}
},
{
"id": "Looker Look",
"type": {
"id": "00000000-0000-0000-0000-100000000014"
}
},
{
"id": "Looker Dashboard",
"type": {
"id": "00000000-0000-0000-0000-100000000013"
}
},
{
"id": "Looker Query",
"type": {
"id": "00000000-0000-0000-0000-100000000016"
},
"layoutRegion": "flow"
},
{
"id": "Looker Tile",
"type": {
"id": "00000000-0000-0000-0000-100000000015"
}
},
{
"id": "Looker Data Set",
"type": {
"id": "00000000-0000-0000-0000-100000000017"
}
},
{
"id": "Looker Data Set Column",
"type": {
"id": "00000000-0000-0000-0000-100000000018"
}
},
{
"id": "Looker Report Attribute",
"type": {
"id": "00000000-0000-0000-0000-100000000019"
}
}
],
"edges": [
{
"from": "Looker Tenant",
"to": "Looker Folder",
"label": "",
"style": "arrow",
"type": {
"id": "00000000-0000-0000-0000-120000000000"
},
"roleDirection": true
},
{
"from": "Looker Folder",
"to": "Looker Query",
"label": "",
"type": {
"id": "00000000-0000-0000-0000-120000000002"
},
"roleDirection": true
},
{
"from": "Looker Folder",
"to": "Looker Look",
"label": "",
"style": "arrow",
"type": {
"id": "00000000-0000-0000-0000-120000000002"
},
"roleDirection": true
},
{
"from": "Looker Folder",
"to": "Looker Dashboard",
"label": "",
"style": "arrow",
"type": {
"id": "00000000-0000-0000-0000-120000000002"
},
"roleDirection": true
},
{
"from": "Looker Folder",
"to": "Looker Tile",
"label": "",
"style": "arrow",
"type": {
"id": "00000000-0000-0000-0000-120000000002"
},
"roleDirection": true
},
{
"from": "Looker Query",
"to": "Looker Look",
"label": "",
"style": "boxing",
"type": {
"id": "00000000-0000-0000-0000-120000000004"
},
"roleDirection": true
},
{
"from": "Looker Dashboard",
"to": "Looker Tile",
"label": "",
"style": "boxing",
"type": {
"id": "00000000-0000-0000-0000-120000000004"
},
"roleDirection": true
},
{
"from": "Looker Dashboard",
"to": "Looker Look",
"label": "",
"style": "arrow",
"type": {
"id": "00000000-0000-0000-0000-120000000007"
},
"roleDirection": true
},
{
"from": "Looker Query",
"to": "Looker Tile",
"label": "",
"style": "arrow",
"type": {
"id": "00000000-0000-0000-0000-120000000007"
},
"roleDirection": true
},
{
"from": "Looker Folder",
"to": "Looker Folder",
"label": "",
"style": "arrow",
"type": {
"id": "00000000-0000-0000-0000-120000000001"
},
"roleDirection": true
},
{
"from": "Looker Tenant",
"to": "Looker Data Set",
"label": "",
"style": "arrow",
"type": {
"id": "00000000-0000-0000-0000-000000007050"
},
"roleDirection": true
},
{
"from": "Looker Data Set",
"to": "Looker Data Set Column",
"label": "",
"style": "boxing",
"type": {
"id": "00000000-0000-0000-0000-000000007062"
},
"roleDirection": true
},
{
"from": "Looker Data Set Column",
"to": "Looker Report Attribute",
"label": "",
"style": "arrow",
"type": {
"id": "00000000-0000-0000-0000-120000000010"
},
"roleDirection": false
},
{
"from": "Looker Query",
"to": "Looker Report Attribute",
"label": "",
"style": "boxing",
"type": {
"id": "00000000-0000-0000-0000-000000007058"
},
"roleDirection": false
},
{
"from": "Looker Report Attribute",
"to": "Looker Report Attribute",
"label": "",
"style": "arrow",
"type": {
"id": "00000000-0000-0000-0000-120000000008"
},
"roleDirection": true
}
],
"showOverview": false,
"enableFilters": true,
"showLabels": true,
"showFields": true,
"showLegend": true,
"showPreview": true,
"visitStrategy": "directed",
"layout": "HierarchyLeftRight",
"maxNodeLabelLength": 50,
"maxEdgeLabelLength": 30,
"layoutOptions": {
"compactGroups": false,
"componentArrangementPolicy": "topmost",
"edgeBends": true,
"edgeBundling": true,
"edgeToEdgeDistance": 5,
"minimumLayerDistance": "auto",
"nodeToEdgeDistance": 5,
"orthogonalRouting": true,
"preciseNodeHeightCalculation": true,
"recursiveGroupLayering": true,
"separateLayers": true,
"webWorkers": true,
"nodePlacer": {
"barycenterMode": true,
"breakLongSegments": true,
"groupCompactionStrategy": "none",
"nodeCompaction": false,
"straightenEdges": true
}
}
}
Overview and diagram view
Synchronizing means refreshing the assets that are currently in Data Catalog as a result of a previous ingestion or synchronization job. After synchronizing SAP Datasphere Catalog, the assets in Collibra Data Catalog accurately reflect the metadata as it exists at the time of synchronization.
- The assets have the same names as their counterparts in SAP Analytics Cloud.
- Relations that were created between SAP Analytics Cloud assets and other assets via a relation type in the SAP Analytics Cloud operating model, are deleted upon synchronization. The same is true of any attribute types in the operating model that you add to SAP Analytics Cloud assets. To ensure that the characteristics you add to SAP Analytics Cloud assets are not deleted upon synchronization, be sure to use characteristics that are not part of the SAP Analytics Cloud operating model.
The following image shows the relations between SAP Analytics Cloud asset types.
You can easily recreate this diagram view in your Collibra environment. See Create a SAP Analytics Cloud operating model diagram view.
Harvested metadata per asset type
This table shows the metadata for each SAP Analytics Cloud asset type and the resource ID for each asset type and metadata.
|
Asset type |
Synchronized metadata |
Resource ID |
|---|---|---|
|
SAP Tenant Resource ID: 00000000-0000-0000-0000-100000000060 |
Description |
00000000-0000-0000-0000-000000003114 |
| Server hosts / is hosted in Business Dimension | 00000000-0000-0000-0000-120000000000 | |
|
SAP Container Resource ID: 00000000-0000-0000-0000-100000000061 |
Description | 00000000-0000-0000-0000-000000003114 |
|
BI Folder assembles / Is assembled in BI Folder |
00000000-0000-0000-0000-120000000001 | |
| Server hosts / is hosted in Business Dimension | 00000000-0000-0000-0000-120000000000 | |
|
SAC Folder Resource ID: 00000000-0000-0000-0000-100000000062 |
Description |
00000000-0000-0000-0000-000000003114 |
|
BI Folder assembles / is assembled in BI Folder |
00000000-0000-0000-0000-120000000001 | |
| Business Dimension groups / is grouped into Report | 00000000-0000-0000-0000-120000000002 | |
|
BI Folder contains / contained in Data Asset |
00000000-0000-0000-0000-120000000014 | |
|
SAC Story Resource ID: 00000000-0000-0000-0000-100000000063 |
Description |
00000000-0000-0000-0000-000000003114 |
| Description from Source | 00000000-0000-0000-0001-000500000074 | |
| Document creation date | 00000000-0000-0000-0000-000000000260 | |
| Document modification date | 00000000-0000-0000-0000-000000000261 | |
|
Owner in source The only harvested metadata are the email addresses of all Admins and one Owner. |
00000000-0000-0000-0000-200000000001 | |
| Business Dimension groups / is grouped into Report | 00000000-0000-0000-0000-120000000002 | |
| Report uses / used in Report | 00000000-0000-0000-0000-120000000007 | |
| Business Dimension groups / is grouped into Report | 00000000-0000-0000-0000-120000000002 | |
|
SAC Data Model Resource ID: 00000000-0000-0000-0000-100000000065 |
||
|
Description |
00000000-0000-0000-0000-000000003114 | |
| Description from Source | 00000000-0000-0000-0001-000500000074 | |
| Document creation date | 00000000-0000-0000-0000-000000000260 | |
|
Document modification date |
00000000-0000-0000-0000-000000000261 | |
|
Owner in source The only harvested metadata are the email addresses of all Admins and one Owner. |
00000000-0000-0000-0000-200000000001 |
|
| Source Type | 00000000-0000-0000-0000-000000000230 | |
| BI Folder contains / contained in Data Asset | 00000000-0000-0000-0000-120000000014 | |
| Data Model contains / is part of Data Entity | 00000000-0000-0000-0000-000000007046 | |
| Data Asset is source for / source BI Report | 00000000-0000-0000-0000-120000000013 | |
| Data Asset groups / is grouped by Data Asset | 00000000-0000-0000-0000-000000007017 | |
|
SAC Data Attribute Resource ID: 00000000-0000-0000-0000-100000000067 |
Description |
00000000-0000-0000-0000-000000003114 |
| Role in Report | 00000000-0000-0000-0000-000000000266 | |
| Source Type | 00000000-0000-0000-0000-000000000230 | |
| Data Entity contains / is part of Data Attribute | 00000000-0000-0000-0000-000000007047 | |
| Data Element targets / sources Data Element | 00000000-0000-0000-0000-000000007069 | |
| Data Asset is source for / source BI Report | 00000000-0000-0000-0000-120000000013 | |
| Data Asset groups / is grouped by Data Asset | 00000000-0000-0000-0000-000000007017 |
Example of ingested SAP Analytics Cloud metadata
The following image shows an example structure after synchronizing SAP Datasphere Catalog.
Recommended hierarchy within a domain
You can enable hierarchies for the domain (or domains) in which your SAP Analytics Cloud assets were ingested. Doing so makes it easier to understand the relation between your SAP Analytics Cloud assets, when viewing the assets on the domain page.
Follow these steps to enable and configure the recommended hierarchy.
Steps
- Open the domain page of the relevant BI Catalog domain.
- On the content toolbar, click .
The Configure Hierarchy dialog box appears. - Select Enable Hierarchy.
- Select Multipath.
- Start typing and select each of the following relation types:
- Technology Asset groups Technology Asset
- Storage Container assembles BI Folder
- Business Dimension groups Report
- BI Folder contains Data Asset
- BI Folder assembles BI Folder
- Report contains Report Attribute
- Data Asset groups Data Asset
- BI Report source Data Asset
- Click Apply.
- In an asset view, if any asset is deleted, for example via synchronization or manual deletion, the view is recreated and the hierarchy is lost. In this case, you can again enable and configure the recommended hierarchy.
- When viewing the hierarchy for a community or domain, if the parent of a node that is in the community or domain belongs to a different community or domain, that node is not shown in the hierarchy.
Create a SAP Analytics Cloud operating model diagram view
You can create a SAP Analytics Cloud-specific diagram view, to visualize the operating model. The following procedure provides instruction on how to quickly create a new diagram view by copying and pasting the JSON code in the diagram view text editor.
Steps
- Open an asset page.
- Click the
Diagram tab.
The diagram is shown in the default diagram view. - Click to add a new view.
- Click the Text tab, to switch to the diagram view text editor.
- Click Show me the JSON code below this procedure, to expand the code.
- Click in the top-right of the expanded code, to copy the code.
The code is copied to your clipboard.
- Paste the code in diagram view text editor.
- Click Save.
- Edit the name and description of the diagram view, to suit your needs.
{
"nodes": [
{
"id": "SAP Tenant",
"type": {
"id": "00000000-0000-0000-0000-100000000060"
}
},
{
"id": "SAP Container",
"type": {
"id": "00000000-0000-0000-0000-100000000061"
}
},
{
"id": "SAC Folder",
"type": {
"id": "00000000-0000-0000-0000-100000000062"
},
"fields": []
},
{
"id": "SAC Data Model",
"type": {
"id": "00000000-0000-0000-0000-100000000065"
},
"fields": []
},
{
"id": "SAC Story",
"type": {
"id": "00000000-0000-0000-0000-100000000063"
},
"fields": []
},
{
"id": "SAC Data Attribute",
"type": {
"id": "00000000-0000-0000-0000-100000000067"
},
"fields": []
}
],
"edges": [
{
"from": "SAP Tenant",
"to": "SAP Container",
"label": "",
"style": "arrow",
"type": {
"id": "00000000-0000-0000-0000-000000007054"
},
"roleDirection": true
},
{
"from": "SAP Container",
"to": "SAC Folder",
"label": "",
"style": "arrow",
"type": {
"id": "00000000-0000-0000-0001-002600000006"
},
"roleDirection": true
},
{
"from": "SAC Folder",
"to": "SAC Data Model",
"label": "",
"style": "arrow",
"type": {
"id": "00000000-0000-0000-0000-120000000014"
},
"roleDirection": true
},
{
"from": "SAC Folder",
"to": "SAC Story",
"label": "",
"style": "arrow",
"type": {
"id": "00000000-0000-0000-0000-120000000002"
},
"roleDirection": true
},
{
"from": "SAC Story",
"to": "SAC Data Model",
"label": "",
"style": "arrow",
"type": {
"id": "00000000-0000-0000-0000-120000000013"
},
"roleDirection": false
},
{
"from": "SAC Folder",
"to": "SAC Folder",
"label": "",
"style": "boxing",
"type": {
"id": "00000000-0000-0000-0000-120000000001"
},
"roleDirection": true
},
{
"from": "SAC Data Model",
"to": "SAC Data Attribute",
"label": "",
"style": "arrow",
"type": {
"id": "00000000-0000-0000-0000-000000007017"
},
"roleDirection": true
}
],
"showOverview": false,
"enableFilters": true,
"showLabels": true,
"showFields": true,
"showLegend": true,
"showPreview": true,
"visitStrategy": "directed",
"layout": "HierarchyLeftRight",
"maxNodeLabelLength": 50,
"maxEdgeLabelLength": 30,
"layoutOptions": {
"compactGroups": false,
"componentArrangementPolicy": "topmost",
"edgeBends": true,
"edgeBundling": true,
"edgeToEdgeDistance": 5,
"minimumLayerDistance": "auto",
"nodeToEdgeDistance": 5,
"orthogonalRouting": true,
"preciseNodeHeightCalculation": true,
"recursiveGroupLayering": true,
"separateLayers": true,
"webWorkers": true,
"nodePlacer": {
"barycenterMode": true,
"breakLongSegments": true,
"groupCompactionStrategy": "none",
"nodeCompaction": false,
"straightenEdges": true
}
}
}
Overview and diagram view
The lineage harvester collects SQL Server Reporting Services (SSRS) metadata and sends it to the Collibra Data Lineage service. Collibra processes the metadata and creates new SSRS assets and relations in Data Catalog. You can see them on the asset page overview or visualize them in a diagram or in a technical lineage.
- The assets have the same names as their counterparts in SSRS and Power BI Report Server (PBRS). Full names and Names cannot be changed in Data Catalog.
- Assets ingested from SSRS and PBRS are called SSRS assets in Data Catalog, except for PBRS reports which are called Power BI Report assets.
- Asset types are only created if you have all specific Data Catalog permissions.
- All SSRS and PBRS assets are created in the same domain.
- Relations that were manually created between SSRS assets or PBRS assets and other assets via a relation type in the SSRS and PBRS operating model, are deleted after synchronizing the metadata.
The following image shows the relations between SSRS asset types and the Power BI Report asset type.
Harvested metadata per asset type
This table shows the harvested SSRS and PBRS metadata for each SSRS asset type and Power BI Report asset type, assuming you have the necessary subscriptions and configurations for a full ingestion. This table also shows the resource ID for each asset type and metadata.
|
Asset type |
Synchronized metadata |
Resource ID |
|---|---|---|
|
SSRS Column Resource ID: 00000000-0000-0000-0000-100000000029 |
Full name |
|
| Display name | ||
| Description | 00000000-0000-0000-0000-000000003114 | |
| Technical Data Type | 00000000-0000-0000-0000-000000000219 | |
| BI Data Model contains / is part of BI Data Attribute | 00000000-0000-0000-0000-000000007196 | |
| Data Element targets / sources Data Element | 00000000-0000-0000-0000-000000007069 | |
| Data Entity contains / is part of Data Attribute | 00000000-0000-0000-0000-000000007047 | |
|
SSRS Data Model Resource ID: 00000000-0000-0000-0000-100000000028 |
Full name |
|
| Display name | ||
| Certified | 00000000-0000-0000-0001-000500000001 | |
| Description | 00000000-0000-0000-0000-000000003114 | |
|
Document creation date |
00000000-0000-0000-0000-000000000260 | |
| Document modification date | 00000000-0000-0000-0000-000000000261 | |
| Document size | 00000000-0000-0000-0000-000000000259 | |
| Location | 00000000-0000-0000-0000-000000000203 | |
| URL | 00000000-0000-0000-0000-000000000258 | |
| Visible on server | 00000000-0000-0000-0000-000000000265 | |
|
BI Data Model contains / is part of BI Data Attribute |
00000000-0000-0000-0000-000000007196 | |
|
BI Folder contains / contained in Data Asset |
00000000-0000-0000-0000-120000000014 | |
| Data Asset is source for / sources BI report | 00000000-0000-0000-0000-120000000013 | |
| Data Entity is part of / contains Data Model | 00000000-0000-0000-0000-000000007046 | |
|
SSRS Folder Resource ID: 00000000-0000-0000-0000-100000000024 |
Full name |
|
| Display name | ||
| Description | 00000000-0000-0000-0000-000000003114 | |
|
Document creation date |
00000000-0000-0000-0000-000000000260 | |
| Document modification date | 00000000-0000-0000-0000-000000000261 | |
| Location | 00000000-0000-0000-0000-000000000203 | |
| URL | 00000000-0000-0000-0000-000000000258 | |
| Visible on server | 00000000-0000-0000-0000-000000000265 | |
| Business Dimension groups / is grouped into Report | 00000000-0000-0000-0000-120000000002 | |
|
BI Folder assembles / is assembled in BI Folder |
00000000-0000-0000-0000-120000000001 | |
|
BI Folder contains / contained in Data Asset |
00000000-0000-0000-0000-120000000014 | |
| Server hosts / is hosted in Business Dimension | 00000000-0000-0000-0000-120000000000 | |
|
SSRS KPI Resource ID: 00000000-0000-0000-0000-100000000026 |
Full name |
|
| Display name | ||
| Certified | 00000000-0000-0000-0001-000500000001 | |
| Description | 00000000-0000-0000-0000-000000003114 | |
|
Document creation date |
00000000-0000-0000-0000-000000000260 | |
| Document modification date | 00000000-0000-0000-0000-000000000261 | |
| Document size | 00000000-0000-0000-0000-000000000259 | |
| Location | 00000000-0000-0000-0000-000000000203 | |
| URL | 00000000-0000-0000-0000-000000000258 | |
| Visible on server | 00000000-0000-0000-0000-000000000265 | |
| Business Dimension groups / is grouped into Report | 00000000-0000-0000-0000-120000000002 | |
|
Data Asset is source for / sources BI Report |
00000000-0000-0000-0000-120000000013 | |
|
Report Attribute contained in / contains Report |
00000000-0000-0000-0000-000000007058 | |
| Report related to / impacted by Business Asset | 00000000-0000-0000-0000-120000000006 | |
|
SSRS Parameter Resource ID: 00000000-0000-0000-0000-100000000027 |
Full name |
|
| Display name | ||
|
Description |
00000000-0000-0000-0000-000000003114 | |
| Business Asset represents / represented by Data Asset | 00000000-0000-0000-0000-000000007038 | |
| Report Attribute contained in / contains Report | 00000000-0000-0000-0000-000000007058 | |
|
Report Attribute sourced from / is source of Data Attribute |
00000000-0000-0000-0000-120000000010 | |
|
SSRS Report Resource ID: 00000000-0000-0000-0000-100000000025 |
Full name |
|
| Display name | ||
| Certified | 00000000-0000-0000-0001-000500000001 | |
| Description | 00000000-0000-0000-0000-000000003114 | |
|
Document creation date |
00000000-0000-0000-0000-000000000260 | |
| Document modification date | 00000000-0000-0000-0000-000000000261 | |
| Document size | 00000000-0000-0000-0000-000000000259 | |
| Location | 00000000-0000-0000-0000-000000000203 | |
| URL | 00000000-0000-0000-0000-000000000258 | |
| Visible on server | 00000000-0000-0000-0000-000000000265 | |
| Business Dimension groups / is grouped into Report | 00000000-0000-0000-0000-120000000002 | |
|
Data Asset is source for / sources BI Report |
00000000-0000-0000-0000-120000000013 | |
|
Report related to / impacted by Business Asset |
00000000-0000-0000-0000-120000000006 | |
| Report uses / used in Report | 00000000-0000-0000-0000-120000000007 | |
|
SSRS Server Resource ID: 00000000-0000-0000-0000-100000000023 |
Full name |
|
| Display name | ||
| Description | 00000000-0000-0000-0000-000000003114 | |
| Server hosts / is hosted in Business Dimension | 00000000-0000-0000-0000-120000000000 | |
|
SSRS Table Resource ID: 00000000-0000-0000-0000-100000000030 |
Full name |
|
|
Display name |
||
| Description | 00000000-0000-0000-0000-000000003114 | |
| Data Entity contains / is part of Data Attribute | 00000000-0000-0000-0000-000000007047 | |
| Data Entity is part of / contains Data Model | 00000000-0000-0000-0000-000000007046 |
Example of ingested SSRS and PBRS metadata
The following image shows an example structure after SSRS and PBRS ingestion.
In Collibra 2024.05, we launched a new user interface (UI) for Collibra Data Intelligence Platform! You can learn more about this latest UI in the UI overview.
Use the following options to see the documentation in the latest UI or in the previous, classic UI:
Recommended hierarchy within a domain
You can enable hierarchies for the domain in which your SSRS assets were ingested. Doing so makes it easier to understand the relation between your SSRS assets, when viewing the assets on the domain page.
Follow these steps to enable and configure the recommended hierarchy.
Steps
- Open the domain page of the relevant BI Catalog domain.
- On the content toolbar, click .
The Configure Hierarchy dialog box appears. - Select Enable Hierarchy.
- Select Multipath.
- Start typing and select each of the following relation types:
- Server hosts Business Dimension
- Business Dimension groups Report
- BI Folder contains Data Asset
- Data Asset is source for BI Report
- Report contains Report Attribute
- BI Folder contains Data Asset
- BI Data Model contains BI Data Attribute
- Data Entity contains Data Attribute
- Click Apply.
- In an asset view, if any asset is deleted, for example via synchronization or manual deletion, the view is recreated and the hierarchy is lost. In this case, you can again enable and configure the recommended hierarchy.
- When viewing the hierarchy for a community or domain, if the parent of a node that is in the community or domain belongs to a different community or domain, that node is not shown in the hierarchy.
Create an SSRS and PBRS operating model diagram view
You can create a diagram view for SSRS and PBRS to visualize the operating model. Complete the following steps to create a new diagram view by copying and pasting the JSON code in the diagram view text editor.
Steps
- Open an asset page.
- Click the
Diagram tab.
The diagram is shown in the default diagram view. - Click to add a new view.
- Click the Text tab, to switch to the diagram view text editor.
- Click Show me the JSON code below this procedure, to expand the code.
- Click in the top-right of the expanded code, to copy the code.
The code is copied to your clipboard.
- Paste the code in diagram view text editor.
- Click Save.
- Edit the name and description of the diagram view, to suit your needs.
{
"nodes": [
{
"id": "SSRS Column",
"type": {
"id": "00000000-0000-0000-0000-100000000029"
}
},
{
"id": "SSRS Data Model",
"type": {
"id": "00000000-0000-0000-0000-100000000028"
}
},
{
"id": "SSRS Table",
"type": {
"id": "00000000-0000-0000-0000-100000000030"
}
},
{
"id": "SSRS KPI",
"type": {
"id": "00000000-0000-0000-0000-100000000026"
}
},
{
"id": "SSRS Parameter",
"type": {
"id": "00000000-0000-0000-0000-100000000027"
}
},
{
"id": "SSRS Folder",
"type": {
"id": "00000000-0000-0000-0000-100000000024"
}
},
{
"id": "Power BI Report",
"type": {
"id": "00000000-0000-0000-0000-100000000006"
}
},
{
"id": "SSRS Report",
"type": {
"id": "00000000-0000-0000-0000-100000000025"
}
},
{
"id": "SSRS Server",
"type": {
"id": "00000000-0000-0000-0000-100000000023"
}
},
{
"id": "Column",
"type": {
"id": "00000000-0000-0000-0000-000000031008"
}
},
{
"id": "Table",
"type": {
"id": "00000000-0000-0000-0000-000000031007"
}
},
{
"id": "Schema",
"type": {
"id": "00000000-0000-0000-0001-000400000002"
}
},
{
"id": "Database",
"type": {
"id": "00000000-0000-0000-0000-000000031006"
}
}
],
"edges": [
{
"from": "SSRS Data Model",
"to": "SSRS Column",
"label": "",
"style": "arrow",
"type": {
"id": "00000000-0000-0000-0000-000000007196"
},
"roleDirection": true
},
{
"from": "SSRS Table",
"to": "SSRS Column",
"label": "",
"style": "arrow",
"type": {
"id": "00000000-0000-0000-0000-000000007047"
},
"roleDirection": true
},
{
"from": "SSRS Data Model",
"to": "SSRS Table",
"label": "",
"style": "arrow",
"type": {
"id": "00000000-0000-0000-0000-000000007046"
},
"roleDirection": true
},
{
"from": "SSRS Data Model",
"to": "SSRS KPI",
"label": "",
"style": "arrow",
"type": {
"id": "00000000-0000-0000-0000-120000000013"
},
"roleDirection": true
},
{
"from": "SSRS KPI",
"to": "SSRS Parameter",
"label": "",
"style": "arrow",
"type": {
"id": "00000000-0000-0000-0000-120000000014"
},
"roleDirection": true
},
{
"from": "SSRS Folder",
"to": "SSRS Data Model",
"label": "",
"style": "arrow",
"type": {
"id": "00000000-0000-0000-0000-120000000014"
},
"roleDirection": true
},
{
"from": "SSRS Folder",
"to": "Power BI Report",
"label": "",
"style": "arrow",
"type": {
"id": "00000000-0000-0000-0000-120000000002"
},
"roleDirection": true
},
{
"from": "SSRS Folder",
"to": "SSRS Report",
"label": "",
"style": "arrow",
"type": {
"id": "00000000-0000-0000-0000-120000000002"
},
"roleDirection": true
},
{
"from": "SSRS Folder",
"to": "SSRS KPI",
"label": "",
"style": "arrow",
"type": {
"id": "00000000-0000-0000-0000-120000000004"
},
"roleDirection": true
},
{
"from": "SSRS Report",
"to": "SSRS Data Model",
"label": "",
"style": "arrow",
"type": {
"id": "00000000-0000-0000-0000-120000000013"
},
"roleDirection": false
},
{
"from": "SSRS Column",
"to": "Column",
"label": "",
"style": "arrow",
"type": {
"id": "00000000-0000-0000-0000-000000007069"
},
"roleDirection": false
},
{
"from": "Column",
"to": "Table",
"label": "",
"style": "boxed",
"type": {
"id": "00000000-0000-0000-0000-000000007042"
},
"roleDirection": true
},
{
"from": "Table",
"to": "Schema",
"label": "",
"style": "boxed",
"type": {
"id": "00000000-0000-0000-0000-000000007043"
},
"roleDirection": false
},
{
"from": "Schema",
"to": "Database",
"label": "",
"style": "boxed",
"type": {
"id": "00000000-0000-0000-0000-000000007024"
},
"roleDirection": false
},
{
"from": "SSRS Server",
"to": "SSRS Folder",
"label": "",
"style": "arrow",
"type": {
"id": "00000000-0000-0000-0000-120000000000"
},
"roleDirection": true
},
{
"from": "SSRS Folder",
"to": "SSRS Folder",
"label": "",
"style": "arrow",
"type": {
"id": "00000000-0000-0000-0000-120000000001"
},
"roleDirection": true
}
],
"showOverview": false,
"enableFilters": true,
"showLabels": true,
"showFields": true,
"showLegend": true,
"showPreview": true,
"visitStrategy": "directed",
"layout": "HierarchyLeftRight",
"maxNodeLabelLength": 50,
"maxEdgeLabelLength": 30,
"layoutOptions": {
"compactGroups": false,
"componentArrangementPolicy": "topmost",
"edgeBends": true,
"edgeBundling": true,
"edgeToEdgeDistance": 5,
"minimumLayerDistance": "auto",
"nodeToEdgeDistance": 5,
"orthogonalRouting": true,
"preciseNodeHeightCalculation": true,
"recursiveGroupLayering": true,
"separateLayers": true,
"webWorkers": true,
"nodePlacer": {
"barycenterMode": true,
"breakLongSegments": true,
"groupCompactionStrategy": "none",
"nodeCompaction": false,
"straightenEdges": true
}
}
}