Forum Discussion
Enable Automatic Refresh with Basic Auth connection to an API
Hello! I have a report I am working on where I need to use the Azure Devops API to get Sprint Start and End dates. I successfully connected to the API in Power BI Desktop by using the Web connection method, choosing Basic Authentication, keeping the username blank and the using my API key as the password. This works perfectly in Power BI Desktop. Unfortunately, when the report was published to the service, I could not schedule a refresh because that authentication method doesn't work there. I have read a lot of blogs around adding headers and using relative path, but I haven't figured out how to make that work for me. Does anyone
I found the solution! It was made via a blending of the relative path concept from Chris Webb's blog: Chris Webb's BI Blog: Using The RelativePath And Query Options With Web.Contents() In Power Query And Power BI M Code Chris Webb's BI Blog (crossjoin.co.uk) with a base 64 concept from the following blog: Encoding basic authentication in an url with Power Query/M language | Ambiguity vs Information (wordpress.com).
Essentially, you make the basic path for the api the main page of azure devops, then you add the specific API page you want to visit to the relative path. You specifcy basic connection, make the username blank and pass the api key into the password. You encode this in base64 with the code shown in the other article. Hope this helps anyone else who may need it.
3 Replies
*does anyone know how to make this work?
Hi b_infinity_1 ,
Try the following methods
Datasets - Get Refresh Schedule
Datasets - Get Refresh Schedule In Group
Best Regards,
Stephen Tao
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.
I found the solution! It was made via a blending of the relative path concept from Chris Webb's blog: Chris Webb's BI Blog: Using The RelativePath And Query Options With Web.Contents() In Power Query And Power BI M Code Chris Webb's BI Blog (crossjoin.co.uk) with a base 64 concept from the following blog: Encoding basic authentication in an url with Power Query/M language | Ambiguity vs Information (wordpress.com).
Essentially, you make the basic path for the api the main page of azure devops, then you add the specific API page you want to visit to the relative path. You specifcy basic connection, make the username blank and pass the api key into the password. You encode this in base64 with the code shown in the other article. Hope this helps anyone else who may need it.
