Oh man…so much good stuff in the new release. And a real bummer.
Add a lookup component in Flow
I’m really disappointed about this. I was confusing “lookup” with “search.” I want to search for any record I want and get a list returned. Nope. I can search using any lookup field I already have. This is good, but not quite what I was thinking.
RIP Bailey Bones, my beloved companion of 14 years.
Unsatisfying use case : A dog turned in at the animal shelter has a microchip number (text field) which I want to use to search for potentially matching dogs. I want to look up a dog in my flow then process their intake at the shelter.
Possible solution: I could do this if I had the microchip number in the name of animal, like Bailey 238392, and I looked it up to the animal record from say, an adoption record. It has to already be a lookup field.
Satisfying use case: Let’s say I am processing an animal record for adoption. From the animal’s record, I can lookup the Contact record of the person who is adopting the animal as part of my animal adoption flow.
Note: you can do a work around for this kind of search. Thanks Jenwlee.
UPDATE 6/13: Thank you everyone for your interest in this solution! I am working on adding it to the AppExchange through Salesforce labs!
At TrailheaDX I ran around like a bird for a video with Einstein and Astro. I also facilitated a lively Circle of Success (small group conversation) on Process Automation. Everyone shared their best practices, asked questions and learned from each other. The admins’ orgs ranged from a 10-free-licenses nonprofit to a giant health insurance company, and years of experience from 0 to 10 (not me! I’m at 8, I think).
One guy (and I’m so sorry I don’t have his name) asked:
“Is there any way to track how often your automation fires?”
That got us thinking. What if you could find out:
How much time am I saving with this automation?
How many times has this process ever fired?
Was the time I spent building this thing worth the investment?
The benefits of sending email directly from Salesforce are that you can automate when they go out, you can send up to 5,000 emails per day, and email templates are really simple to set up.
Dear Asses and Donkeys Trust, I no longer want to receive your email. XOXO, Belinda
But any time you’re emailing groups of people, you should be mindful of the requirements of the CAN-SPAM law (which I just learned isn’t called the “Canned Spam” law). CAN-SPAM requires that emails, in certain scenarios, provide an option for the recipient to unsubscribe.
I am writing to you on my personal blog as a puzzle-solving Salesforce admin, not a Salesforce employee. Your decisions around unsubscribe options can have legal implications for your organization so please do not take anything from this post as legal guidance or means to make your communications legally compliant. That decision is between you and your lawyers.
Maya, Zach, Thomas and I traveled down to Portland for Forcelandia earlier this month for the amazing admineloper conference. I was so excited to share my love of Flow loops in my first regional conference presentation!
Forcelandia is held at The Kennedy School, an old elementary school turned into a hotel by McMenamin’s.
Flow Loops unlock incredible power previously held only by devs. Without using any code, Admins can create an automated process to loop through all related records and take actions based on what is found there!
Demo scenario 1: Hollywood for the Holidays’ will connect you with a celebrity to spend the holidays with! Folks fill out the lead form with an interest and a holiday. Our Flow will loop through all confirmed celebrities and create an opportunity for each celebrity. Continue reading →
If you’re a Developer, you’re probably fairly familiar with your org’s Governor Limits (CPU Time, SOQL queries, DML operations). But if you’re an Admineloper or Business Analyst, excited to design automation with new tools like process builder and visual flow, you might not be taking these limits into account, and subsequently hitting errors.
This last week I had the immense pleasure of presenting on this topic at Forcelandia. My session provided an overview of Governor Limits, how they pertain to Process Builder and Flow, and tips for avoiding hitting these limits with your clicks-not-code automation.
As a more advanced Salesforce admin/configurator/”admineloper”/consultant (i.e. all the hats but dev), it’s often hard for me to find content at conferences that hits that sweet spot right before one ventures into code. I’m talking Custom Settings, advanced formula logic, Custom Metadata Types, integrations and external objects, cool deployment tools, and of course, flows and all they have to offer, etc! When I look for content I don’t want to watch another training on how to set up Sales Path or how to use process builder, I’ve got that covered, and when I do have questions I can usually find the answer using searchtheforce.com. That is why this year I’m super excited for all the advanced admin content offered at Forcelandia.
Salesforce’s Visual Workflow and Process Builder are incredibly powerful tools but can be very difficult to troubleshoot. I struggled to make these tools effective until I was able to get a glimpse of what was happening inside. Salesforce has some suggestions for how to troubleshoot failing flows but often these tools provide incomplete answers. Particularly for auto launched flows, these techniques are often insufficient.
Answering why this failed doesn’t have to be a rabbit hole.