Showing results for 
Search instead for 
Did you mean: 

Fabric is Generally Available. Browse Fabric Presentations. Work towards your Fabric certification with the Cloud Skills Challenge.


The query specified in the URI is not valid: VS403522: The property 'Description' is not available



I am trying to query ADO data using OData. My challenge is unable to query the "Description" field. The Below Error Appears


The query specified in the URI is not valid: VS403522: The property 'Description' is not available


The description is part our of work Items, yet unable to get that field in $metadata or normal work item query.

Resolver I
Resolver I

The Description (or any other longtext field) is not available via the standard oData feed. You can retrieve it via VSTS.Contents. I previously wrote a linkedin post on this after I worked it out myself. 


You essentially make 2 calls. One to retrieve the workitem IDs (either via oData.Feed or Web.Contents) and another using that workitem ID to retieve the Description, etc.


So for instance using power query, you could use something similar to this (change OrgA and ProjA to your organisation and Project as well as other fields and other filter criteria):


#"Retrieve oData" = Table.FromRecords({[
FeedData= OData.Feed("" 
&"$filter=(Area/AreaPath eq 'ProjA\Sandbox' and Project/ProjectName eq 'ProjA' and WorkItemType eq 'Product Backlog Item')"
#"Expand Data" = Table.ExpandTableColumn(#"Retrieve oData", "FeedData", {"WorkItemId",  "Title", "State","WorkItemType", "Priority"}, {"WorkItemId", "Title", "State","WorkItemType", "Priority"}),
#"Retrieve VSTS Data" = Table.AddColumn(#"Expand Data","VSTS", each Json.Document(VSTS.Contents("" &Number.ToText([WorkItemId])))),
#"Expanded VSTS" = Table.ExpandRecordColumn(#"Retrieve VSTS Data", "VSTS", {"fields"}, {"VSTS.fields"}),
#"Expanded VSTS.fields" = Table.ExpandRecordColumn(#"Expanded VSTS", "VSTS.fields", {"System.Description", "Microsoft.VSTS.Common.AcceptanceCriteria"}, {"VSTS.fields.System.Description", "VSTS.fields.Microsoft.VSTS.Common.AcceptanceCriteria"})
in #"Expanded VSTS.fields"

You should get something similar to this:




See also:


It also explains how to strip out the HTML, etc.

@ v-yalanwu-msft

Thank you for your response. 


So how do I get the Description field in my Odata query? This error comes only when i add the description field..


Here is my sample query

= OData.Feed("" & "$filter=WorkItemType eq 'Risk'" & "&$select= WorkItemId, InProgressDate, CompletedDate, LeadTimeDays, CycleTimeDays, ProjectSK, WorkItemRevisionSK, AreaSK, Revision, Watermark, Title,Severity, Probability,WorkItemType, ChangedDate, CreatedDate, State, BusinessValue, ClosedDate, Priority, ResolvedDate, DueDate, Effort, OriginalEstimate,CompletedWork, RemainingWork, StartDate, StoryPoints, TargetDate, ParentWorkItemId, TagNames, StateCategory" & "&$expand=Description($select=WorkItemId)", null, [Implementation="2.0"])



Community Support
Community Support

Hi, @Sabarikumar7579 ;

Queries that violate an OData error rule will result in a failed response with a 400 (Bad Request) status code. Associate messages don't appear within the property. Instead, they'll generate an error message in the property in the JSON response.


OData Analytics query guidelines - Azure DevOps | Microsoft Learn
Best Regards,
Community Support Team _ Yalan Wu
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.

Helpful resources

PBI November 2023 Update Carousel

Power BI Monthly Update - November 2023

Check out the November 2023 Power BI update to learn about new features.

Community News

Fabric Community News unified experience

Read the latest Fabric Community announcements, including updates on Power BI, Synapse, Data Factory and Data Activator.

Power BI Fabric Summit Carousel

The largest Power BI and Fabric virtual conference

130+ sessions, 130+ speakers, Product managers, MVPs, and experts. All about Power BI and Fabric. Attend online or watch the recordings.

Top Solution Authors