Forum Discussion
Invalid Connection Credentials When Adding API to On‑premises Data Gateway
Power BI Gateway Data Refresh Issue Resolution
Troubleshooting Steps
During a support call with Microsoft, assistance was provided and various tests were conducted to diagnose the issue.
The solution involved creating a Generation 1 (Gen1) dataflow in Power BI. In this dataflow, a table was created to store the token generation link.
The M code used in Power Query in Power BI Desktop was copied and pasted into the dataflow to enable data retrieval via the alternate link (this alternate link had been preventing the on-premises data gateway from refreshing data in the Power BI Service).
Once the dataflow connection was added in the on-premises data gateway, the Power BI Service scheduled refresh was able to update the data successfully.
there is no need to add the historycontact endpoint. Implement a custom action in your connector that adds it as a relative parameter.
But how do I do this?
This API only requires these two parameters:
Authorization: Company access token (Bearer token)
x-page (optional): Page number to return
Sorry, I thought you were using a custom connector.
Please follow the documentation. Use RelativePath and Query parameters. https://learn.microsoft.com/en-us/powerquery-m/web-contents#example-1
So it works in Power BI Desktop, but when adding this link to the gateway, in the Power BI Service it fails — it doesn’t allow me to add it and always returns an error when configuring the connection.