Forum Discussion

CC_22's avatar
CC_22
Regular Visitor
3 years ago
Solved

ADO AreaPath now AreaName?

Hope someone can help, 

I've created an straightforward Odata feed query to bring in IterationPath (complete with Product Increment and Iterations) and AreaPath (organization/project/team name). It was working well until a month ago, when the message that AreaPath and IterationPath were null field names. I updated the names to AreaName and IterationName and, even though these returned values, they were not the values I was looking for. In addition, these new field names seem to have a combination of values. 

The error message is this: 

 

From research, this means that the field AreaPath is null, it does not exist, not that there are null values under that field. Same with IterationPath.

What is curious, is that the old names work sometimes and not others. I have tried changing the API version, to remove instability of the preview versions, but no luck. 

I'm looking to learn what actually happened to ADO's board under the hood to cuase this problem, albeit momentary, and how to avoid it next time. I had to re-do all my reports using ADO because they all broke; I re-did them starting from the Odata feed in PBI Desktop, not copying the M code. 

Any insights would be appreciated.

Thanks!

CC

1 Reply

  • foodd's avatar
    foodd
    Community Champion

    Consider closing this post, and opening it under the Developer Community (visualstudio.com)

    that is also Azure DevOps feedback as an idea or a problem.  There is a wider audience following these specific questions.