Here's how my Flow is supposed to run:
A member of the organization submits a Form > Power Automate creates a Planner Task, filling it out using the information from the form > Once the task is completed, the responder receives an email saying the task associated with the form they submitted is complete.
The first two steps work perfectly, but the response step is where I'm having the issue.
The Trigger is too general. The Flow's precision goes from Campus (List) > Stage (Bucket) > Issue (Task). I need the Trigger to be more precise so that when that specific task is finished, it triggers the next steps. The problem with the Trigger being too general is that if multiple people submit forms for 1 list, when one of the tasks in the list is marked complete every one of those people get an email.
Solved! Go to Solution.
Hi @dgoins :
You could add a condition action to judge if the completed task the SPECIFIC Planner Task.If yes,then send the email.
Best Regards,
Bof
Could you split the current flow into two flows?
But how would it trigger when a specific task is completed? That trigger is too general, because it goes when any task in the plan is completed
It would fire whenever any task is finished, yes, but it would only fire to the members of the task itself, something which you would define in the logic, no?
No, it would fire an email to anyone who posted a task in that list.
OK, well ... good luck!
Hi @dgoins :
You could add a condition action to judge if the completed task the SPECIFIC Planner Task.If yes,then send the email.
Best Regards,
Bof
Hey @v-bofeng-msft!
This works!! My only question now is how can the flow go back when the condition returns false? Is there a do-while loop, maybe?
The first Microsoft-sponsored Power Platform Conference is coming in September. 100+ speakers, 150+ sessions, and what's new and next for Power Platform.
Announcing a new way to share your feedback with the Power Automate Team.
Learn to digitize and optimize business processes and connect all your applications to share data in real time.
User | Count |
---|---|
72 | |
23 | |
17 | |
17 | |
14 |
User | Count |
---|---|
125 | |
35 | |
30 | |
28 | |
26 |