We have the following situation:
When using a Managed Metadata column value to name folders automatically created by the Content Organizer, the Content Organizer creates folders/subfolders for the *entire* term hierarchy from the term to the entry point in the column properties, not just
the single value actually entered in the column. Is this expected behavior? If so, it seems quite odd. If not, is there some way to get this to behave the same way it does when using a non-Managed Metadata column?
Documents from a document library are to be routed to a Records Center and placed into a specific folder (Category1, for example). The Content Organizer is configured to evaluate whether a value exists within a Managed Metadata column - if the column is
empty the rule does not fire, if the column is populated the rule fires. Assume the Managed Metadata column is called "MMColumn" and points to a branch in our taxonomy named "Terms". The term the user applies to the document is Category1 (chosen from MM) which
corresponds to the name of the ultimate destination folder.
Our rule specifies that the document is to be routed to our Records Center. The option to automatically create a folder is enabled with the folder name to be the value from the Managed Metadata column specified above.
Expected behavior is our docume
View Complete Post