BI tool operating models

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

Tip 

Select a BI tool.

Currently, the information is shown for:

 

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.

Note 
  • 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.

Note 
  • In Tableau, data objects descriptions can be inherited from other data objects. Any such inherited descriptions are not harvested.
  • In Tableau, worksheets and dashboards can be hidden, so that only admins can view them. During Tableau synchronization, hidden worksheets and dashboards are returned by the Tableau APIs, but the path to these data objects in Tableau is not included. Therefore:

    • The "URL" attribute on the asset pages of Tableau Dashboard and Tableau Worksheet assets is empty.
    • The "Visible on server" attribute is set to "false".

Asset type

Synchronized metadata

Public ID

Tableau Server

Resource ID: 00000000-0000-0000-0000-110000000005

Description

Description
Server hosts / is hosted in Business Dimension ServerHostsBusinessDimension
URL: The link to the data in Tableau Url

Tableau Site

Resource ID: 00000000-0000-0000-0000-110000000000

Description Description

BI Folder assembles / Is assembled in BI Folder

BIFolderAssemblesBIFolder
Server hosts / is hosted in Business Dimension ServerHostsBusinessDimension
URL: The link to the data in Tableau Url

Tableau Project

Resource ID: 00000000-0000-0000-0000-110000000001

Description

Description
Owner in Source

The only harvested metadata are email addresses. To harvest this metadata, you need to enable the Metadata API by setting the restOnly property in your lineage harvester configuration file to false.

For additional rules and limitations, see Additional information, further down in this topic.

OwnerInSource

BI Folder assembles / is assembled in BI Folder

BIFolderAssemblesBIFolder
Business Dimension groups / is grouped into Report BusinessDimensionGroupsReport

BI Folder contains / contained in Data Asset

BIFolderContainsDataAsset

Tableau Workbook

Resource ID: 00000000-0000-0000-0000-110000000002

Description

Description
Document creation date DocumentCreationDate
Document modification date DocumentModificationDate
Document size DocumentSize
Owner in Source

The only harvested metadata are email addresses. To harvest this metadata, you need to enable the Metadata API by setting the restOnly property in your lineage harvester configuration file to false.

For additional rules and limitations, see Additional information, further down in this topic.

OwnerInSource
URL: The link to the data in Tableau Url

Visits count

This is the amount of times the workbook was viewed in Tableau.

VisitsCount
Report groups / is grouped into Report ReportGroupsReport
Tableau Workbook contains / contained in Tableau Data Model TableauWorkbookContainsTableauDataModel
Business Dimension groups / is grouped into Report BusinessDimensionGroupsReport

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 DocumentCreationDate

Document modification date

DocumentModificationDate
Owner in Source

The only harvested metadata are email addresses. To harvest this metadata, you need to enable the Metadata API by setting the restOnly property in your lineage harvester configuration file to false.

For additional rules and limitations, see Additional information, further down in this topic.

OwnerInSource

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.
ReportImage
URL: The link to the data in Tableau Url
Visible on server VisibleOnServer

Visits count

This is the amount of times the dashboard was viewed in Tableau.

VisitsCount
Report groups / is grouped into Report ReportGroupsReport
Report uses / used in Data Attribute ReportUsesDataAttribute
Report uses / used in Report ReportUsesReport

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 DocumentCreationDate

Document modification date

DocumentModificationDate

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.
ReportImage
URL: The link to the data in Tableau Url
Visible on server VisibleOnServer

Visits count

This is the amount of times the worksheet was viewed in Tableau.

VisitsCount
Report groups / is grouped into Report ReportGroupsReport

Report uses / used in Data Attribute

ReportUsesDataAttribute
Report uses / used in Report ReportUsesReport

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

Description

Calculation Rule

CalculationRule
Data Type: The data type of a data asset, as it is declared by the data source. DataType
Role in Report RoleInReport
BI Data Model contains / is part of BI Data Attribute BIDataModelContainsBIDataAttribute
Data Element targets / sources Data Element DataElementTargetsDataElement

Report uses / used in Data Attribute

ReportUsesDataAttribute

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

Description

Certified

Note Certification is only possible for published Tableau data sources.

Certified

Document creation date

DocumentCreationDate

Document modification date

DocumentModificationDate

Original Name: The name of the data source in Tableau

OriginalName
Owner in Source

The only harvested metadata are email addresses. To harvest this metadata, you need to enable the Metadata API by setting the restOnly property in your lineage harvester configuration file to false.

For additional rules and limitations, see Additional information, further down in this topic.

OwnerInSource
BI Data Model contains / is part of BI Data Attribute BIDataModelContainsBIDataAttribute
Business Dimension source / is source of System BusinessDimensionSourceSystem
Tableau Workbook contains / contained in Tableau Data Model TableauWorkbookContainsTableauDataModel
Data Asset contained in / contains BI Folder BIFolderContainsDataAsset

Additional information

For the Owner in source attribute, the following rules apply:

  • If the system creates a Tableau data object and the Tableau data object does not have a user ID, the Owner in source attribute is shown as System on the asset page.
  • If the user who created a Tableau data object no longer exists, the Owner in source attribute is shown as empty on the asset page.

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.

Important 

In Collibra 2024.05, we launched a new user interface (UI) for Collibra 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

  1. Open the domain page of the relevant BI Catalog domain.
  2. On the content toolbar, click .
    The Configure Hierarchy dialog box appears.
  3. Select Enable Hierarchy.
  4. Select Multipath.
  5. 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
  6. Click Apply.

Note 
  • 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

  1. Open an asset page.
  2. Click the Diagram tab.
    The diagram is shown in the default diagram view.
  3. Click to add a new view.
  4. Click the Text tab, to switch to the diagram view text editor.
  5. Click Show me the JSON code below this procedure, to expand the code.
  6. Copy and paste the code in the diagram view text editor.
  7. Click Save.
  8. Edit the name and description of the diagram view, to suit your needs.

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.

Note 
  • 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.

Asset type

Synchronized metadata

Public ID

Power BI Capacity

Resource ID: 00000000-0000-0000-0000-100000000002

Full name

 
Display name  
Server hosts / is hosted in Business Dimension ServerHostsBusinessDimension
BI Folder assembles / is assembled in BI Folder BIFolderAssemblesBIFolder

Power BI Column

Resource ID: 00000000-0000-0000-0000-100000000008

Full name

 
Display name  
Description Description
Calculation Rule CalculationRule
Role in Report RoleInReport
Technical Data Type TechnicalDataType
BI Data Model contains / is part of BI Data Attribute BIDataModelContainsBIDataAttribute
Data Element targets / sources Data Element DataElementTargetsDataElement
Data Entity contains / is part of Data Attribute DataEntityContainsDataAttribute

Power BI Dashboard

Resource ID: 00000000-0000-0000-0000-100000000004

Full name

 
Display name  

URL

Note If the dashboard is part of an app in Power BI, the URL on the asset page links to the dashboard in the Power BI app.

Url
Data Asset is source for / sources for BI Report DataAssetIsSourceForBIReport

Report uses / used in Report

ReportUsesReport
Report related to / is impacted by Business Asset ReportRelatedToBusinessAsset

Power BI Data Flow

Resource ID: 00000000-0000-0000-0000-100000000010

Note Collibra Data Lineage supports data flows, but not streaming data flows. In this context, streaming means that the data is not saved in Power BI; therefore, lineage cannot be created.

Full name

 

Display name

 

Description

Description

Owner in Source

The only harvested metadata are the email addresses of all Admins and one Owner.

OwnerInSource

BI Folder contains / contained in Data Asset

BIFolderContainsDataAsset

Data Entity is part of / contains Data Model

DataEntityIsPartOfDataModel

BI Data Model is source for / sources BI Data Model

BIDataModelIsSourceForBIDataModel

Power BI Data Mart

Resource ID: 00000000-0000-0000-0000-100000000052

Full name

 

Display name

 
Certified

Certified

Document modification date

DocumentModificationDate

URL

Url

Owner in source

The only harvested metadata are email addresses.

OwnerInSource

BI Folder contains / contained in Data Asset

BIFolderContainsDataAsset

Data Entity is part of / contains Data Model

DataEntityIsPartOfDataModel

BI Data Model is source for / sources BI Data Model

BIDataModelIsSourceForBIDataModel

Power BI Data Model

Resource ID: 00000000-0000-0000-0000-100000000007

Full name

 
Display name  
Certified

Certified

Description Description

Owner in source

The only harvested metadata are email addresses.

OwnerInSource

BI Folder contains / contained in Data Asset

BIFolderContainsDataAsset

Data Asset is source for / sources BI report

DataAssetIsSourceForBIReport

Data Entity is part of / contains Data Model

DataEntityIsPartOfDataModel

BI Data Model is source for / sources BI Data Model

BIDataModelIsSourceForBIDataModel

Power BI Report

Resource ID: 00000000-0000-0000-0000-100000000006

Full name

 

Display name

 
Certified

Certified

Description

Description

Owner in Source

The only harvested metadata are the email addresses of all Admins and one Owner.

OwnerInSource

Source type

SourceType

URL

Note If the report is part of an app in Power BI, the URL on the asset page links to the report in the Power BI app.

Url
Business Dimension groups / is grouped into Report BusinessDimensionGroupsReport
Data Asset is source for / sources BI Report DataAssetIsSourceForBIReport

Report related to / is impacted by Business Asset

ReportRelatedToBusinessAsset

Report uses / used in Report

ReportUsesReport

Power BI Server

Resource ID: 00000000-0000-0000-0000-100000000001

Full name

 
Display name  
Server hosts / is hosted in Business Dimension ServerHostsBusinessDimension

Power BI Table

Resource ID: 00000000-0000-0000-0000-100000000009

Full name

 

Display name

 
Description Description
Calculation Rule CalculationRule
Data Entity contains / is part of Data Attribute DataEntityContainsDataAttribute
Data Entity is part of / contains Data Model DataEntityIsPartOfDataModel

Power BI Tile

Resource ID: 00000000-0000-0000-0000-100000000005

Full name

 

Display name

 
URL Url
Business Dimension groups / is grouped into Report BusinessDimensionGroupsReport
Data Asset is source for / sources BI Report DataAssetIsSourceForBIReport
Report related to / is impacted by Business Asset ReportRelatedToBusinessAsset
Report uses / used in Report ReportUsesReport

Power BI Workspace

Resource ID: 00000000-0000-0000-0000-100000000003

Full name  
Display name  
Description Description
State State

Owner in source

The only harvested metadata are email addresses.

OwnerInSource
BI Folder assembles / is assembled in BI Folder BIFolderAssemblesBIFolder
BI Folder contains / contained in Data Asset BIFolderContainsDataAsset
Business Dimension groups / is grouped into Report BusinessDimensionGroupsReport

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 Power BI data object and the Power BI data object does not have a user ID, the Owner in source attribute is shown as System on the asset page.
  • If the user who created a Power BI data object no longer exists, the Owner in source attribute is shown as empty on the asset page.

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.

Important 

In Collibra 2024.05, we launched a new user interface (UI) for Collibra 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

  1. Open the domain page of the relevant BI Catalog domain.
  2. On the content toolbar, click .
    The Configure Hierarchy dialog box appears.
  3. Select Enable Hierarchy.
  4. Select Multipath.
  5. 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
  6. Click Apply.

Note 
  • 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

  1. Open an asset page.
  2. Click the Diagram tab.
    The diagram is shown in the default diagram view.
  3. Click to add a new view.
  4. Click the Text tab, to switch to the diagram view text editor.
  5. Click Show me the JSON code below this procedure, to expand the code.
  6. Copy and paste the code in the diagram view text editor.
  7. Click Save.
  8. Edit the name and description of the diagram view, to suit your needs.

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.

Note 
  • 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 cannot be created:
  • Between MicroStrategy Documents and MicroStrategy Dossiers.
  • Between MicroStrategy Documents and MicroStrategy Reports.

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.

Note The following folders in MicroStrategy are not included in the ingestion:
  • Object Templates
  • System Objects
  • Version Update History

Asset type Harvested MicroStrategy metadata in Data Catalog

Public ID

 MicroStrategy Data Attribute

Resource ID: 00000000-0000-0000-0000-100000000047

Description

Description

Source Type

SourceType

Technical Data Type

TechnicalDataType

Data Element targets / sources Data Element

DataElementTargetsDataElement

Data Entity contains / is part of Data Attribute

DataEntityContainsDataAttribute

Data Attribute used in / uses Report

ReportUsesDataAttribute

MicroStrategy Data Entity

Resource ID: 00000000-0000-0000-0000-100000000048

Description

Description

Source Type

SourceType

Data Entity contains / is part of Data Attribute

DataEntityContainsDataAttribute

Data Entity is part of / contains Data Model

DataEntityIsPartOfDataModel

Data Asset is source for / sources BI Report

DataAssetIsSourceForBIReport

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

Description

Certified

Certified

Owner in source

The only harvested metadata are email addresses.

OwnerInSource

Source Type

SourceType

BI Folder contains / contained in Data Asset BIFolderContainsDataAsset

Data Asset is source for / source BI Report

DataAssetIsSourceForBIReport

Data Model contains / is part of Data Entity

DataEntityIsPartOfDataModel

MicroStrategy Document

Resource ID: 00000000-0000-0000-0000-100000000049

Description

Description

Certified

Certified

Owner in source

The only harvested metadata are email addresses.

OwnerInSource

URL

Note You can specify the platform on which you run MicroStrategy, in your lineage harvester configuration file, to ensure the correct URL.

Url

Business Dimension groups / is grouped into Report

BusinessDimensionGroupsReport

BI Report contains / contained in BI Data Model

BIReportContainsBIDataModel

MicroStrategy Dossier

Resource ID: 00000000-0000-0000-0000-100000000043

Description

Description

Certified

Certified

Owner in source

The only harvested metadata are email addresses.

OwnerInSource

Business Dimension groups / is grouped into Report

BusinessDimensionGroupsReport
Report groups / is grouped into Report ReportGroupsReport

Report uses / used in Report

ReportUsesReport
BI Report source / is source for Data Asset DataAssetIsSourceForBIReport

MicroStrategy Folder

Resource ID: 00000000-0000-0000-0000-100000000042

Description

Description

BI Folder assembles / is assembled in BI Folder

BIFolderAssemblesBIFolder

Business Dimension groups / is grouped into Report

BusinessDimensionGroupsReport

BI Folder contains / contained in Data Asset

BIFolderContainsDataAsset

MicroStrategy Project

Resource ID: 00000000-0000-0000-0000-100000000041

Description

Description

BI Folder assembles / is assembled in BI Folder

BIFolderAssemblesBIFolder

Server hosts / is hosted in Business Dimension

ServerHostsBusinessDimension

MicroStrategy Report

Resource ID: 00000000-0000-0000-0000-100000000044

Description

Description

Certified

Certified

URL

Url

Owner in source

The only harvested metadata are email addresses.

OwnerInSource

Report groups / is grouped into Report

ReportGroupsReport

Business Dimension groups / is grouped into Report

BusinessDimensionGroupsReport

Data Asset is source for / sources BI Report

DataAssetIsSourceForBIReport

MicroStrategy Server

Resource ID: 00000000-0000-0000-0000-100000000040

Server hosts / is hosted in Business Dimension

ServerHostsBusinessDimension

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

  1. Open the domain page of the relevant BI Catalog domain.
  2. On the content toolbar, click .
    The Configure Hierarchy dialog box appears.
  3. Select Enable Hierarchy.
  4. Select Single path.
  5. 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
  6. Click Apply.
Note 
  • 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

  1. Open an asset page.
  2. Click the Diagram tab.
    The diagram is shown in the default diagram view.
  3. Click to add a new view.
  4. Click the Text tab, to switch to the diagram view text editor.
  5. Click Show me the JSON code below this procedure, to expand the code.
  6. Copy and paste the code in the diagram view text editor.
  7. Click Save.
  8. Edit the name and description of the diagram view, to suit your needs.

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.

Note 
  • 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

Public ID

Looker Dashboard

Resource ID: 00000000-0000-0000-0000-100000000013

Full name

 
Display name  
Description Description
Document creation date DocumentCreationDate
Document last accessed date

DocumentLastAccessedDate

Favorites count

FavoritesCount

Owner in source

The only harvested metadata are email addresses.

OwnerInSource
Technical Data Type TechnicalDataType
URL Url
Visit count

VisitCount

Business Dimension groups / is grouped into Report BusinessDimensionGroupsReport
Report groups / is grouped into Report ReportGroupsReport
Report related to / is impacted by Business Asset ReportRelatedToBusinessAsset
Report uses / used in Report ReportUsesReport

Looker Data Set

Resource ID: 00000000-0000-0000-0000-100000000017

Full name

 
Display name  
Description Description
Data Set contains / is part of Data Element

DataSetContainsDataElement

Technology Asset source system for / source system Data Asset TechnologyAssetSourceSystemForDataAsset

Looker Data Set Column

Resource ID: 00000000-0000-0000-0000-100000000018

Full name

 
Display name  
Description Description
Data Set contains / is part of Data Element

DataSetContainsDataElement

Report Attribute sourced from / is source of Data Attribute ReportAttributeSourcedFromDataAttribute

Looker Folder

Resource ID: 00000000-0000-0000-0000-100000000012

Full name

 
Display name  

Document creation date

DocumentCreationDate

Owner in source

The only harvested metadata are email addresses.

OwnerInSource
BI Folder assembles / is assembled in BI Folder BIFolderAssemblesBIFolder
Business Dimension groups / is grouped into Report BusinessDimensionGroupsReport
Server hosts / is hosted in Business Dimension ServerHostsBusinessDimension

Looker Look

Resource ID: 00000000-0000-0000-0000-100000000014

Full name

 
Display name  
Description Description
Document creation date DocumentCreationDate
Document last accessed date

DocumentLastAccessedDate

Document modification date DocumentModificationDate
Favorites count

FavoritesCount

Owner in source

The only harvested metadata are email addresses.

OwnerInSource
Report image ReportImage
URL Url
Visit count

VisitCount

Business Dimension groups / is grouped into Report BusinessDimensionGroupsReport
Report groups / is grouped into Report ReportGroupsReport
Report uses / used in Report ReportUsesReport

Looker Report Attribute

Resource ID: 00000000-0000-0000-0000-100000000019

Full name

 
Display name  
Data Element targets / sources Data Element DataElementTargetsDataElement

Report Attribute contained in / contains Report

ReportAttributeContainedInReport
Report Attribute sourced from / is source of Data Attribute ReportAttributeSourcedFromDataAttribute

Looker Query

Resource ID: 00000000-0000-0000-0000-100000000016

Full name

 
Display name  

URL

Url

Business Dimension groups / is grouped into Report

BusinessDimensionGroupsReport
Report Attribute contained in / contains Report ReportAttributeContainedInReport

Report uses / used in Report

ReportUsesReport

Looker Tenant

Resource ID: 00000000-0000-0000-0000-100000000011

Full name

 
Display name  
Description Description
Server hosts / is hosted in Business Dimension ServerHostsBusinessDimension
Technology Asset source system for / source system Data Asset TechnologyAssetSourceSystemForDataAsset

Looker Tile

Resource ID: 00000000-0000-0000-0000-100000000015

Full name

 

Display name

 
Business Dimension groups / is grouped into Report BusinessDimensionGroupsReport
Report uses / used in Report ReportUsesReport

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 Looker data object and the Looker data object does not have a user ID, the Owner in source attribute is shown as System on the asset page.
  • If the user who created a Looker data object no longer exists, the Owner in source attribute is shown as empty on the asset page.

Example of ingested Looker metadata

The following image shows an example structure after Looker ingestion.

Important 

In Collibra 2024.05, we launched a new user interface (UI) for Collibra 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

  1. Open the domain page of the relevant BI Catalog domain.
  2. On the content toolbar, click .
    The Configure Hierarchy dialog box appears.
  3. Select Enable Hierarchy.
  4. Select Multipath.
  5. 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
  6. Click Apply.

Note 
  • 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

  1. Open an asset page.
  2. Click the Diagram tab.
    The diagram is shown in the default diagram view.
  3. Click to add a new view.
  4. Click the Text tab, to switch to the diagram view text editor.
  5. Click Show me the JSON code below this procedure, to expand the code.
  6. Copy and paste the code in the diagram view text editor.
  7. Click Save.
  8. Edit the name and description of the diagram view, to suit your needs.

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.

Note 
  • 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 Description
Technical Data Type TechnicalDataType
BI Data Model contains / is part of BI Data Attribute BIDataModelContainsBIDataAttribute
Data Element targets / sources Data Element DataElementTargetsDataElement
Data Entity contains / is part of Data Attribute DataEntityContainsDataAttribute

SSRS Data Model

Resource ID: 00000000-0000-0000-0000-100000000028

Full name

 
Display name  
Certified Certified
Description Description

Document creation date

DocumentCreationDate
Document modification date DocumentModificationDate
Document size DocumentSize
Location Location
URL Url
Visible on server VisibleOnServer

BI Data Model contains / is part of BI Data Attribute

BIDataModelContainsBIDataAttribute

BI Folder contains / contained in Data Asset

BIFolderContainsDataAsset
Data Asset is source for / sources BI report DataAssetIsSourceForBIReport
Data Entity is part of / contains Data Model DataEntityIsPartOfDataModel

SSRS Folder

Resource ID: 00000000-0000-0000-0000-100000000024

Full name

 
Display name  
Description Description

Document creation date

DocumentCreationDate
Document modification date DocumentModificationDate
Location Location
URL Url
Visible on server VisibleOnServer
Business Dimension groups / is grouped into Report BusinessDimensionGroupsReport

BI Folder assembles / is assembled in BI Folder

BIFolderAssemblesBIFolder

BI Folder contains / contained in Data Asset

BIFolderContainsDataAsset
Server hosts / is hosted in Business Dimension ServerHostsBusinessDimension

SSRS KPI

Resource ID: 00000000-0000-0000-0000-100000000026

Full name

 
Display name  
Certified Certified
Description Description

Document creation date

DocumentCreationDate
Document modification date DocumentModificationDate
Document size DocumentSize
Location Location
URL Url
Visible on server VisibleOnServer
Business Dimension groups / is grouped into Report BusinessDimensionGroupsReport

Data Asset is source for / sources BI Report

DataAssetIsSourceForBIReport

Report Attribute contained in / contains Report

ReportAttributeContainedInReport
Report related to / impacted by Business Asset ReportRelatedToBusinessAsset

SSRS Parameter

Resource ID: 00000000-0000-0000-0000-100000000027

Full name

 
Display name  

Description

Description
Business Asset represents / represented by Data Asset BusinessAssetRepresentsDataAsset
Report Attribute contained in / contains Report ReportAttributeContainedInReport

Report Attribute sourced from / is source of Data Attribute

ReportAttributeSourcedFromDataAttribute

SSRS Report

Resource ID: 00000000-0000-0000-0000-100000000025

Full name

 
Display name  
Certified Certified
Description Description

Document creation date

DocumentCreationDate
Document modification date DocumentModificationDate
Document size DocumentSize
Location Location
URL Url
Visible on server VisibleOnServer
Business Dimension groups / is grouped into Report BusinessDimensionGroupsReport

Data Asset is source for / sources BI Report

DataAssetIsSourceForBIReport

Report related to / impacted by Business Asset

ReportRelatedToBusinessAsset
Report uses / used in Report ReportUsesReport

SSRS Server

Resource ID: 00000000-0000-0000-0000-100000000023

Full name

 
Display name  
Description Description
Server hosts / is hosted in Business Dimension ServerHostsBusinessDimension

SSRS Table

Resource ID: 00000000-0000-0000-0000-100000000030

Full name

 

Display name

 
Description Description
Data Entity contains / is part of Data Attribute DataEntityContainsDataAttribute
Data Entity is part of / contains Data Model DataEntityIsPartOfDataModel

Example of ingested SSRS and PBRS metadata

The following image shows an example structure after SSRS and PBRS ingestion.

Important 

In Collibra 2024.05, we launched a new user interface (UI) for Collibra 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

  1. Open the domain page of the relevant BI Catalog domain.
  2. On the content toolbar, click .
    The Configure Hierarchy dialog box appears.
  3. Select Enable Hierarchy.
  4. Select Multipath.
  5. 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
  6. Click Apply.

Note 
  • 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

  1. Open an asset page.
  2. Click the Diagram tab.
    The diagram is shown in the default diagram view.
  3. Click to add a new view.
  4. Click the Text tab, to switch to the diagram view text editor.
  5. Click Show me the JSON code below this procedure, to expand the code.
  6. Copy and paste the code in the diagram view text editor.
  7. Click Save.
  8. Edit the name and description of the diagram view, to suit your needs.