Document Set Metadata Does Not Sync to Files: User-Safe Fix

When you update metadata on a SharePoint Document Set, the changes do not automatically appear on the individual files inside that set. This behavior often confuses users who expect column values to propagate down to each document. The root cause is that SharePoint Document Set metadata is stored at the set level and is not designed to overwrite file-level metadata by default. This article explains why the sync fails and provides a practical, user-safe method to copy metadata from the Document Set to its child files.

Why Document Set Metadata Does Not Sync to Files

SharePoint Document Sets are a special content type that groups related documents together. The metadata you add to a Document Set — such as Project Name, Status, or Client — is stored on the Document Set item itself, not on the individual files inside it. When you view a file in the library, its metadata columns are empty or show default values. This is by design: SharePoint does not cascade or push parent metadata down to child items. The sync failure is not a bug; it is a limitation of the Document Set feature. To make metadata appear on each file, you must actively copy the values using a workflow or a custom script.

User-Safe Steps to Sync Document Set Metadata to Files

The following method uses Power Automate, which runs in the background without requiring code or direct SharePoint permissions changes. It is safe for all users with at least Edit permissions on the library.

1. Open Power Automate and create a new flow
   Go to make.powerautomate.com and sign in with your work account. Select Create from the left menu, then choose Automated cloud flow.
2. Set the trigger: “When a file is added or modified in a folder”
   Search for the SharePoint connector and select the trigger When a file is added or modified in a folder. Provide the site URL and the library name. For the folder field, leave it blank to monitor all folders, or select the specific Document Set folder.
3. Add an action to get the Document Set metadata
   Click + New step, search for SharePoint, and select the action Get file metadata. In the File Identifier field, choose the Identifier from the trigger output. This retrieves the file’s folder path. Then add another action: Send an HTTP request to SharePoint. Use the following settings:
   • Site Address: Your site URL
   • Method: GET
   • Uri: _api/web/getfilebyserverrelativeurl('@{triggerOutputs()?['body/{FullPath}']}')/ListItemAllFields

   This returns the file’s list item, including its parent folder’s metadata.

4. Extract the Document Set metadata values
   Use the Compose action to parse the JSON response. For example, to get the Project Name column, use the expression: outputs('Send_an_HTTP_request_to_SharePoint')?['d']?['ProjectName']. Repeat for each column you want to sync.
5. Update the file’s metadata
   Add the action Update file properties. Select the site and library. In the Id field, choose the Item ID from the trigger output. For each column, map the value from the Compose action. For example, set Project Name to the output of the Compose step.
6. Save and test the flow
   Name the flow something like “Sync Document Set Metadata to Files”. Click Save, then Test. Upload a new file to the Document Set folder and verify that the file inherits the Document Set’s metadata values.

Common Issues When Metadata Does Not Sync

“The flow runs but metadata remains empty”

This usually happens when the HTTP request returns a null value for the Document Set column. Check the column name spelling in the Compose expression. Use the exact internal name of the column, which you can find in the SharePoint library settings under the column name. Spaces in column names must be replaced with _x0020_ in the expression.

“The flow triggers on every file change, not just new files”

By default, the trigger runs on both add and modify events. To limit it to new files, add a condition that checks if the file was created in the last 5 minutes. Use the Condition action with the expression @{triggerOutputs()?['body/{Created}']} compared to @{addHours(utcNow(), -0.083)}.

“The Document Set folder is not a real folder”

Document Sets appear as folders in the library but are actually content types. The HTTP request method above works because it retrieves the list item of the file, which includes the parent folder’s metadata as long as the folder is a Document Set. If the folder is a standard folder, this method will not work — the metadata must be stored on the folder itself.

Document Set Metadata Sync Methods: Comparison

Item	Power Automate Flow	SharePoint Designer Workflow
Setup complexity	Low, no code required	Medium, requires SharePoint Designer 2013
Trigger	File added or modified	Item created or changed
Maintenance	Automatic, cloud-based	Manual, must be republished after changes
Permissions needed	Edit on the library	Full Control or Designer access
Performance	Fast for up to 100 files per minute	Slower, runs on-premises or in SharePoint

Document Set metadata does not sync to files automatically, but you can fix this with a Power Automate flow. Use the steps above to copy column values from the set to each file. For consistent metadata across all Document Sets, create site columns and add them to the Document Set content type. This ensures the same columns appear on every Document Set and its child files.