After using the content and structure system to copy documents from one site's document library to another, the document properties fields that are set to accept multiple metadata values from our taxonomy are no longer accepting these values (either a single value or multiple values).

As part of the move, SP2013 added new columns to the table for every multi-value metadata field. (i.e. "Product" now has a companion column called "Product_0" which is a multi line text field). I understand this happens due to the method of transfer using content and structure.

So, when a new document is uploaded to the doc library, I can input all the other classifications (i.e. drop down options, single value metadata columns), but the Multi-Value metadata field does not save. I can fill in the values and no error is generated when saving the changes, but when I go back to the table view, the values I input are not saved. When I re-open the document properties menu again, the values are not saved there either.

If I use "quick edit" from the table view, I can edit the columns and the values will be saved correctly.

How do I get the document properties page to work as expected again allowing users to correctly complete the multi-value fields and having them saved to the doc library?

  • I did some additional checking this morning and this issue strangely affects a single-value input metadata field as well as the multi-value fields. I have some single value input fields that do not have this behavior and some that do. Two of the columns even reference the same taxonomy but behave differently. – Sunfrost Nov 15 '18 at 17:14
  • More testing: I tried creating 2 new document libraries on two sites and tested the following: 1. Source library - all columns setup to mirror the source library that displayed the issue above. Destination Library - empty, no custom columns. Only the default "title" column created by SP. Outcome - SP created metadata_0 columns for all metadata columns in the destination library except for the 1st column. The Source Library was unaffected (no _0 columns created). – Sunfrost Nov 19 '18 at 17:19
  • More testing 2 - Same source library as example 1 above. Destination Library - Created a new library, mirrored the columns to match Source Library exactly (name, metadata options...) Outcome - no change compared to example 1. – Sunfrost Nov 19 '18 at 17:23

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Browse other questions tagged or ask your own question.