Microsoft Dynamics 365 | Integration, Dataverse...

Power Automate Populate Word Template fills properly but downloaded, does not

(5) Share

Report

Posted on by JA-11021511-0

Hello!

I have created a Power Automate flow that gathers dynamic content in Dynamics 365 and populates a word template and creates that file and stores in it Sharepoint.

The flow is working perfectly but when I downloaded the final file. The content control has the placeholder text instead of the dynamic one.

Viewing the file directly from Sharepoint shows the proper content.

But downloaded, it does not. I have also emailed the file and it still shows up as below.

I have enabled the "Remove content control when contents are edited" from the properties of each content control.

Thanks!

Categories:

Power Platform integration

I have the same question (0)

All responses (2)

Answers (0)

JA-11021511-0 37 on at

Like (2)

Report
Copy link

Link copied!

I have found out that it will be filled out if sent within the same organisation but not when downloaded or sent outside the organisation.

Is this a setting to fix?

Was this reply helpful? Yes No
Suggested answer

DAnny3211 11,399 on at

Like (0)

Report
Copy link

Link copied!
Hi,

The issue you're experiencing—where the Word template populated via Power Automate shows correct dynamic content in SharePoint but reverts to placeholder text when downloaded or emailed—is likely related to how content controls behave when the document is opened outside of the SharePoint context or cached incorrectly.

✅ Suggested Solutions

Disable “Remove content control when contents are edited”

Although enabling this setting seems logical, it can cause the content to revert or not persist properly when the document is opened in different environments. Try disabling this option for each content control and republish the template.

Ensure the Flow Uses “Populate Word Document” Correctly

Double-check that the Populate a Microsoft Word template action is correctly mapping the dynamic fields and that the output file is saved as a .docx (not .tmp or .doc).

Use “Convert File” to PDF Before Sending

If the document is only meant for viewing, consider converting it to PDF before emailing. This ensures the dynamic content is preserved and not affected by Word rendering quirks.

Check for Caching Issues

Sometimes, when downloading from SharePoint, the file may be cached or opened in a preview mode that doesn’t reflect the latest changes. Try downloading via right-click > Save As or opening in Word Desktop App instead of browser preview.

Avoid Emailing Immediately After Creation

Add a short delay (e.g., 10–30 seconds) in the flow before emailing the file to ensure SharePoint has fully committed the changes.

Test with a Clean Template

Create a new Word template with minimal formatting and test the flow again. This helps isolate whether the issue is with the template itself.

Let me know if you'd like help reviewing your flow configuration or testing alternative output formats.

Thanks and best regards,

Daniele

Note: This response was prepared with support from Copilot to ensure clarity and completeness.

Was this reply helpful? Yes No