Skip to main content

Power BI

Needs Votes

Bypass test connection/Ignore failure for Web Sources that depend on authorization header

Vote (144) Share
Elton Sequeira's profile image

Elton Sequeira on 09 May 2017 00:55:48

The power BI service runs a test connection on Web API data sources before pulling data. However for Web Sources whose response depends on a required authorization header fail to authenticate in the power bi service while setting up a scheduled refresh. The source is accessed using Web.Contents and by passing the URL, Relative path and authorization header. This works perfectly fine in Power BI desktop since it executes the GET request along with the authorization header without a test connection. If the same could be done in power bi service by either bypassing the test connection or ignoring failures then a schedule refresh could be setup.

Comments (25)
Elton Sequeira's profile image Profile Picture

dc9d61f3 dc5b-4fa8-8929-5bc20dc9af44 on 06 Jul 2020 00:08:27

RE: Bypass test connection/Ignore failure for Web Sources that depend on authorization header

Datasources on the web have many forms of authentication and authorization. Fortunately, mquery allows us to craft unique queries to accommodate those different methods. Unfortunately, Power BI service does not. Until skip connection test is back online many web datasources are offline for Power BI..

Elton Sequeira's profile image Profile Picture

317fe3e4 1f2a-46a2-a02b-214b625a0677 on 06 Jul 2020 00:07:42

RE: Bypass test connection/Ignore failure for Web Sources that depend on authorization header

Wow - any ideas for a workaround?

Elton Sequeira's profile image Profile Picture

e7ab2142 8467-4fbf-a7e5-e35bc62f4dd0 on 06 Jul 2020 00:07:10

RE: Bypass test connection/Ignore failure for Web Sources that depend on authorization header

'+1 please fix, such a neg to the product.

Elton Sequeira's profile image Profile Picture

42d4b512 b667-4c9a-8cdf-9add9c51b218 on 06 Jul 2020 00:04:58

RE: Bypass test connection/Ignore failure for Web Sources that depend on authorization header

Lost 4 hours today on this issue thinking the problem came from my query...

Elton Sequeira's profile image Profile Picture

2f980be4 38bf-4ef8-a853-63aa90b5945b on 05 Jul 2020 23:58:06

RE: Bypass test connection/Ignore failure for Web Sources that depend on authorization header

Common PwBi Team! I am trying to use PwBI + SharePoint REST API (That requires authentication upfront ).. the workaround of using relativepath won't work here!! Please, integration is the KEY that makes PwBI so great, and right now I am not able to connect TWO MICROSOFT PRODUCTS!!! fix it pls!

Elton Sequeira's profile image Profile Picture

d35ed26f e4ad-44fc-a789-7c33c7e572e2 on 05 Jul 2020 23:53:22

RE: Bypass test connection/Ignore failure for Web Sources that depend on authorization header

We have just came across this too, voting for a fix to this issue.

Elton Sequeira's profile image Profile Picture

08b0f4d2 7401-46ef-af7c-4b0db64cdbd0 on 05 Jul 2020 23:51:39

RE: Bypass test connection/Ignore failure for Web Sources that depend on authorization header

I need this too... in desktop it works, but in service it doesn't work

Elton Sequeira's profile image Profile Picture

ce5a2041 366c-48f1-b4e5-73973c9d886a on 05 Jul 2020 23:50:10

RE: Bypass test connection/Ignore failure for Web Sources that depend on authorization header

Please add this feature

Elton Sequeira's profile image Profile Picture

2337c80a b8f2-44f9-9711-fb8fa527341e on 05 Jul 2020 23:44:44

RE: Bypass test connection/Ignore failure for Web Sources that depend on authorization header

'+1, please fix this

Elton Sequeira's profile image Profile Picture

0899fd77 7924-4e03-a8ce-2a6ad9992491 on 05 Jul 2020 23:39:42

RE: Bypass test connection/Ignore failure for Web Sources that depend on authorization header

I had this issue as well. It worked for me to use only the root URL in the 'URL' part and to put everthing else, including the user and password, in 'relative path'. This is decribed here: https://community.powerbi.com/t5/Service/Anonymous-access/td-p/19136
(Apparently this only works if the root ULR is accessible without authorization.)
Furthermore I had to delete the entire dataset on PBI Service and publish it from PBI Desktop again.