Fabric is Generally Available. Browse Fabric Presentations. Work
towards your Fabric certification with the Cloud Skills Challenge.
Do not make the several pre-fetch calls to API endpoints for the Web.Contents method. Just grab the data.
When using PowerBI DirectQuery it performs 2-3 pre-fetch warm-up calls. Most like to see if the endpoint is alive and if alive has some data.
Similar syntax to below I am using:
GetCSVData = Web.Contents( "https://api.acme.com/v1/exports?order_id=ON-00000",........)
And it results in HTTP errors of 499 (client abort connection) and 502 (bad gateway) and eventually HTTP 200 (ok).
If you want to get a solution for this kind of network issue in the Power BI as soon as possible, I suggest you to open a support ticket to ask the opinions from the technical support team of Microsoft about this issue.
Thank you very much!
Community Support Team _Robert Qin
No need for a support ticket... I prefer someone from the PowerBI server-side development team to look at the source code and the logic related to this behavior of contacting the API endpoint with the Web.Contents funtion.
I guess this "DirectQuery server-side" part of powerbi is not found in public github for me to investigate... 😉
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.