cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 
simonjhudson

Change the trigger

Submitted by Advocate IV on ‎12-05-2017 06:38 AM

As far as I can tell, it isn't possible to change the Trigger step for a different Trigger.

Often we build a flow, then find the intial condition isn't correct (we need a SharePoint created or modified, not just created, for example. Or we need to switch a flow from SharePoint to OneDrive.) If it's a sophisticated Flow then rebulding it from the top is incredibly tedious and prone to mistakes.

 

So please provide a mechanism to chage the trigger condition in the flow for a completly different trigger condition. 

Status: Planned

Today it is possible but you first have to remove the uses of the outputs of the trigger. At that point you can remove the trigger and add a new one. This is required because if you have actions that depdend on specific fields from the trigger outputs you need to find all of those locations and point them at the new trigger outputs fields once available. 

14 Comments (14 New)
Comments
Stephen
Power Automate
Power Automate
‎12-18-2018 01:21 PM
Status changed to: Planned

Today it is possible but you first have to remove the uses of the outputs of the trigger. At that point you can remove the trigger and add a new one. This is required because if you have actions that depdend on specific fields from the trigger outputs you need to find all of those locations and point them at the new trigger outputs fields once available. 

Anonymous
Not applicable
‎04-29-2019 02:00 AM

Maybe to overcome the issue described, when the initial condition is changed, the items that rely on it are higlighted so that they can be easily identified and changed.

markforemansapn
Advocate I
Advocate I
‎05-14-2019 08:23 PM

@Stephen 's solution works for me. Thanks!

ONYXJas
Advocate IV
Advocate IV
‎07-22-2020 10:22 PM

The problem of dependent actions is a knotty one whenever ANY step is changed, not just the trigger.

 

What would be really useful is for the flow editor to allow the step (or trigger) change, but then CALL OUT steps where dependent dynamic data is affected by flagging them in the UX.  That would make it really easy to find dependencies that need to be fixed following a change like this.