Template Issues

Fix Missing Word Quick Parts in Power Automate from SharePoint

Anum Mushtaq Oct 21, 2026 868 views

Question details

The user needs to populate and save Word documents in SharePoint using list data, but is unable to proceed because Word Quick Parts fields do not appear as dynamic content in Power Automate.

How to Fix Missing Word Dynamic Content in Power Automate

Product: Microsoft Power Automate
Device & OS: not provided
Scenario: Setting up a Power Automate flow to generate Word documents automatically based on SharePoint list items.
Observed behavior: Word Quick Parts fields fail to show up in the dynamic content menu when configuring the Power Automate flow.

Before you start

Verify that you have a premium Power Automate license, as the 'Populate a Microsoft Word template' action requires it, and ensure your Word template is saved in a SharePoint Document Library or OneDrive.

Solution 1Recommended

Replace Quick Parts with Plain Text Content Controls

Power Automate cannot always map standard Quick Parts. You must use Plain Text Content Controls in your Word template to generate dynamic content fields in the flow.

The most common reason fields do not appear in Power Automate is incorrect field types in the Word document. Power Automate specifically requires the Developer tab's 'Plain Text Content Control' to recognize mapable fields.

Enable the Developer Tab

Open your Word template, go to File > Options > Customize Ribbon, and check the box for 'Developer' in the right column.

Insert Plain Text Content Controls

Place your cursor where you want dynamic data. Go to the Developer tab and click the 'Aa' icon (Plain Text Content Control).

Assign a Title to the Control

Select the newly inserted control, click 'Properties' in the Developer tab, and enter a clear Title and Tag (e.g., 'CustomerName'). This exact title will appear in Power Automate.

Save and Re-run Flow

Save the updated template back to your SharePoint Document Library. Go back to Power Automate, refresh your flow, and the new fields will appear as dynamic content.

Replace Quick Parts with Plain Text Content Controls

Requirement Check: Avoid using Rich Text Content Controls or legacy form fields, as Power Automate cannot populate them natively.

Solution 2

Consult the Microsoft Power Automate Community

If your fields still do not appear or your flow fails to save to SharePoint, escalate the issue to official Microsoft experts.

Free Microsoft Office alternative

Prepare Document Templates Seamlessly with WPS Office

While Power Automate requires Microsoft tools for backend flow execution, you can use WPS Office as a lightweight, highly compatible alternative to create, format, and prepare your daily Word templates before uploading them to your cloud drives.

1. Download and Install: Get the free WPS Office suite from the official website and install it on your device.
2. Create Your Template: Open WPS Writer to design your document layout, insert tables, and format text precisely.
3. Save as DOCX: Save your completed template in the standard .docx format to ensure full compatibility with cloud platforms.

Highly compatible with Microsoft Word (.docx), Excel, and PowerPoint formatsLightweight application that runs smoothly on almost any deviceFamiliar user interface with zero learning curve for Office usersFree to use for everyday document editing and formatting

microsoft office alternative - wps office

Frequently Asked Questions

Why are my Word fields not showing up in Power Automate?

Power Automate requires 'Plain Text Content Controls' to map dynamic fields. Standard Quick Parts, Rich Text controls, or legacy form fields usually do not display as dynamic content in the flow setup.

Do I need a premium license to populate Word templates in Power Automate?

Yes, the 'Populate a Microsoft Word template' action in Power Automate is a premium connector. You will need a standalone Power Automate premium license to use it.

Where should I save my Word template for Power Automate to access it?

You should store your Word template in a SharePoint Document Library or OneDrive for Business so the Power Automate flow can easily retrieve, populate, and save the generated file.

Document & File Issues