Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 5 Next »

This page will walkthrough the setup of PowerBI in K.

Power BI currently only supports lineage to Snowflake and Oracle.


Step 1) Enabling PowerBI Admin APIs to be accessible to an AD Group

This step is performed by the Power BI Admin

  • Open Power BI portal and navigate to Admin Portal in the top right hand navigation

  • Go to Tenant Settings and scroll to Admin API settings

  • Set Allow Service Principals to use read-only Power BI admin APIs to Enabled

  • Select Specific Security Groups

    • Add an AD group that is appropriate for managing this access. This is typically the Admin group for Power BI. If no appropriate group exists, contact your Azure AD admin to create a new security group.

    • Record this AD group for Step 2

  • Set Enhance admin API responses with detailed metadata to Enabled

    • Add the same AD group as the previous API Settings option

  • Set Enhance admin APIs responses with DAX and mashup expressions to Enabled

    • Add the same AD group as the previous API Settings option

Make sure you send the AD Group name to the Azure AD Admin so that they can complete the next step


Step 2) Registering PowerBI App in Azure AD

This step is performed by the Azure AD Admin

  • Log in to your company’s Azure Portal and open the Azure Active Directory page

  • Select App Registration in the side panel and click New registration

  • Complete the registration form

    • Name: Enter a name for the integration e.g. KADA Power BI API Integration

    • Supported account types: Select Accounts in this organisation directory only

    • Redirect URL: Add https://www.kada.ai

  • Click Register to complete the registration

  • Click on the newly created KADA Power BI API Integration App

  • Save the Application (client) ID and Directory (tenant) ID for use in a later step

  • Click on Endpoints and save the URL for OpenID Connect metadata document for use in a later step

  • Select Certificates & secrets in the side panel and click New client secret

  • Complete the new secret form and save the Secret ID for use in a later stope

  • Select API permissions in the side panel and check that that Microsoft.Graph - User.Read permission has been added

  • Return to the Azure Portal and select Group

  • Find the AD Group that was created in step 1 and click Members

  • Select Add Members and add KADA Power BI API Integration to the group as a Service Principal

Make sure you send the following information to the K Admin so that they can complete the next process.

  • Application (client) ID

  • Directory (tenant) ID

  • Secret ID


Step 3) Add PowerBI as a New Source

This step is performed by the K Admin

  • Select Platform Settings in the side bar

  • In the pop-out side panel, under Integrations click on Sources

  • Click Add Source and select Power_bi

  • Select Direct Connect and add your Power BI details and click Next

  • Fill in the Source Settings and click Save & Next

    • Name: Give the Power BI source a name in K

    • Host: Must be unique. You can use http://app.powerbi.com if you only have 1 instance of Power BI.

    • Timeout: Default is 10, sometimes it may take longer for the API to respond, so we recommend increasing it to 20

    • Add the Host/Mapping details. See this page for more details

  • Add Connection Details

    • Tenant ID: Add the Directory (tenant) ID copied from step 2

    • Client ID : Add the Application (client) ID copied from Step 2

    • Client Secret: Add the Secret ID copied from Step 2

  • Click Finish Setup

  • Save the Landing Directory for use in a later step


Step 4) Create a json file in the landing directory

  • Create a json file called mapping.json which is an empty json, and place it in the landing directory

{}

Snowflake connections are automatically mapped inside the 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.

{ "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.

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


Step 5) Schedule PowerBI source load

  • Select Platform Settings in the side bar

  • In the pop-out side panel, under Integrations click on Sources

  • Locate your new PowerBI Source and click on the Schedule Settings (clock) icon to set the schedule

Note that scheduling a source can take up to 15 minutes to propagate the change.


Step 6) Manually run an ad hoc load to test PowerbIsetup

  • Select Platform Settings in the side bar

  • In the pop-out side panel, under Platform Settings click on Batch Manager

  • In Source Load click Run

  • Select the name of the Source you created in Step 2 and click Run

  • After the source is triggered, the screen will change to the Monitor tab where you can see the progress of the job.

A manual source load will also require a manual run of

  • DAILY

  • GATHER_METRICS_AND_STATS

To load all metrics and indexes with the manually loaded metadata. These can be found in the Batch Manager page

 

Troubleshooting failed loads

  • If the job failed at the extraction step

    • Check the error. Contact KADA Support if required.

    • Rerun the source job

  • If the job failed at the load step, the landing folder failed directory will contain the file with issues.

    • Find the bad record and fix the file

    • Rerun the source job

  • No labels