logo
search
SharePoint Document Issues

Fix Word Quick Parts Not Displaying SharePoint People Metadata

Partner EditorPartner Editor Sep 25, 2026 869 views

Question details

Word Quick Parts do not display data for SharePoint People columns when documents are generated using Power Automate, although other metadata fields render correctly.

How to Fix Word Quick Parts Not Displaying SharePoint People Metadata
Product
Microsoft Word, SharePoint, Power Automate
Device & OS
not provided
Scenario
Automated document creation using Power Automate in a SharePoint document set.
Observed behavior
Quick Parts for People metadata remain completely blank in the generated Word document, while all other text and choice metadata fields display properly.
Before you start

Ensure you have owner or edit permissions for both the SharePoint document set and the associated Power Automate flow to verify column configurations and run histories.

Solution 1Recommended

Force Metadata Sync via Manual List Update

Manually updating a field in the SharePoint source list triggers a refresh that forces the Word Quick Parts to pull in the People column data.

Because Power Automate may not fully initialize complex 'People' objects during the initial file creation, a secondary manual update forces SharePoint to push the metadata into the Word template's Quick Parts.

1
Open the Document Set

Navigate to your SharePoint site and open the specific document set containing the generated Word file.

2
Edit Properties

Select the document, open the details pane, or click on 'Edit Properties' in the toolbar.

3
Update a Field

Make a minor change to any metadata field in the source list and save the changes. Note: simply rewriting the exact same People value will not trigger the update.

4
Verify Quick Parts

Open the Word document to confirm that the People column data now displays correctly in the embedded Quick Parts fields.

Force Metadata Sync via Manual List Update
Testing Result: Updating any field in the source list consistently causes the People columns to display properly in the generated document.
Free Microsoft Office alternative

Experience Seamless Document Editing with WPS Office

While dealing with complex automated syncing issues between SharePoint and Word, you might need a reliable and fast alternative for standard document tasks. WPS Office offers a lightweight, completely free productivity suite that handles your daily text processing flawlessly.

  1. 1. Download WPS Office: Visit the official WPS website and download the free installation package for your operating system.
  2. 2. Install the Application: Run the installer and follow the on-screen instructions to set up WPS Office on your computer.
  3. 3. Open Your Documents: Launch WPS Writer and open your existing .docx files to enjoy seamless and fast document editing without complex sync errors.
Highly compatible with Microsoft Word (.docx, .doc) formatsLightweight software that runs quickly without heavy system requirementsFree to use with a familiar, ribbon-based interface for easy migrationCross-platform support for Windows, Mac, Linux, iOS, and Android
microsoft office alternative - wps office

Frequently Asked Questions

Why do Word Quick Parts show up blank for People columns?

This often happens because automated processes like Power Automate may not fully initialize or pass the complex data structure of a People object during the initial file creation, unlike standard text fields.

Does manually updating the SharePoint column fix the Quick Parts display?

Yes. Editing and saving any metadata field in the SharePoint source list triggers a document property refresh, which forces the People column data to render correctly in Word Quick Parts.

Can this sync issue be fixed entirely within Power Automate?

In some cases, adding an 'Update file properties' action immediately after the document creation step in your Power Automate flow can force the metadata to sync without requiring manual intervention.

Do other SharePoint metadata fields have this problem in Word Quick Parts?

Typically, simple metadata types like single lines of text, dates, and choices display correctly upon automated creation. The issue is predominantly isolated to complex fields like People or Lookup columns.