Similar Posts

12 Comments

  1. In the offchance this is a double post, we had some weird network hiccup:

    Marc, is this O365 only? We’re on premises in 2013 and I don’t appear to have to ask for the TaxonomyCatchAll column to see the term labels when I GET a list that has managed metadata columns. They come back as part of the return.

    1. @Chris:

      I don’t have an on premises SharePoint 2013 instance to test on, but I’m certain that the REST APIs are behind there. They also may be behind in SharePoint 2016. That’s the nature of SaaS: they can update it very frequently. I’m not sure when the TaxonomyCatchAll field showed up, unfortunately. I’ll see if I can find out…

      M.

  2. I really like this approach but now it turned out that this does not work if you are working with a subsite. I receive an error there because the lookup list is not in the same web.

    1. Yup, I’m seeing the same – not working in a subsite. In the end I’m making two calls for the different fields I need – one to the main item and one with “/FieldValuesAsText” tacked on the end – this gives the raw default label for the term, which is what I needed

Leave a Reply

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.