Jessie is Success Content Specialist at Salesforce.org. All opinions expressed on this blog are her own or those of the contributors. For fourteen, she has specialized in CRM, email marketing and fundraising platforms. Jessie co-led the Seattle Salesforce Non-Profit User Group in 2015-2016. She wrote a sh*tty first draft of a novel and hopes to do something with it some day.
“I am trying to set up an autolaunched flow to remove Opportunity Contact Roles from open opportunities with deceased contacts. (For example, we are soliciting a major gift from a couple, and one of them passes away before the donation is received.) I have successfully configured a process to remove the deceased contact from acknowledgement for that gift when it comes in, but for the sake of clean data I would like to also automatically remove their OCR from the opportunity record. I am coming up with ‘unhandled faults’ and hoping since this is only my 2nd flow ever that someone will be able to see an obvious error with my configuration.
Dude. With the Spring ’20 release, we can now update 1000s of records at a time in Flow. The release itself doesn’t give us this power directly, but it allows developers to create invocable apex actions that can be reused for many objects.
Learning how to build a Flow is like interacting with a volunteer who…needs some extra help. Through these videos, I explain some of the trickier flow concepts for admins: “get records” and “record variables.” I was lucky enough to give his presentation at Dreamforce 2019.
Good news: in this version I have unlimited time so I’ve shown all the steps in detail.
More good news: this presentation doesn’t actually utilize anything specific to nonprofits so it’s suitable for you Sales Cloud folks as well.
Wednesday, 12pm Westin St. Francis with Salesforce.org staff Jessie Rymph
Flow is a powerful automation tool that walks users through screens, updates multiple objects at once, and reaches distantly related records all with clicks-not-code. By learning Flow, nonprofits can surpass the limitations of Process Builder and harness the power of code without actually having a developer on staff. In this session, we’ll demystify record variables, “get records”, and other elements that are often unfamiliar to non-coders. Participants will walk away with an understanding of the *why* behind each step in the flow creation process!
Thursday, 11:30am Moscone West with MVP Maya Peterson
One process to rule them all, one process to find them, one process to bring them all and in the invocation bind them. As a best practice Salesforce now recommends restricting your org to one record-change process per object. Truly a tool of great power. In this session you’ll learn tricks to manage process criteria nodes using Custom Metadata Types, Custom Settings, and Custom Permissions. No harrowing trip to Mount Doom required.
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.
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?