Contents
Getting and Setting Managed Metadata Fields in SharePoint 2013 Workflows. In many workflow scenarios, you’ll want to get a field value from a list item in one list and apply that value to a list item on another list. With most field types, you can do this easily using workflow variables and built-in list actions in SharePoint Designer 2013.
How are managed metadata fields similar to lookup fields?
Managed metadata fields are similar in structure to lookup fields, with complex values of type TaxonomyFieldValue. If you use the REST API to get or set the value of a managed metadata field named Customer, the JSON payload looks something like this:
How to use metadata triggers in SharePoint flow?
So let’s dive into it! Start by opening flow. Select the “Create from blank” Option, and select the “When a file is created or modified (properties only)” option. Choose the site Address, SharePoint Library Name and Folder where you’d like to enable users to manipulate documents via metadata triggers.
Why are metadata changes not applied to list items?
I update a term and hit up and the changes are not reflected on a content type (wiki page) where I am using that meta data item. After making the term item update (changing text) and navigating back to the wiki page I inspect the properties and the value is not showing the updated value.
How can I get label value of the meta data to update?
When I go into edit mode it shows the correct value which is good however this also would require me to navigate to every page go into edit mode and hit update/save on the page (in order to get the correct property value). How can I get the label value of the meta data to update (when making changes to the term store).
That may have worked in SharePoint 2010 workflows, but it doesn’t work in SharePoint Designer 2013 where workflow activities are built on the client web services. The error is clear – SharePoint is expecting a complex object, and it complains when the workflow manager sends it a string.
How to add a taxonomy field in SharePoint?
Let’s say you add a taxonomy field called “Client”, SharePoint will automatically add a note field called “Client_0”. Therefore, the solution is to update the hidden filed with a well-formatted text value, so that its associated taxonomy field also gets updated.
Are there any problems with SharePoint 2013 farm?
Today’s problem occured after I restarted a Hyper-V based SharePoint 2013 farm (Windows Server 2012, one SharePoint 2013 machine, one SQL Server 2012 machine, one DC). I fired up Central Administration and was hit with the following error: Unknown SQL Exception 0 occurred.