0

Add a Flowr action to update and repair Word document Quick Parts (document properties/content controls)

Description:
We would like to request the addition of a new Flowr action that can update and repair Quick Parts (document properties linked to SharePoint fields) in Microsoft Word files.

Problem Statement:
When Word documents are migrated either:

  • From SharePoint Server to SharePoint Online, or
  • Between different SharePoint Online sites or libraries,

…the Quick Parts in the Word documents often break or become outdated. This is due to changes in the internal bindings to SharePoint columns or content types.

Additionally, there are scenarios where the underlying SharePoint fields change — for example, due to a solution redesign or data migration from third-party platforms. In such cases, it's necessary to update the metadata bindings and values in bulk across many documents.

Requested Functionality:
A new Flowr action that can:

  1. Detect and repair broken Quick Parts by relinking them to the appropriate SharePoint fields.
  2. Update multiple Quick Parts in a Word document with new values.
  3. Process multiple documents in bulk, to support large-scale migration or update scenarios.
  4. Accept mapping input (e.g., a JSON object or SharePoint list) to define which fields should be updated and with what values. This mapping must be required to ensure accurate and consistent updates.

Technical Background:
There is an existing API method provided by Aspose.Words that allows reading, updating, and repairing Quick Parts in DOCX files. Leveraging this capability could provide a reliable backend for this functionality.

Use Cases:

  • Post-migration document cleanup from SP2013/SP2016 to SharePoint Online
  • Field binding updates during information architecture changes
  • Repairing metadata display issues in document templates or contracts
  • Automation of post-migration document integrity checks

Value:
This enhancement would significantly streamline document migration and modernization projects, reduce manual rework, and improve consistency in document metadata management.

2 comments

  • Avatar
    Jay Goodison Official comment

    Hello Patrick Carl

    Thank you for the detailed suggestion. 

    We have added this to our backlog and plan to deliver the required capability by Q4 this year. If there is a more urgent requirement, please contact sales@encodian.com to discuss options. 

  • 0
    Avatar
    Patrick Carl

    Great to hear - thank you. An earlier availability would be helpful to use this feature in on-going projects. I've contacted the Sales Team about that.

Please sign in to leave a comment.