Getting Rich text or HTML fields from Azure DevOps work items to PowerBI

[vbvbvb]

Hello all,

Looking for helop with following topic -- I am using OData query to get Analytics data from ADO: https://analytics.dev.azure.com/<org>/<project>/_odata/v3.0-preview/WorkItems

It works fine and does the job, however I found a need to collect comments from users which should be stored in custom field (Text - Multiple lines):

From what I found out so far, apparently OData query do not return any HTML or Long text fields, so only workaround is to use VSTS REST API query.  But unfortunately there's very scarse and unclear inforamtion on this topic - I found guide way https://endjin.com/blog/2016/07/querying-the-vsts-work-items-api-directly-from-power-bi but in my case,  it fails with obsure error after I press "Invoke".

Is there any clear guidance how to connect to VSTS REST API from Power BI and fetch that custom HTML field and combine with another table? Would appreciate any help!

[vbvbvb]

I gave a 2nd look at 2nd article "Retrieve long text fields from Azure DevOps in PowerBI (linkedin.com)" -- after changing Privacy levels, it works and it is best step-by-step tutorial for this issue out there. Thanks for reference!

[ferryv]

Thanks for highlighting the privacy level might need changing for it to work. I added this to the notes in the article, which I omitted previously.

[Anonymous · Accepted solution]

Hi @vbvbvb ,

Please refer to the following post that may be helpful to you:

Solved: How to connect Azure DevOps REST API in to power b... - Microsoft Power BI Community

Retrieve long text fields from Azure DevOps in PowerBI (linkedin.com)

How do I converting work Item description from Azu... - Power Platform Community (microsoft.com)

Best Regards,

Neeko Tang

If this post helps, then please consider Accept it as the solution to help the other members find it more quickly. 

[vbvbvb]

Hello @Anonymous ,

Solution 1 is not working, query to that API return empty JSON:

Source 2 fails after addin bit with VSTS code, first asks for data privacy classicification, then shows: 

Solution 3 has interesting potential, but need to be tested. Will try later and confirm.