I made two modifications. I made the Trigger column default to match the column I'm watching. So, when a new record is created the two match from the start which avoids making a 2nd flow. I also added a 2nd condition that the column I'm watching must also equal the value I want. So, the flow wont trigger until two conditions are met - The two columns don't match AND the column I'm watching has the value I want. Seems to be working well.
Awesome work. i implemented the same but experienced the same trigger being triggered when someone opens the list and updates another item when the two column are the same or different depending on your flow it will trigger the alert again, What i did to mitigate this from happening is after the flow i added a step with an update item which updates the second mirror column to now match the first so that the trigger does not happen when someone comes in again and updates another item on the list
Great video! Could you make this work if the choice column is originally blank and then modified in a power app to display in a share point list? Trying to reduce errors if a different column is modified by accident but only want the choice column to push a flow into another list. Thanks!
Hi Thank you for this, I have slightly a different scenario issue here, I want to trigger an email when an item on the SharePoint list is modified by specifying the person who created it or in other words whoever submitted that record, I want to receive an email only when that person modifies.
I followed your steps regarding the trigger condition, but when I try to save the flow, this error pops up: "The input parameter(s) of operation 'When_an_item_or_a_file_is_modified' contains invalid expression(s). Fix invalid expression(s) for the input parameter(s) of operation 'When_an_item_or_a_file_is_modified'."
So, am I understanding correctly: in order to make this flow work, I would need to create yet ANOTHER variable in my SP list (the 'request trigger column'?)? Hmmm, I'll come back to this, but I would like to avoid altering my list fields...
why not just use the "create a rule" function within Sharepoint List to get an email notification when a particular column changes? I also found the video a little bit confusing as a newbie. you stated that the flow would trigger if the two columns did not match and then went on to create a second flow to match the two columns. I would appreciate if you or someone could explain this. p.s. I have tried to do this flow with my data and it does not work.
the method in the video allows you to do trigger conditions, so that the flow doesn't necessarily run every time there is a change to the item in SharePoint.
Nice! I don't think the other examples out there acknowledge your flow could trigger over and over again without this. Thanks.
This was incredibly helpful and easy to follow. Thank you so much for this work around!
I made two modifications. I made the Trigger column default to match the column I'm watching. So, when a new record is created the two match from the start which avoids making a 2nd flow. I also added a 2nd condition that the column I'm watching must also equal the value I want. So, the flow wont trigger until two conditions are met - The two columns don't match AND the column I'm watching has the value I want. Seems to be working well.
Love that!
how did you add two conditions
Awesome work. i implemented the same but experienced the same trigger being triggered when someone opens the list and updates another item when the two column are the same or different depending on your flow it will trigger the alert again, What i did to mitigate this from happening is after the flow i added a step with an update item which updates the second mirror column to now match the first so that the trigger does not happen when someone comes in again and updates another item on the list
Thank you so much for this and for explaining so simply! You've saved me so much mental energy haha
Thank you! This has been a real headache for me x_x
Awesome instructional video. Thx
Thank you so much Teacher
Great video! Could you make this work if the choice column is originally blank and then modified in a power app to display in a share point list? Trying to reduce errors if a different column is modified by accident but only want the choice column to push a flow into another list. Thanks!
Hi Thank you for this, I have slightly a different scenario issue here, I want to trigger an email when an item on the SharePoint list is modified by specifying the person who created it or in other words whoever submitted that record, I want to receive an email only when that person modifies.
I followed your steps regarding the trigger condition, but when I try to save the flow, this error pops up: "The input parameter(s) of operation 'When_an_item_or_a_file_is_modified' contains invalid expression(s). Fix invalid expression(s) for the input parameter(s) of operation 'When_an_item_or_a_file_is_modified'."
I had the same issue, instead of doing a filter do a condition!
In Filter Array instead of copying the condition from the advance mode of Filter Query, go to the Code View tab and copy the query from there.
So, am I understanding correctly: in order to make this flow work, I would need to create yet ANOTHER variable in my SP list (the 'request trigger column'?)? Hmmm, I'll come back to this, but I would like to avoid altering my list fields...
Can you please create same video for dataverse column change ?
Thank you!
why not just use the "create a rule" function within Sharepoint List to get an email notification when a particular column changes?
I also found the video a little bit confusing as a newbie. you stated that the flow would trigger if the two columns did not match and then went on to create a second flow to match the two columns. I would appreciate if you or someone could explain this.
p.s. I have tried to do this flow with my data and it does not work.
Link to Johnathan Silva video for expressions mentioned in video?
You are the best
Why don't use the get changes action ?
the method in the video allows you to do trigger conditions, so that the flow doesn't necessarily run every time there is a change to the item in SharePoint.
Just a query why we cant use trigger condition
a trigger condition is used at around 7 minutes into the video