Read the following articles to improve your Salesforce knowledge.
Salesforce Summer ’26 is here. I went through the release notes to identify the key features you should actually care about. Here’s a quick summary of what’s worth your attention and what it means for your org.
Salesforce Summer’26 Release Quick Summary
#Trailhead #Salesforce Admin #New Releases #Flow #Agentforce #Salesforce Developer
I look forward to reading your review and take on the new features in every release. Thanks for doing this!
Read the following articles to improve your Salesforce knowledge.
@* Salesforce Administrators * @* Release Readiness Trailblazers * @* Lightning Now! *@* Sales Cloud - Best Practices * @* Sales Cloud - Getting Started *@Salesforce Flow Automation @Salesforce Automation Hour @Lightning Flow Discussions @The Blog Group @* Salesforce Developers * @* Experience Cloud * @* Service Cloud * @Salesblazer Community Group
Read the following articles to improve your Salesforce knowledge.
@* Salesforce Administrators * @* Release Readiness Trailblazers * @* Lightning Now! *@* Sales Cloud - Best Practices * @* Sales Cloud - Getting Started *@Salesforce Flow Automation @Salesforce Automation Hour @Lightning Flow Discussions @The Blog Group @* Salesforce Developers * @* Experience Cloud * @* Service Cloud * @Salesblazer Community Group
Read the following articles to improve your Salesforce knowledge.
I created a flow for lead routing based on this video Round Robin Assignment Using Flow - YouTube published by @Salesforce Automation Hour. We needed something custom that could adapt to people being out of office and changing the number of group members in the Round Robin.
It works great when one lead comes in at a time. However when we import leads it assigns all leads matching the account type decision to the first group member rather than assigning one record and then assigning the next record to the next group member.
I am guessing I need to add a loop somewhere but not sure where/how.
Untimely we need it to work if it is one lead or an import. #Flow #Automation
Honestly, the issue happens because when you import a bunch of leads, the flow fires for all of them at the same time and they all grab the same first user before the “last assignment date” gets updated. The easiest fix is to add a
scheduled path so the assignment happens a minute later instead of instantly. That way each record processes one after another and the round robin actually rotates. You don’t really need a loop unless you want to redesign the whole thing—just delay the assignment step and it’ll work for both single leads and imports.If you want an alternative to building this yourself, you could try LeadAngel, LeanData kind of tools.. they already have lead assignment / routing built in, with support for round robin, availability, out-of-office, etc.
Read the following articles to improve your Salesforce knowledge.
@* Salesforce Administrators * @* Release Readiness Trailblazers * @* Lightning Now! *@* Sales Cloud - Best Practices * @* Sales Cloud - Getting Started *@Salesforce Flow Automation @Salesforce Automation Hour @Lightning Flow Discussions @The Blog Group @* Salesforce Developers * @* Experience Cloud * @* Service Cloud * @Salesblazer Community Group
Hi everyone!
I've created a date-based workflow rule that sends an email alert to an opp owner when the opp's close date is a day away. I've created an email template and manually test it to make sure it is succesfully sent. In short, the email successfully goes through (whether manually triggered by testing or by the time-based Workflow Rule) and it is received by the Opp owner (me).
... However, the {!Opportunity.Id} seems to be truncated (effectively missing its last three characters); instead of
https://xyz-dev-ed.develop.lightning.force.com/lightning/r/Opportunity/006Hu00001Z2FlnIAF,
... the Opp Id only shows
https://xyz-dev-ed.develop.lightning.force.com/lightning/r/Opportunity/006Hu00001Z2Fln
I've created another time-based workflow just to rule out a one-off glith on my original workflow rule, but the {!Opportunity.Id} object will always be missing the last 3 chars in the body of the message.
I understand that Workflow Rules are to be deprecated but I wonder if anybody else has faced this situation any lately, and how it's been addressed; thank you for your time!
What you are seeing is the difference in the 15-digit (case sensitive) and the 18-digit (case insensitive) Record Ids. Both are valid and are used at different points in the system, although I can't always explain why. For example, if I want to use an ID in a VR (don't--it's bad practice but highlights the example here), I need the 15 digit version; the 18-digit version won't fire the rule. If I plan to do a data load to update records, the 18-digit version should be used to be absolutely sure you have the correct record because while really, SUPER unlikely, it is possible there would be another record with the same 15-digit Id. I've not personally experienced it, but I've heard horror stories.
Yay! I just got AI Specialist Certified. This is a fairly difficult exam, to be honest.
Cert # 23.
Meredith Anglin and I collaborated on a blog post for Salesforce Break to share my study tips.
If you are planning on taking the exam, make sure you check out the post and the links for training resources.
How to Pass the Salesforce AI Specialist Exam - Link: https://salesforcebreak.com/2024/09/09/becoming-a-salesforce-ai-specialist/
Happy studies.
I passed my certification exam this week and I owe it all to Examforsure. The questions were very similar to the real exam. Thank you!!
Read the following articles to improve your Salesforce knowledge.
