Skip to content
  • There are no suggestions because the search field is empty.

Power BI Troubleshooting

Learn how to troubleshoot and resolve common Power BI integration issues like API limits, access errors, and connector visibility problems.

TABLE OF CONTENTS

429 Too Many Requests Error

This error occurs when you exceed the Precoro API limits due to excessive queries from Power BI. It typically happens when queries lack filters, causing Power BI to pull an excessive amount of data.

429 Error

Solution:

  • Wait for the API limit to reset, then execute targeted queries.
  • Set up incremental data updates in Power BI to reduce the number of queries.

Access to the Resource is Forbidden Error

This error occurs when authorization credentials (email and token) are entered incorrectly during the company connection process.

Access to Resource is Forbidden

Access Forbidden

Solution:

  • Reconnect using the correct email and API token.
  • Make sure the credentials belong to a user with access to the relevant company in Precoro.

Refer to the Using API in Precoro article for detailed token generation instructions.

Connector Not Displayed in the List of Available Ones

This issue can occur if:

  • The connector file is in the wrong folder. Ensure the path is exactly:
    C:\Users\[userName]\Documents\Power BI Desktop\Custom Connectors\.
  • Power BI was downloaded from the app store. Subsequently, folder names and paths may differ, causing compatibility issues.

Solution:

Data Sources Not Saved, Requiring Reintegration Each Time

This happens when you’re not logged into your Power BI account.

Solution:

  • Create an official Power BI account by registering on their website.
  • Log into your account using the desktop version of Power BI. This way, all configurations will be saved, eliminating the need to recreate reports.

Sign In.

Unable to Determine the Data Source Due to Unknown Functions 

This error occurs if the Precoro Power BI custom connector is not activated in the On-Premises Data Gateway application. Due to this, the Precoro.Company function included in the custom connector can't be recognized.

Solution:

  1. Locate the folder where the On-Premises Data Gateway was installed. The standard path is C:\Program Files (x86)\On-premises data gateway

  2. Create a folder named Custom Connectors inside that directory.

  3. Place the .mez connector file provided by your CSM manager (as described here) into the Custom Connectors folder.

  4. In the On-Premises Data Gateway application, go to the Connectors tab and make sure the Load custom data connectors from: field points to the Custom Connectors folder. The standard path is C:\Program Files (x86)\On-premises data gateway\Custom Connectors

  5. Restart the On-Premises Data Gateway service: press Win + R, type "services.msc", find the gateway service in the list, right-click it, and click Restart.

  6. Restart the gateway from the On-Premises Data Gateway app as well.

  7. Go back to https://app.powerbi.com, open the scheduled refresh settings for your dataset, and click Discover Data Sources below the error message.

A screenshot of the error message