Versions Compared

Old Version 13

changes.mady.by.user Dean Nguyen

Saved on

compared with

New Version 14

changes.mady.by.user Dean Nguyen

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Scroll ignore
scroll-viewporttrue
scroll-pdftrue
scroll-officetrue
scroll-chmtrue
scroll-docbooktrue
scroll-eclipsehelptrue
scroll-htmltrue
scroll-epubtrue

Open in new tab

This page will walkthrough the setup of PowerBI in K.

...

  • 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

  • [Required for Power BI detailed lineage] Set Allow Service Principals to use Power BI APIs to Enabled

    • Select Specific Security Groups

      • Add the same AD group as the previous step

...

Info

This step is performed by the Power BI Admin

[Required for Detailed Lineage] Your K instance will now have access to the majority of your Power BI assets. To profile and catalog items such as Pages within a Report, or if your datasource connections use parameters, please add the KADA Power BI API Integration (created in Step 2) as a Member to each Power BI workspace you want it to profile.

...

Warning

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

  • If you noticed that some reports do not have lineage

Warning

Troubleshooting missing lineage

If you notice that some Report to Dataset lineage is missing despite following all the steps above, it will be because the Enhance admin APIs response with detailed metadata only works for datasets published AFTER turned this feature on. In order to get detailed metadata for lineage, you will need to republish each dataset again.

Image Added