Forum Discussion

Griggs's avatar
Griggs
Frequent Visitor
1 year ago
Solved

POST API - Web.Contents failed to get contents

I have the following query that is working fine in Power BI desktop (I have anonymised the API Key and Workspace ID in the relative path). However, when publised, I am getting an error:Failed to upda...
Need Help
  • OwenAuger's avatar
    OwenAuger
    1 year ago

    Hi Griggs

    I took your query and added my own Clockify API Key & Workspace ID, and initially received the same error when setting up Data Source Credentials in the Power BI Service.

     

    After some testing, it seems the only way to avoid the error and validate the Data source credentials is to bypass the connection test by enabling "Skip test connection" as shown here:

    This seems to be one of those cases where the Power BI Service simply can't validate the API URL. Changing the split between Base & Relative URLs didn't seem to help in this case.

     

    In any case, after enabling "Skip test connection", I was able to successfully refresh the semantic model in the Service.

     

    Are you also able to get refresh working in the same way?

OwenAuger's avatar
OwenAuger
Super User
1 year ago

Hi Griggs

I took your query and added my own Clockify API Key & Workspace ID, and initially received the same error when setting up Data Source Credentials in the Power BI Service.

 

After some testing, it seems the only way to avoid the error and validate the Data source credentials is to bypass the connection test by enabling "Skip test connection" as shown here:

This seems to be one of those cases where the Power BI Service simply can't validate the API URL. Changing the split between Base & Relative URLs didn't seem to help in this case.

 

In any case, after enabling "Skip test connection", I was able to successfully refresh the semantic model in the Service.

 

Are you also able to get refresh working in the same way?