Dynamics Community Forum Thread Details

Power Automate, PO Approval - not triggering for users with limited (recorded) permission sets

Hi,

I have an issue with power automate workflow (PO approval) not getting triggered for users with specific permission sets. Does anyone have experience with Power Automate workflows not getting triggered?

Below are the steps I took and tests I ran:

New permission set, recorded, can only create a PO, request approval, send PO, post invoice and receipt

I've created a permission set by recording the steps required, including "request approval".
Perm set = "Regional AP"

Create new user group, including recorded permission set.

User Group = "Regional AP Group" - contains the following Perm Sets
1. Regional AP
2. Login
3. Local
4. System app - basic

Updated users, only have user group memberships

Regional AP Group
Automate Action
Excel Export Action
Teams Users

Tested PO creation, success. Updated users can only:

Add a new PO
Request Approval
Send PO
Post PO Invoice and Receipt

Setup and tested power automate PO approval workflow, success

d a new flow from Template, "Request approval for D365 BC Purchase Order"
Tested the power automate PO approval workflow template with users with delivered user groups (User group = d365 full access) -

Tested PO approval for users with limited access (User group = regional AP group), fail.

Add a new PO, success
Request Approval, status changes to "Approval Requested", success
Review My Flows, PO Approval, Run History, no trigger, fail

So the limited access user works and the flow works, but the limited access user can't trigger the flow.

Even though the limited access user can create a PO and request approval, something (missing table, page, codeunit?) is preventing the flow from getting triggered. There is no error message, just a PO in "Requested Approval" status and an empty Run History.

I've compared the Effective Permissions of "Full Access User" (~10,000 objects) with those of "Regional AP User" (~3500 objects), but nothing jumped out as a the culprit(s) for the failed trigger.

Any ideas appreciated.

Best, Mike

Quick Links