YAY!! It’s here it’s here it’s finally here!!
Course: Knowing when to code in Salesforce!
The #1 most common mistake I see from Salesforce newbies is using the wrong tool for the job!
In this course, we put an end to the age old question: “Should we solve this using code?”
In fact, we’re going to take a real-life business scenario and attempt to solve it using each of Salesforce’s automation tools. Along the way, we’ll explain the pros and cons of each solution:
You’re going to know exactly what tool to use for your job using a step-by-step approach!
Watch this course and hope you enjoy – Don and I had a BLAST making it!
P.S. scholarships are available to veterans, their family members, the unemployed, and those in need of a good hug. Email me at firstname.lastname@example.org and I’ll do my best to help you out!
So happy! — David
Looking forward to this course and we hope its full of information and experience with the hands of experts in it
Great content as usual, i am taking a chance to get ahead of myself here BUT do you have a good SF implementation guide to share?
I’m half way through with the “Play by Play” and It’s really cool stuff. Means simple and at the same time very very powerful hecks.
Keep it up.. :-)
I am currently watching this. I just thought that in the flow module of the course, the issue there could have been easily resolved by invoking the the flow on case create/update instead of account update.
P.S. As usual I am enjoying the course. Thanks.
That part gets really hairy when case 1 is open but your most recent edit is on case 5 which turned to closed!
Flow is very powerful so there are hacks to get this mostly working, but of course it’s all a matter of trade-offs! Flow could be the best solution for your particular use case / org!
Exactly. I think for me we don’t have to worry about which case was updated, since the flow itself won’t care which case is updated-to whether it is closed or opened. As long as there is an AccountId of the case being updated, the flow will try to find at least 1 open case of that account. Then from there the flow will update the Account’s Has Open Case field.
EDIT: we would’ve ran into a separate issue had the flow been on cases instead, and that’s that it wouldn’t calculate on case deletion.
Thus we decided to run it on account, and get the latest calculation possible.
Both approaches are totally valid, just with different walls / errors! Wish we had time to cover these scenarios!
Our goal was actually to break each tool as much as possible, so even if flows did run on delete, we’d break it using a governor limit =)
Moral of the story: all tools have pros and cons, choose the simplest tool that is good enough for your particular scenario / org!
Can’t argue with that. I just finished the course. Great job! And Thank you!
By the way on a completely different topic, as much as I wanted to get that sf99 t-shirt, there is no way for me to get to where you are. I am on the other side of the world. haha! I am not sure if this has been asked before, but can I print it for me?
Have your way with it!
I completely geek out this weekend and finished the Play by Play series. Great work once again!!!