Forum Discussion

YogeshP's avatar
YogeshP
New Member
6 years ago
Solved

Power BI Service - scheduled refresh failure when using Azure DevOps API

I have connected my Power BI report to the Azure DevOps data, using AzureDevOps connector (beta). Since this doesn't support the multi line text field data under it's data set, I have referred this document and used the queries option to call the Azure DevOps REST API to fetch this data.

The report refreshes successfully when used in Power BI desktop app. But the refresh fails when published to the Power BI service with the message "You can't schedule refresh for this dataset because the following data sources currently don't support refresh".

Is there any fix for this or any work around to get the multi line text field data and it successfully refreshes in the Power BI service ?

Need Help
Tips and Tricks

5 Replies

  • Anonymous's avatar
    Anonymous
    Not applicable
    6 years ago

    Hi YogeshP ,

    I'd like to suggest you enable 'relative path' optional parameter to split URL to root path and relative path and add your authority credentials in the header.

    Using The RelativePath And Query Options With Web.Contents() In Power Query And Power BI M Code 

    For example:

     

    let
    Source = Json.Document(Web.Contents("https://[instance-name].visualstudio.com/", [Headers=[Authorization="Basic " & Credentials],RelativePath="DefaultCollection/[project-name]/_apis/wit/wiql/[query-guid]"]))
in
    Source

     

    After these, you can use anonymous mode to refresh your report from web API.
    Regards,

    Xiaoxin Sheng

    • YogeshP's avatar
      YogeshP
      New Member
      6 years ago

      Anonymous 

      As directed I used it as below:

      let
    Source = Json.Document(Web.Contents("https://[instance-name].visualstudio.com/", [Headers=[Authorization=Text.Combine({"Basic ", Binary.ToText(Text.ToBinary("USERNAME:PASSWORD"),0)})], RelativePath="DefaultCollection/[project-name]/_apis/wit/wiql/[query-guid]"]))
in
    Source

      It gave me the error: The 'Authorization' header is only supported when connecting anonymously.....

       

      Later I changed the data source settings to 'Anonymous' method, it gave the error:

      DataFormat.Error: We found extra characters at the end of JSON input.
      Details:
      Value=
      Position=4

      Probably as it returned a non-JSON reponse (HTML page asking to sign-in)

       

      Later I changed removed the 'Header' part as tried again (with anonymous and org authorization), it gave the same above error.