1. Third Party Cookies
    1. Overview
    2. Password Reset
    1. System Notifications
    2. Data Manager Notifications
    1. Troubleshooting Load Times
    2. Cache Warming
    1. Updating License Key
    1. Web Accessibility
    1. Menu Tuning
    2. Cache Warming
    1. Password Settings

Coming Soon: Power BI Connection

Troubleshooting Power BI Access

When Everything is Working

Once you have established a Power BI connection and published Power BI dashboards and/or reports to Curator's navigation, the next step is to have users log in to begin consuming those dashboards and/or reports.

If everything is set up perfectly, the process should be:

  1. Log in to Curator using whatever authentication method is configured under Backend > Settings > Security > Authentication Settings.
  2. Log in to Power BI. Note: If you are already authenticated to Power BI or if you are using a SSO solution that supports it, this step may be so fast it is invisible to your users.
  3. Curator should render its navigation with all of the Curator content the user has access to based on the platform of origin (i.e. Tableau determines access to Tableau content, ThoughtSpot determines access to ThoughtSpot content, and Power BI determines access to Power BI content). Note: It is possible to further restrict access to content within Curator, but it is not possible to loosen access beyond what the platform of origin allows.

When Something Goes Wrong

If you've gone through all of the steps and you see other Curator content but all of the Power BI content is missing from the navigation, here are the steps you can take to troubleshoot.

Verify You Are Authenticated To Power BI from Curator

To verify you are actually authenticated to Power BI from Curator, you'll need to use Curator's frontend debug mode. This feature is typically disabled by default, so you'll need to enable it by navigating to Backend > Settings > Curator > Portal Settings > General tab > Debug Settings section (found below the Global Settings section), toggling on the Enable Frontend Debug setting, and saving.

Next, go to the frontend and append ?debug=1 to the URL. For example, if your Curator frontend is https://curator.yourcompany.com/ then the address you'll want to go to is https://curator.yourcompany.com/?debug=1.

You should see a debug bar show up at the bottom of the screen. Click on the Session tab and look for an entry under powerbi > user.

If there isn't one, then something happened during log in to prevent you from being authenticated to Power BI from Curator. To fix this, log out of Curator and log back in.

If your session has an unexpired powerbi > user entry, then you are authenticated to Power BI, but Power BI is telling Curator you don't have access to content there. Proceed to the next section to troubleshoot further.

Checking What Power BI is Telling Curator

Curator issues API calls to Power BI using your authenticated session. The major thing Curator is checking with these API calls is which dashboards and/or content you have access to.

To see what Power BI is responding with, you can enable the Power BI debug mode by navigating to Backend > Integrations > Connections > Click on your Power BI connection, toggling on the Debug Mode for Power BI setting, and save.

For good measure, go ahead and click on the Clear Cache button at the top right section of the screen to ensure Curator makes fresh API calls to Power BI.

Next, go back to Curator's frontend and refresh the page.

If the Power BI content still doesn't show up in the navigation as expected, then navigate to Backend > Settings > Logs > Event Logs and look for the API calls being made to Power BI. Click on each entry to view the details. It's unlikely these will be obvious or intuitive, so feel free to see these details to Curator support.

The fix for your situation will be highly dependent on what the API is telling Curator. In the meantime, you can verify your user has access to the Power BI workspace and dashboard/report in question.