Fix the REST API to return the value and not the Id when getting single value Managed Metadata field
REST API should be fixed when getting single value Managed Metadata since it returns the Id instead of the actual value, which then requires another call to get the value. Without this you cannot show a list of items/docs with the single Managed Metadata value. Note that "Allow Multiple" Managed Metadata works fine as it returns a collection of actual values.
Thanks for your feedback! Although we appreciate your time and effort to give us this feedback, it’s not something we’re planning to do right now.
We are looking into evolving the Microsoft Graph APIs in these areas.
8 commentsComments are closed
fix this crap
This has been an issue since 2015 without a fix?
Tom Daly commented
this is also just frustrating for developers. It would be best to show the label and it would be even better to easily query/filter on taxonomy terms via rest.
Dean Verleger commented
Today I'm getting results in string form "label|guid"...
It's unclear to me why I'm getting a string and not an object (with the original label-as-id bug).
Anyway, this is on one tenant not another which means to support both scenarios my code is getting mightily cluttered.
Joris Guichard commented
Super annoying, why is fetching the right label possible when selecting a specific item in a list but not when requesting the whole list?! Please fix!!
Please fix this!
Martin Braun commented
I can confirm this issue and it's not only happening with Managed Metadata, but also with Person or Group fields. It's right that the normal request should return the ID not the value, but when you expand FieldValuesAsHtml, it should fill the expanded object with the value surrounded by proper HTML. This is happening and works fine when you have a multi value field, but on a single value field, it will contain the ID surrounded by proper HTML, not the value.
I'm shocked Microsoft never realized or fixed their mistake, after almost 4 years!!
Anton Thorn commented
Why is this still not fixed? It's been an issue for at least three years.