cancel
Showing results for 
Search instead for 
Did you mean: 
Reply
Abbie8290
Frequent Visitor

When an existing item is modified trigger starts before item is modified.

Hey guys, I have a two flows running. One that triggers when an item is created and one where triggers when an item is modified. The one that should trigger when the item is modified, begins as soon as the item is created which causes the flow to fail as it is based on conditions that will only be true once the item is modified. I turned off the other flow (when an item is created) since both flows pull from the same list, but its still triggering when an item is added and not when I modify it.

 

Is there anyone else experiencing this issue, or is there something I'm not understanding about this trigger? My assumption was the trigger should only start once the item is added to a list, then selected and edited.

 

Any help or thoughts would be greatly appreciated. I've been stuck on this one for a few days now.

 

Abbie

1 ACCEPTED SOLUTION

Accepted Solutions
Mike2500
Continued Contributor
Continued Contributor

I agree it's a bit tricky to get set up.

 

Starting from a new flow with a trigger of "when a new item is created", add a "do until". (when you click "new step", it's under "more", as it's neither an action nor a condition)

 

The "do until" needs a condition to be set up, but lets leave that alone for now. Inside the "do until" add a "get item". The site address and list name will be the same as your original list used in the "when an item is created". For the Id, use the ID field from the "when an item is created" trigger.

 

Right, so after the item is created, we immediately request it again. This is functional, not efficient.

 

Then, add a "delay" action. (or, officially, a "schedule - delay"). For testing purposes, you can set it for a few seconds, but if you deploy it that way, I'm not sure what that would do to your billing.

 

Then, go back to the condition for the do until. When you click into the "choose a value" box, you should get a list of available fields, and that list should include all the fields retrieved from the "get item" action. 

 

 

flow do until.png

View solution in original post

4 REPLIES 4
Mike2500
Continued Contributor
Continued Contributor

You're right, this behavior is inconsistent with how SPD workflows functioned. a workaround is to put in a loop that checks for the value of a particular field, and then pauses for a period of time. This is admittedly a poor workaround, but it's the only one I've found so far. 

Thanks for the reply, @Mike2500

 

Hmm, I see. If you don't mind could you five me an example of this workaround? I'm a begginer when it comes to flows and I'm still figuring stuff out. When you say a loop, is that an action available for the workflow? Could you screenshot what you mean, if you don't mind so I can visually have an example?

 

Thanks.

 

Abbie

Mike2500
Continued Contributor
Continued Contributor

I agree it's a bit tricky to get set up.

 

Starting from a new flow with a trigger of "when a new item is created", add a "do until". (when you click "new step", it's under "more", as it's neither an action nor a condition)

 

The "do until" needs a condition to be set up, but lets leave that alone for now. Inside the "do until" add a "get item". The site address and list name will be the same as your original list used in the "when an item is created". For the Id, use the ID field from the "when an item is created" trigger.

 

Right, so after the item is created, we immediately request it again. This is functional, not efficient.

 

Then, add a "delay" action. (or, officially, a "schedule - delay"). For testing purposes, you can set it for a few seconds, but if you deploy it that way, I'm not sure what that would do to your billing.

 

Then, go back to the condition for the do until. When you click into the "choose a value" box, you should get a list of available fields, and that list should include all the fields retrieved from the "get item" action. 

 

 

flow do until.png

View solution in original post

@Mike2500

 

Thank you! I tried this flow and so far it is working for what I need it to do!

 

Abbie

Helpful resources

Announcements
MPA_User Group Leader_768x460.jpg

Manage your user group events

Check out the News & Announcements to learn more.

V3_PVA CAmpaign Carousel.png

Community Challenge - Giveaways!

Participate in the Power Virtual Agents Community Challenge

Carousel 2021 Release Wave 2 Plan 768x460.jpg

2021 Release Wave 2 Plan

Power Platform release plan for the 2021 release wave 2 describes all new features releasing from October 2021 through March 2022.

R2 (Green) 768 x 460px.png

Microsoft Dynamics 365 & Power Platform User Professionals

DynamicsCon is a FREE, 4 half-day virtual learning experience for 11,000+ Microsoft Business Application users and professionals.

Top Solution Authors
Users online (1,301)