We are having issues with moving/copying Document Sets using Workflows. It is working as expected in Dev but does not function as expected in Prod. The issue is how the data is populated to the Drop Off Library. Our library has the document set and one custom column (meta data) which will be used for routing rules. We have enabled both Document Sets and Document IDs in both environments. The workflow error generated is “unknown error” and nothing seems to be appearing in the ULS logs.
We have tried deleting all rules, turning off Content Organizer, and then deleting the Drop Off Library. We then re-enabled the Content Organizer and set a Rule. The Drop Off Library was again generated by the system and contains the Content Types and columns as expected. BUT… still not functioning.
Does anyone have any thoughts of where to go next?
Thanks in advance for any help you might be able to provide!
Milton
Thanks for the lead on the known issue. I have recreated the environment using only columns and content types with no spaces in the names. It did not resolve my issue.
SAD!!!!!!
All of my fields are exactly as your example. XXX%5Fx0020%5FXXX; I am assuming this is OK?
Yes it’s different. You can get the internal name for a column by browsing to the List Settings > Edit Column and look at the QueryString. This will be url encoded but is a simple way of retrieving the internal name without writing any code. You will get something like:
/_layouts/FldEdit.aspx?List=%7B37920121%2D19B2%2D4C77%2D92FF%2D8B3E07853114%7D&Field=Product%5Fx0020%5FDescription
%5F is a ‘_’. The field name is Product_x0020_Description.
The code option is to use:
string itemInternalName = item.Fields[“Field Display Name”].InternalName;
Hope this helps
Thanks, I looked at the link. Is internal name different than the name displayed by accessing Site Settings>Site Columns>Column Name?
Hi,
Please check that custom column have the same internal name as in dev. Maybe it’s solve the problem:
Some Managed Metadata fields not populated
