Quite often we are facing the challange to write ManagedMetadata values to SharePoint Columns with Nintex Workflow.
The only way to acheive this I know, is described in the following blog:
Is this procedure the recommended way to do this?
Or are there some other good ideas around?
Solved! Go to Solution.
Thanks for your reply.
Your approach works fine for SharePoint lists.
But if you want to write into a column in a document library you have to go the way using the "Call Web Service" activity.
We struggled with the guide in this post "Setting managed metadata fields in a Nintex workflow" because of a wrong field Name reference. After checking the internal field Name with "SharePoint Manager" from Codeplex, we got it up & running. The internal field Name is just a guid instead of "PrimaryCategoryTaxHTField0".
Btw: Another Thing I notice which was a bit strage to me was the fact that it is very important which activity you are using for storing the source taxonomy field value.
If you are using a "build a string" activity you will only get the Taxonomy Field Name without the Field ID.
But if you are using the activity "Set Variable" you will get the Taxonomy Field Value including the id which makes it very much easier to build the string for the web Service update request.
Yes, it depends on what activity you choose to get the value. I have seen the same stuff.
Thanks for figuring out that this implementation works different for lists and libraries. I have a similar requirement to make this working for Lists and Libraries. Will test it in both the scenarios and see if that works out and post the updates based on that.
We got this working in lists and document libraries with the same approach of GUID. There was no difference in behaviour.
Wherever we got the text value of MMS data, we queried the TaxonomyHiddenList to fetch by label using Query List Action.
What GUID are your referring to that replaced "PrimaryCategoryTaxHTField0"? What did you need to change to use the GUID in the web service call?