【FlowFest】 | V2 Challenges and Answers!
ฝัง
- เผยแพร่เมื่อ 4 ส.ค. 2024
- Have you heard of FlowFest? V2 just ended last week and we had a really fun time! Try out these interesting challenges yourself 🙌
Visit our blog for more Flow knowledge:
salesforce-flowsome.com/
【Unmanaged package for fix-my-flow challenges】
login.salesforce.com/packagin...
【Register for v3】
forceanywhere.force.com/s/flo...
#salesforce #flow #salesforceFlowsome #flowfest #challenge #answer
Wow one of the best flow videos I’ve seen - awesome thanks and can’t wait to try out the custom loop!!
FlowFest challenges demystified. Great work, Melody. Thank you.
Thanks Andy:)!
This is great, Melody. Thank you! I just signed up for the next event.
That's great! Hope to see you there next time Gustavo
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.
Thanks for the constructive feedback! This is definitely something we want to improve for V3:)!
@@salesforceflowsome any chance to see your reply on separate comments above?
Regarding #15: I had no idea you could manually assign the variable from the screen component. This saves the assignment step. Cool!
I feel like one can never stop finding new things about Flow!
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?
Fields component should work as well:)
@@salesforceflowsome please check new comments under your video
#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.
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?
@Salesforce Flowsome! any comments?
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.
@salesforceflowsome any chance to see your reply?
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.