The list used in this video was created in this tutorial if you want to follow along! ua-cam.com/video/gYwkfwyRIxI/v-deo.html Reza also has a great video on sending reminder notifications here: ua-cam.com/video/v54QozIEGyw/v-deo.html
So I went to start one and realized Reza has a really good one already! Not sure if it’s worth reinventing the wheel or not, what do you think? Here’s the link: ua-cam.com/video/v54QozIEGyw/v-deo.html
Thanks for your video explaining both the condition within the flow (if and when it runs) and the trigger condition (preventing the flow from running altogether). I'm gonna play a bit with this trigger condition! It is essential to me to have only relevant flow runs in my flow run history. Without the trigger condition, any change would result in a flow run, spamming the history for irrelevant changes.
Yeah, the trigger condition is important, but it's not going to update the item willy-nilly because we have the conditional branch in there - it'll only update the item if the status changes and the new value is "complete". If it updates the item, it'll trigger itself a max of one extra time to re-check the conditions. The trigger condition can't check if a specific field changed, because we have to run a "get changes" action to get that info, but it can check the existing field values (e.g. current status) which keeps it from triggering overly much.
@ I found your vid in my quest to send 1 (and only 1) email after an approval flow, or, likewise, populate a calendar with 1 (and only 1) event after that approval. It’s unnecessarily hard with the tools MS have given us (with the potential change trigger loop). I’ve seen other clunky solution with a ‘memory’ field to track the last value of the approval result field, a necessity because MS cannot use versioned field values within the trigger condition itself. Sigh.
@@roelanddewindt Yes, sending the reminder email is on my list too. Reza has a newer really good video on approvals in Lists if you haven't seen that one, it doesn't handle reminders but it is very good. You're totally right that it's unnecessarily hard to make the experience good.
Hi, good video thanks for sharing. When I have multiple rows of completed status, how do I stop the completed dates changing on all the completed status when a new status is changed to complete. Thanks in advance
The trigger for this is on a single item, and it only updates the item that triggered it, so it should never be affecting more than itself. Do you maybe have something using get or update "items" vs "item"?
Were you ease dropping on our staff meeting?!?! 😸 Were were just discussing your video about using Lists instead of Planner (we have a great use case for that). And we were discussing the importance of setting completed dates. This saves us some trouble figuring out how to do that properly. Thank you!
In update item I get 'Assigned To' , this looks like need to be populated to allow for the flow to work . Your tutorial doesn't have this , how should I deal with this ?
Only if the field is required - you’ll have to update anything that is set to required to reset it to the same value that it already is (Power Automate foible). Is yours multi or single value?
To clarify, if your assigned-to field is single value, you can set the field to use the dynamic content card for your assigned to "claims" by inserting that (or email) and it will reset it to the current value. If your assigned-to field is multivalue, it becomes substantially more difficult because it wants the claims in an array, so you have to for-each on the assignees field to append to an array variable and then insert that in the array editor (it's the little "T" icon next to the field, erase whatever is in there and put in your appended array variable). At the end of the day, if you don't NEED a field to be required, it's easier to just ... set it to not required. That way you don't need to re-set the fields every flow run.
I followed the steps and the test says its successful, but the date doesn't populate in my list. my expression result comes back as false and not true. Not sure what i did.
Make sure that the status field card you are comparing to is the status value, not the status - there's two with a similar name, the value is the actual text label in the field. Also the true comparator for the "has changed" is very picky - so don't use double quotes, the true function, or capital case or anything like that, just the word true. It needs to read as the boolean, not as text.
@@bi-ome Thank you! I think i know why its happening, i have an addition field populate when adding the update item under the true statement, "title", under "id" what should be populated here? i didnt see that happen in your video.
@@alexandracrispino For Title just set it to the title field from the trigger actions. Basically any required field will tend to do this, you just reset it to the same value it was previously with the matching field name (or the value equivalent for choice fields). I'm not sure why mine didn't, it usually does - maybe a modern UI quirk.
The list used in this video was created in this tutorial if you want to follow along! ua-cam.com/video/gYwkfwyRIxI/v-deo.html
Reza also has a great video on sending reminder notifications here: ua-cam.com/video/v54QozIEGyw/v-deo.html
Crossing my fingers for the reminders video!
So I went to start one and realized Reza has a really good one already! Not sure if it’s worth reinventing the wheel or not, what do you think? Here’s the link: ua-cam.com/video/v54QozIEGyw/v-deo.html
Thanks for your video explaining both the condition within the flow (if and when it runs) and the trigger condition (preventing the flow from running altogether). I'm gonna play a bit with this trigger condition! It is essential to me to have only relevant flow runs in my flow run history. Without the trigger condition, any change would result in a flow run, spamming the history for irrelevant changes.
Yeah, the trigger condition is important, but it's not going to update the item willy-nilly because we have the conditional branch in there - it'll only update the item if the status changes and the new value is "complete". If it updates the item, it'll trigger itself a max of one extra time to re-check the conditions. The trigger condition can't check if a specific field changed, because we have to run a "get changes" action to get that info, but it can check the existing field values (e.g. current status) which keeps it from triggering overly much.
@ I found your vid in my quest to send 1 (and only 1) email after an approval flow, or, likewise, populate a calendar with 1 (and only 1) event after that approval. It’s unnecessarily hard with the tools MS have given us (with the potential change trigger loop). I’ve seen other clunky solution with a ‘memory’ field to track the last value of the approval result field, a necessity because MS cannot use versioned field values within the trigger condition itself. Sigh.
@@roelanddewindt Yes, sending the reminder email is on my list too. Reza has a newer really good video on approvals in Lists if you haven't seen that one, it doesn't handle reminders but it is very good. You're totally right that it's unnecessarily hard to make the experience good.
Hi, good video thanks for sharing. When I have multiple rows of completed status, how do I stop the completed dates changing on all the completed status when a new status is changed to complete.
Thanks in advance
The trigger for this is on a single item, and it only updates the item that triggered it, so it should never be affecting more than itself. Do you maybe have something using get or update "items" vs "item"?
Were you ease dropping on our staff meeting?!?! 😸 Were were just discussing your video about using Lists instead of Planner (we have a great use case for that). And we were discussing the importance of setting completed dates. This saves us some trouble figuring out how to do that properly. Thank you!
😆 The completed date is important, you’re right! You might also want due date reminders… that’s on the list too haha
@@bi-ome Yes, but that trigger will function a little differently. It will assure the due date is always in the future 😸
@@barttrudeau9237 Well, only if you don’t want it to keep reminding people who are extremely tardy 😆 But yeah, it will check the due date for sure!
In update item I get 'Assigned To' , this looks like need to be populated to allow for the flow to work . Your tutorial doesn't have this , how should I deal with this ?
Only if the field is required - you’ll have to update anything that is set to required to reset it to the same value that it already is (Power Automate foible). Is yours multi or single value?
To clarify, if your assigned-to field is single value, you can set the field to use the dynamic content card for your assigned to "claims" by inserting that (or email) and it will reset it to the current value. If your assigned-to field is multivalue, it becomes substantially more difficult because it wants the claims in an array, so you have to for-each on the assignees field to append to an array variable and then insert that in the array editor (it's the little "T" icon next to the field, erase whatever is in there and put in your appended array variable).
At the end of the day, if you don't NEED a field to be required, it's easier to just ... set it to not required. That way you don't need to re-set the fields every flow run.
I followed the steps and the test says its successful, but the date doesn't populate in my list. my expression result comes back as false and not true. Not sure what i did.
Make sure that the status field card you are comparing to is the status value, not the status - there's two with a similar name, the value is the actual text label in the field. Also the true comparator for the "has changed" is very picky - so don't use double quotes, the true function, or capital case or anything like that, just the word true. It needs to read as the boolean, not as text.
@@bi-ome Thank you! I think i know why its happening, i have an addition field populate when adding the update item under the true statement, "title", under "id" what should be populated here? i didnt see that happen in your video.
@@alexandracrispino For Title just set it to the title field from the trigger actions. Basically any required field will tend to do this, you just reset it to the same value it was previously with the matching field name (or the value equivalent for choice fields). I'm not sure why mine didn't, it usually does - maybe a modern UI quirk.
I'm not keen on using the new UI either
😂 I'll get used to it eventually... I hope