Populate Word Document File Not Found (Using Logged In User's Account)

(0) Share

Report

Posted on by PowerPlatypus89

I have a flow that is triggered by Power Apps.

The flow then populates a Word template with information from Power Apps, creates a new file, and then sends a share link back to Power Apps.

The Word template is saved in the OneDrive of a service account.

This works fine when I'm on the service account but it fails when I'm logged in with the Service Account, it fails when logged in to my account and fails for users.

I spent a great deal of time troubleshooting this and finally came to the conclusion that the Populate Word Template is using the account of the user logged in to the Power App.

Is this expected behavior? It seems very odd as everything else in Power Automate uses the account connection configured in the Flow, not the account of the user logged in to the app.

Does anyone else have a similar workload up and running? Maybe using SharePoint as the location of the template file instead of OneDrive?

All responses (1)

Answers (1)

Verified answer

shoog 2,164 on at

Like (0)

Report

Re: Populate Word Document File Not Found (Using Logged In User's Account)

Anytime you trigger a flow from Power Apps, it will use the credentials of the user running the app. This is by design.

You could share the template with all users or put it on a SPO location where users have access.