Fix SharePoint Document Set Metadata After Moving Files
Question details
Apply the target Document Set's shared metadata to files moved between Document Sets.

- Product
- SharePoint Document Sets
- Device & OS
- not provided
- Scenario
- A user moves files between Document Sets in the same SharePoint library and expects the destination's shared-column values to apply.
- Observed behavior
- Moved files can retain their original metadata instead of inheriting the target Document Set's values. Copy behavior can differ.
Check which columns are configured as shared columns in the Document Set content type and note the destination Document Set's values. Test both move and copy operations in the same library configuration, since their results can differ.
Update the moved file's properties manually
Use this approach for a small number of files when you can enter the destination Document Set's values yourself.
In the SharePoint library, select the destination Document Set and open its details pane to review its metadata values.
Open the destination Document Set, select the moved file, and use the Details pane or Edit properties command.
Enter the destination values in the relevant columns and save the properties if prompted. Reopen the file's details to verify the changes.

Apply destination metadata with Power Automate
Use a flow when files are moved frequently and manual property updates are impractical.
Work with Office documents in WPS Office
WPS Office is a free, lightweight alternative for editing documents, spreadsheets, and presentations in a familiar interface. Its Microsoft Office format compatibility makes it easier to continue working with existing files, though it does not replace SharePoint Document Set metadata management.

Frequently Asked Questions
Why did my file keep its old metadata after I moved it?
Moving a file between Document Sets in the same library may not refresh its shared-column values. Open the file's details pane and update the properties, or use automation to apply the destination values.
Will copying a file apply the destination Document Set's metadata?
Copying can produce different results from moving, but behavior depends on the library configuration. Test a copy in the target library and check the resulting file properties before relying on it.
Do shared columns automatically update files in nested folders?
Shared-column values do not necessarily propagate to folders inside a Document Set. Check the properties of files in nested folders and use manual updates or automation if needed.
How can I tell whether my Power Automate flow caught a move?
Move a test file, then open the flow in Power Automate and review its run history. If no run appears, test another trigger or approach for your library before deploying the flow.




