Hi All
Is there a way to control, i.e. re-issue, an approval email? I have a power app that allows a person to kick off an approval flow for a document. What is happening is when a selected approver gets the initial email, they will not necessarily review the doc straight away, sometimes leaving it up to the last day of the approval period or it gets deleted for some reason. I'd like to offer the approver the opportunity to re-issue the same approval email so the recipient can approve/reject the design.
Any suggestions much welcomed!
cheers!
dj
Sure. It's actually much easier than you'd expect. PowerAutomate has baked-in operators for Common Data Service / Dataverse that make it incredibly easy. In your Trigger or Action, just search for "common" and the Common Data Service operations will all show up.
From there, you will need to select an Organization to create a connection. This may be where you get stuck because you might not (probably don't) have access to the Default Environment. You will probably need to ask your administrator to add you as a user in this environment with a role that gives you access to these records. And before you ask: no, I don't know what table names to tell your admin you need. I would assume, though, that they have some fairly predictable set of names like, "approval" and "request".
Ok, so do you have an example of how to query the CDS to see/interrogate the approval app?
thanks!
dj
They're precisely the same thing. When you kick one of those off from PowerAutomate, the Approval app will show it in Teams right away.
Hi
Thanks for you reply!
What you say is interesting. I'm fairly new to this Power Platform so I'm trying to understand what goes on behind the scenes. I'm not using the Teams approval, just the normal one which is kicked off via Power Automate. Is that action also embedded in the CDS?
Cheers!
dj
2 answers:
Again, if you will be operating this at scale, definitely query the CDS database directly to get your info; I haven't seen big problems since the modernization to Flow, but I still bear the scars of trying to rely on tons of waiting Workflows and I will never trust an async process to handle long term waits at scale again.
WarrenBelz
85
Most Valuable Professional
Michael E. Gernaey
65
Super User 2025 Season 1
mmbr1606
55
Super User 2025 Season 1