Add the Technical Lineage for Power BI capability to the Edge site

After you create a connection to Power BI, you can add the Technical Lineage for Power BI capability.

Requirements and permissions

A global role that has the following global permissions:

  • System administration
  • Manage connections and capabilities, for example Edge integration engineer.
  • Register profiling information

Steps

  1. Open an Edge site.
    1. On the main menu, click , and then click Settings.
      The Settings page opens.
    2. In the tab pane, click Edge.
      The Sites tab opens and shows a table with an overview of the Edge sites.
    3. In the table, click the name of the Edge site whose status is Healthy.
      The Edge site page opens.
  2. In the Capabilities section, click Add capability.
    The Add capability page appears.
  3. Enter the required information.
    FieldDescriptionRequired

    Capability

    This section contains general information about the capability.

    Name

    The name of the Edge capability.

    Yes

    Description

    The description of the Edge capability.

    No

    Capability template

    The capability template. The value that you select in this field determines which sections appear on the page.

    In the drop-down list, select Technical Lineage for Power BI.

    Yes

    Main Properties

    The required custom properties are based on the selected capability template.

    Source ID

    The connection to the data source.

    Yes

    Power BI connection

    The Power BI connection that you created for ingestion in Data Catalog.

    Tip Select the name that you provided in the Name field when you created a connection to Power BI.

    Yes

    API URL

    The API URL of your Power BI service.

    Note This field is only relevant for US government customers.

    The default value is https://api.powerbi.com.

    		 No
    Scope

    Optional property that is intended only for customers with a different scope, such as Chinese tenants.

    Example https://analysis.chinacloudapi.cn/powerbi/api/.default

    scope
    Domain ID

    The unique reference ID of the domain in Collibra Data Intelligence Cloud in which you want to ingest the Power BI assets.

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

    		 Yes
    Source configuration

    This field allows you to provide JSON code for database mapping, workspace filtering and specifying the name of a System asset in Collibra.

    Tip If you previously integrated Power BI via the lineage harvester, you can copy and paste in this field the JSON code from your Power BI <source ID> configuration file.

    • Specify the name of a database, on which server the database is running, and optionally, the name of the schema.
    • Configure workspace filtering.
      Tip We highly recommend that you read through Filtering Power BI workspaces for important information and guidance before configuring your filters.
    • If useCollibraSystemName in the lineage harvester configuration file is set to true, use the collibraSystemName property to specify the system name of databases in Power BI. Collibra Data Lineage uses the system names to match the structure of databases in Power BI to assets in Data Catalog.
    		No

    Custom Properties

    This section identifies to which Collibra Data Lineage service instance you want to upload the Power BI metadata.

    techlinKey

    The unique API key to connect to the Collibra Data Lineage service instance.

    A unique user key is needed for each Collibra environment. If you're not sure what your user key is, please contact your Collibra Customer Success Manager.

    Warning This section applies only to US government customers.

    No

    techlinHost

    The URL of he Collibra Data Lineage service instance to which you want to upload Power BI metadata, for example "techlin-gcp-eu.collibra.com".

    Warning This section applies only to US government customers.

    No

    Advanced Properties

    This section contains the advanced properties for creating a technical lineage.

    Delete Raw Metadata After Processing

    Metadata is harvested and uploaded in a ZIP file to a Collibra Data Lineage service instance, for processing.

    Use this optional property to specify whether or not the raw metadata should be deleted after it has been processed.

    If you select this option, the raw metadata is deleted after processing. If you don't select this option, it is stored in an Amazon S3 bucket.

    		 
    Analyze Only

    This option determines whether to only load and analyze the source data on the Collibra Data Lineage service instances.

    When you select this option, the technical lineage of the data source is not created during the synchronization of the capability. Selecting this option is equivalent to entering the load-sources and analyze command with a source specified when you use the lineage harvester.

    This option is not enabled by default.

    You can use this option to control when to start full synchronization of data sources. For example if you have three data sources, A, B, and C, you can synchronize the data sources as follows:

    • During weekdays, synchronize data sources A and B with the Analyze Only checkbox selected in the capabilities. Collibra Data Lineage only loads and analyzes data sources A and B without synchronizing the technical lineage.
    • On the weekend, synchronize data source C without selecting the Analyze Only checkbox in the capability. Collibra Data Lineage synchronizes the technical lineage for all data sources including A, B, and C.

    No

    Active

    The option determines whether to include or remove the technical lineage of the data source.

    Select this option to include the technical lineage of this data source.

    Clear the checkbox to exclude the technical lineage of this data source.

    		 No
  4. Click Create.
    The Edge site connects to your data source.

What's next?

Synchronize the Power BI technical lineage.