Forum Discussion
REST API bug when retrieving managed metadata list field configured to allow single values?
- Oct 18, 2017
Hi Joel,
This is a well-known issue since 2013.
Single-valued MMD columns just can be retrieved as desired with OData, with Multi-valued MMD columns it is much better.
But there is a workaround. There is a possibility of getting single-valued MMD columns' values while items request if do it with `getItemsByCAMLQuery` list's method. It's a part of REST API, is an implementation for backward compatibility. The downside of the approach is that OData configurators like ($select, $filter, $expand and so on) can't be used together with OData.
--
Regards,
Andrew
Hi Joel,
This is a well-known issue since 2013.
Single-valued MMD columns just can be retrieved as desired with OData, with Multi-valued MMD columns it is much better.
But there is a workaround. There is a possibility of getting single-valued MMD columns' values while items request if do it with `getItemsByCAMLQuery` list's method. It's a part of REST API, is an implementation for backward compatibility. The downside of the approach is that OData configurators like ($select, $filter, $expand and so on) can't be used together with OData.
--
Regards,
Andrew
Hi Andrew, thanks for your reply!
To be honest, I was really surprised to never come across this limitation before :)
I did found some blog posts describing the CAML workaround, but between that and the JSOM, I ended up with JSOM.
Joel