Hi. Thank you for your fantastic Flow series and teaching. In this case, why did you not simply use an Update Record Element using the filters to Update all the Cases where the Account Id is equal to the Id record that triggered the flow?
Hi Daniel, thanks for the nice comments! Ah originally I was trying to find the easiest case to explain how to make a loop, but I neglected the fact that we can just use the Update Records with specify condition to achieve the same. Thanks for pointing out! I will pin your comment at the top so everyone will be able to see this: "Update Records with Specify Conditions can update multiple records that meet the criteria. It should be used when you are updating all records with the same value"
Just wanted to comment and say that as a long time reader of your blog, I'm so excited to see this new UA-cam channel. I learn much better from video walkthroughs and this was a great example of a flow loop! I know you're currently studying Apex for PD1 and it'd be great to see some Apex tutorials here as well. I'm a senior Admin and want to try for my PD1 in the next year.
Thanks so much for your nice comment Land! I will see if I can create some contents for Apex as well:) Before that, highly recommend to check out Apex Hours for Apex tutorials!
What a great tutorial! I finally grasped what loops are all about... I have to be honest, digging through walls of text on the topic is really tiresome, but a work-along video like yours got this topic across much more effectively & efficiently!
Ok, it is very clear how to make a loop. Thanks! But, 1. It would be better to check if any record found before we do any update or even loop (good practice to check null values, null collections). Even if we know it wont fail when no Cases found - it is still a very good practice. Ask developers :) 2. Why we actually do so many actions if we could do just one update action? Like I"m a new flow guy and it looks for me that we overcomplicate the staff that could be done with just 1 action. Or get/decision/update to check null decision and waste 2 operations (2 as on the video - get + update, but still no need to overcomplicate with a loop). Would it be better to show example that is more illustrative as the only one flow solution? E.g. When you need to update found record with 2 different logic based on the data on the same records - but even then, you will have 1 get and 1 update, that is not better than having just 2 separate update actions. So you whether select an example when you make a loop to do 3 different updates (assignments) to the same set group of records (1 actions < 3 update actions for sure more optimized), OR make an example where you need to have a more complex logic of updates (when you need not only filter records to update, but take value from each separate record in the loop and use it in the calculation of the new value to be)
Hi, I came here after reading your amazing blog on governor limits. As per flow limit- It allows 2000 elements per transaction. And, I see in most cases wherever we use loop, we have to set atleast two assignment elements. Means if 1100 record coming into flow, we'll end up hiting the limit? Eg. 1 Element (To get record) 1 for loop itself 2 assignment element 1 for DML operation Total = 2 + (2 × 1100) + 1 = 2203 = Crash??? I know we must filter the record before it comes to loop, but 1100 rec is not so big and can be expected even after filter. I am afraid to use autolaunch flows instead of apex if that's the case. Please correct me if am going wrong here in understanding the flow limits or suggest a solution/approach to avoid it. Thanks!
Hi Vicky, Thanks for the nice words and you are absolutely correct! Flow is not designed for huge amount of data (just yet), but there are some ways we can bypass it. First is, if you are updating all the records to a same value, you can skip the loop and just use Update Records. This will save a bunch of elements. Otherwise, leverage Schedule-triggered flow or Record-Triggered flow. These two flows are bulkified, meaning you can build the flow as if it's for one record, but the system will automatically batch all the records. This will help you run flows on a bigger set of data. I actually have a dull experiment on this topic - you can take a look if you are interested: salesforce-flowsome.com/flow-how-to-run-flow-on-a-huge-amount-of-data/ Super great question!
@@salesforceflowsome Thanks for the reply. Probably we can optimize the flow using formula or by using platform event. Will try it deeply when I get some time.
Hi. Thank you for your fantastic Flow series and teaching. In this case, why did you not simply use an Update Record Element using the filters to Update all the Cases where the Account Id is equal to the Id record that triggered the flow?
Hi Daniel, thanks for the nice comments! Ah originally I was trying to find the easiest case to explain how to make a loop, but I neglected the fact that we can just use the Update Records with specify condition to achieve the same. Thanks for pointing out! I will pin your comment at the top so everyone will be able to see this:
"Update Records with Specify Conditions can update multiple records that meet the criteria. It should be used when you are updating all records with the same value"
Thank you Melody. This is excellent. You make it look so easy and explain it so clearly.
Thanks Gustavo as always:)!
I'm so happy to have found this new channel of yours. You made understanding loops so much easier for me to understand, thank you
That’s nice to hear Robert. Good luck!🍀
Excellent Explanation!
Thank you .Loop concept very well explained
I’m glad to hear. Thanks Babita!
Just wanted to comment and say that as a long time reader of your blog, I'm so excited to see this new UA-cam channel. I learn much better from video walkthroughs and this was a great example of a flow loop!
I know you're currently studying Apex for PD1 and it'd be great to see some Apex tutorials here as well. I'm a senior Admin and want to try for my PD1 in the next year.
Thanks so much for your nice comment Land! I will see if I can create some contents for Apex as well:) Before that, highly recommend to check out Apex Hours for Apex tutorials!
Thank You.
Helpful!
What a great tutorial! I finally grasped what loops are all about... I have to be honest, digging through walls of text on the topic is really tiresome, but a work-along video like yours got this topic across much more effectively & efficiently!
Thanks!! I will try my best to make more videos that are easy to follow along!
Wonderful explanation....thank you!
Nice to hear that. Thanks Sharmila😊
Great ❤️
Thanks😊!
Ok, it is very clear how to make a loop. Thanks!
But,
1. It would be better to check if any record found before we do any update or even loop (good practice to check null values, null collections). Even if we know it wont fail when no Cases found - it is still a very good practice. Ask developers :)
2. Why we actually do so many actions if we could do just one update action? Like I"m a new flow guy and it looks for me that we overcomplicate the staff that could be done with just 1 action. Or get/decision/update to check null decision and waste 2 operations (2 as on the video - get + update, but still no need to overcomplicate with a loop).
Would it be better to show example that is more illustrative as the only one flow solution?
E.g. When you need to update found record with 2 different logic based on the data on the same records - but even then, you will have 1 get and 1 update, that is not better than having just 2 separate update actions.
So you whether select an example when you make a loop to do 3 different updates (assignments) to the same set group of records (1 actions < 3 update actions for sure more optimized), OR make an example where you need to have a more complex logic of updates (when you need not only filter records to update, but take value from each separate record in the loop and use it in the calculation of the new value to be)
Hi,
I came here after reading your amazing blog on governor limits.
As per flow limit-
It allows 2000 elements per transaction.
And, I see in most cases wherever we use loop, we have to set atleast two assignment elements.
Means if 1100 record coming into flow, we'll end up hiting the limit?
Eg. 1 Element (To get record)
1 for loop itself
2 assignment element
1 for DML operation
Total = 2 + (2 × 1100) + 1 = 2203 = Crash???
I know we must filter the record before it comes to loop, but 1100 rec is not so big and can be expected even after filter.
I am afraid to use autolaunch flows instead of apex if that's the case.
Please correct me if am going wrong here in understanding the flow limits or suggest a solution/approach to avoid it.
Thanks!
Hi Vicky,
Thanks for the nice words and you are absolutely correct! Flow is not designed for huge amount of data (just yet), but there are some ways we can bypass it.
First is, if you are updating all the records to a same value, you can skip the loop and just use Update Records. This will save a bunch of elements.
Otherwise, leverage Schedule-triggered flow or Record-Triggered flow. These two flows are bulkified, meaning you can build the flow as if it's for one record, but the system will automatically batch all the records. This will help you run flows on a bigger set of data. I actually have a dull experiment on this topic - you can take a look if you are interested:
salesforce-flowsome.com/flow-how-to-run-flow-on-a-huge-amount-of-data/
Super great question!
@@salesforceflowsome Thanks for the reply.
Probably we can optimize the flow using formula or by using platform event.
Will try it deeply when I get some time.