An awesome place to learn everything about flow. 【For new starter】: Go through the Intro and Important Concepts playlist 【For learning-by-doing】: Go through the Practice playlist, and search for the unclear concepts in this channel
This was so helpful and clear I'm wondering how I can have her teach me everything I need to know for the rest of my life. This is exactly how my brain needs to be taught concepts!!! THANK YOU SO MUCH FOR THIS.
Hi Flowsome, If I create the flow for one object, would I still need to follow step 2: Plot the data model? For example, I want the flow to run on the contact object only.
This is so helpful. Learning flow as an admin is very difficult and it is hard to make my brain think this way. These videos make coding with point and click easier to understand in plain language.
Debug option in the flow will show Input/Output values for all nodes/elements in the flow. But, if one needs to look at detailed logs containing get/update/delete operations on records & limits info, 'debug logs' is essential.
Very nice video, but background music is terrible because I don't understand what is she saying in the video? So, I think removing background music and better than it new session.
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)
So, on the last challenge you show a flow with 2 get records, loop inside another loop, 4 update records and you say there is only 2 errors? doesn't it all looks like a complete mess? It can be done better: 1. Get all Accounts. 2. Loop through Accs and save names in the Text collection 3. Get open Leads 4. Loop through Leads 4.a. decision (check if acc name collections contains current Lead Company) 4.a.yes branch - assign new status, add to lead collection for update 4.a.no branch - assign priority based on the formula that calculates based on the number of employee (don't forget to handle null value), add to lead collection for update 5. update all leads in the collection So we have: 1. Just 1 update action, no 4 ones 2. 2 separate loops, no nested loops It is actually frustrating to see that representative of Flow Expert contest makes flows that cause a lot of questions (like this situation and also see below). All together it add concerns how fair and professional the whole competition is. Like do you count all best practices, how optimized the flows and ready for production? or you judge just by: it works in the current org, it doesn't have obvious issues like dml inside loop, it was done fast and in time?
and even more questioned the solution, if you think like how this flow is triggered? how often? would it make sense to trigger 2 flows when lead created/updated (company name/status/number of employee changed) or account created/updated (name changed). This way you would deal with one lead and one account at a time. Or one account and couple of related leads. But not with the whole set of Accs in the org (that could be thousands) and all set of Open leads (that can be also quite a lot). Moreover, on Lead level you would have just a before flow, that is more optimized than after flows.
Why is it legal to use beta features? They are not yet released. So if you are going to award best flow experts, it makes sense to award if their flows will work for the customers. And customers definitely use not a sandbox or dev edition org for their business.
#15. Where in requirements it is said you need to copy all values from the original account? You use recordId var to create a child account - so it copies all values, inc. address, any custom fields you have (e.g. External System Id), AccountNumber, etc. Why it is considered to be correct if it wasn't mentioned in requirements? Moreover, AccountNumber as well as External System Id definitely should be different. I would create a child Account record by manually assigning just 3 fields from the screen and parent account id.
Thanks Melody for your video, I experienced an error on this "This error occurred when the flow tried to create records: INVALID_FIELD_FOR_INSERT_UPDATE: Account: bad field names on insert/update call:" I was able to trace it to person account fields which are not allowing me to update. How do I manage this
For challenge #19, could we use the fields component instead of individual screen components instead or fields would not support creating multiple records?
Found this channel from a reddit thread and I just have to say THANK you. I love that you actually go through and explain the individual parts of a flow and why you would use them. I can't stand guides that just say "go do x" without ever explaining how they arrived at that decision in the first place.
I just went through the exercises. There is nothing I found difficult but I think the time to do the exercises would be tough. I didn't time myself, probably should have. Suggestion for people trying these exercises, activate the flows and save a new version. That way if you need to go back to the source you can easily do that. A suggestion for creating activities. Maybe try working in smaller groups leaving people out of the process for each activity. Let's say you have 9 people creating 6 exercises. Work in groups of 3 to create 2 exercises each. They the other 6 can try the exercises they did not create to get an idea how long each exercise takes to complete. If it takes 6 experts an hour to complete the exercises maybe they are too long. Just a thought. Looking forward to V3 if I am lucky enough to be chosen to compete.
Hi Jason, what kind of duplicate error are you getting? Is it that you update the same record multiple time or you have duplicate records in your org? This might because your flow logic is conflicting with your duplicate rules, so I’d recommend modifying the flow logic so that the rules don’t get triggered
Love watching these types of videos, very insightful and clear! Was there new update that prevents you from clicking on the name of orchestration to view the current steps at 9:17?
