Versions Compared

Version Old Version 2 New Version Current
Changes made by

Dean Nguyen

Dean Nguyen

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Info

Power BI currently only supports lineage to Snowflake and Oracle.

  1. Create an application in Azure to access the PowerBI Dean Nguyen you can populate this with the existing guid you have for this.
    You will needFollow the instructions here [M - Admin] How to: Register an integration to Power BI to create a service principal that can access the Power BI API’s

    From these instructions you will need the following the complete the setup:

    1. The Tenant ID

    2. The Client ID

    3. The Client Secret

  2. Log in to K and go to Platform Settings > Integration / Sources

  3. Click on New Source and Select Power_bi

  4. Fill in the Power BI details
    Name: Give the Power BI source a name in K
    Host: Can be anything, generally we use app.powerbi.com
    PowerBI Tenant ID: from previous
    Timeout: Default is 10, sometimes it may take longer for the API to respond, so we recommend increasing it to 20

    Click Next

  5. Add your Client ID and Client Secret. Click Save. After a successful connection, click Next

  6. Click Finish Setup to complete the PowerBI configuration and save the landing directory path for reference

  7. To complete the setup to be runnable you will need to create a json file called mapping.json which is an empty json, and place it in the landing directory.

    Code Block
    languagejson
    {}


    Snowflake connections are automatically mapped inside he extraction process. If you know in advance of other types of Data Source Names referenced in PowerBI you may choose to populate the file in advance like so. Where myDSN is the Data Source Name as it appears in Power BI, host and database are those that are onboarded into K already or that you intend to onboard into K. Make sure the host and database values match onboarded or intended onboarding values.

    Code Block
    languagejson
    {
    "myDSN": {
        "host": "myhost",
        "database": "mydatabase"
    }
}


    If you don’t know any in advance, you will be able to request a log extract from KADA to tell you what DSNs were encountered by the extractor that it couldn’t map to populate it for the next run.

    Code Block
    languagetext
    DaxParser.parse_oracle: Encountered an unknown DSN myDSN that was not in the mapping.json

  8. Click on Edit Schedule in Sources and set up a schedule to extract PowerBI metadata



...