Trigger condition to fire only when specific field values have changed

[Deb]

Hi All,

I have a flow that triggers when an item is created or modified in Primary list and accordingly updates the secondary list. I want to restrict the trigger condition based on 'two specific field values' - i.e trigger only when 'Product/Vendor' name is changed in Primary list. Since the values are dynamic in nature, I cannot hard code syntax like this - @equals(triggerBody()?['Product']?['Value'], 'XYZ').

Hence, is there way to limit 'what fields' Flow should watch for changes and then triggers based on it??

Thanks

Deb

[Pstork1]

There is an action called "Get changes for an item or file (properties only)" You can use that to see if a particular field was changed since the last time the item was modified.  The flow will still trigger on all modifications, but this can help you decide whether to proceed or not.  As you said since the values are dynamic there is no way to add a trigger filter.

[yashkamdar]

Hello Team,

This should definitely help you out.

Step 1- So the trigger is when an Item or a file is modified

Step 2 - Get changes for an Item or a file

Keep the configurations same as the one I have mentioned in the screenshot below.

Step 3 - Condition

Here the true magic lies, the above action gives you results for each column that might have changed in the form of true or false as shown below -

So you just need to grab the column that you are looking after in your case Product/Vendor and apply a condition to check if the response for modified of it is True or False, if it is true then it has been modified doesnt matter what it has been modified to.

Just starting writing your next part of logic in the YES logic of the condition.

If this reply has answered your question or solved your issue, please mark this question as answered. Answered questions helps users in the future who may have the same issue or question quickly find a resolution via search. If you liked my response, please consider giving it a thumbs up. THANKS!

[Deb]

Thanks so much @yashkamdar for the elaborate steps. I wanted a better way to control this so that Flow doesn't kick off on False Positive. In this solution - Flow will still fire each time when an item has changed for the fields I am not interested to watch. But seems like there is no other way to go around it?

[yashkamdar]

Hello Team,

Yes unfortunately, this is the only option going forward.

There isn't a privilege available directly inside the Settings option of Trigger where we can maybe manipulate and check that Flow only trigger for Dynamic value.

If this reply has answered your question or solved your issue, please mark this question as answered. Answered questions helps users in the future who may have the same issue or question quickly find a resolution via search. If you liked my response, please consider giving it a thumbs up. THANKS!

[lyndseylula]

This is an old thread but 3 years later I’m looking for a solution and wondering if anything has changed to make it possible?

[Pstork1]

AS mentioned there is a way to check to see if a particular field has changed.  Or you can create a trigger condition that only fires when a field changes to a specific value.  But to set it to only fire when a specific field has changed in any way is still not possible.

[lyndseylula]

I think I might have found a way...?

I created a new column in the SP List called "ProcessorWas". I kept the Condition in my flow, to check for Get changes for an item or file (properties only), Has Column Changed: Processor.

If true, it does the action I want, then I added an Update Item and pass the Processor to ProcessorWas.

Then in the original When an item or file is modified Trigger Conditions I put @not(equals(triggerOutputs()?['body/Processor/Email'], triggerOutputs()?['body/ProcessorWas/Email']))

It seems to be working! I change the Processor and it fires, change anything else and it doesn't fire at all. Unlike before when it was firing with any change then doing the Condition check.

[Pstork1]

Yes, if you use the flow to track the previous value of the column then you can use a trigger condition to make sure it only fires if that column changes.  But that requires that you create an extra column to track the previous value.

[felipeabajo]

Thanks a lot Yash, your response is very helpful.

I have checked this procedure can be also applied to lookup fields.

However, even though the values of action 'Get changes' displays Yes or No, the value in the condition should be true or false.

Kind regards