Forum Discussion

Anonymous's avatar
Anonymous
Not applicable
5 years ago

Accessing Description in AzureDevops from PowerBI via oData API?

I am currently using Odata feed in PowerBI power query to access User Stories and their fields from Azure Devops in order to build reporting. I am unable to access the 'description' field using the O...
Need Help
ferryv's avatar
ferryv
Resolver II
3 years ago

No problem. As this seems to come up a lot, I decided to write an article on LinkedIn about retrieving the Description and Acceptance Criteria with an end-to-end process for a fictional Azure DevOps organisation and project that might help you on your way. The process would be the same for other work item types also (e.g. Risks, Bugs, etc), but the fields might be slightly different.

Anonymous's avatar
Anonymous
Not applicable
3 years ago

Thank you for Sharing this Article, it's really helpful.. am able to retrive the Acceptance Criteria with out any HTML code.. but if acceptance criteria is empty for any of the row.. am getting an error. how to solve this error.

  • ferryv's avatar
    ferryv
    Resolver II
    3 years ago

     

    Change the last step in the process from 

     

    #"Remove HTML from Acceptance Criteria" = Table.AddColumn( #"Add lf for li (AC)","Acceptance Criteria", each Text.Combine(Html.Table([VSTS.fields.Microsoft.VSTS.Common.AcceptanceCriteria],{{"AC",":root"}})[AC],"#(lf)"))

     

    to 

     

    #"Remove HTML from Acceptance Criteria" = Table.AddColumn( #"Add lf for li (AC)","Acceptance Criteria", each if [VSTS.fields.Microsoft.VSTS.Common.AcceptanceCriteria] = null then null else Text.Combine(Html.Table([VSTS.fields.Microsoft.VSTS.Common.AcceptanceCriteria],{{"AC",":root"}})[AC],"#(lf)"))

    Essentially, the change checks if the original value is null and if it is, it keeps it as null (or you can change it to any other value, like "No acceptance criteria provided", otherwise it strips the html out.

     

    That should resolve the issue you're having. 

     

    Thanks for pointing that out. I have updated the referenced article above also with the fix. 

    • Anonymous's avatar
      Anonymous
      Not applicable
      3 years ago

      Thank you, it is working as expected… my Final Ask.... is it possible to pull the extract data for more than one projects with in Same Organization

      • ferryv's avatar
        ferryv
        Resolver II
        3 years ago

        I don't see any reason why you shouldn't be able to, although I have not worked through that specific scenario. 

         

        I wrote an article on Linkedin a while back on how to retrieve data from multiple Azure DevOps organisations - Link to the article. This also works across different projects and area paths within a single Azure DevOps organisation.

         

        If you read through this and modify the example in that article with the code to retrieve longtext fields, you should be good to go.