Hurray! Our own blogger Maya Peterson is featured in this week’s GeekWire as Geek of the Week, which “profiles the characters of Pacific Northwest tech, science, games, innovation, and more.”
On March 1, 2020, the official start of Spring ’20 in our world, comes needed security improvements regarding sharing data with external users. However, you can uncheck the Secure guest user record access checkbox and test out these changes until Summer ’20. Phew. If you’re using any Site Guest Users, and are ready to try out the new settings you’ll need to create new sharing rules. Hint: Salesforce sites are used in Volunteers for Salesforce and frequently in Communities.
What’s a Salesforce Site? “Salesforce sites enables you to create public websites and applications that are directly integrated with your Salesforce.com organization—without requiring users to log in with a username and password. You can publicly expose any information stored in your organization through pages that match the look and feel of your company’s brand. Use sites to create public community sites to gather customer feedback, branded login and registration pages for your portals, Web forms for capturing leads, and so on.” — the Site setup page in Salesforce. Continue reading →
Question: When a contact dies, how can you use Flow to delete their Opportunity Contact Roles for open opportunities? Answer: With a Loop!
Use common sense. Install and test thoroughly in a sandbox! You’re deleting records! I made it really quickly and did not test thoroughly!
Here are the requirements as posted by Ashlynn on the Power of Us Hub:
“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.
Thanks to Alex Edelstein and UnofficalSF.com for an unmanaged package that performs this magic for us! Watch my video of how I use the “Map Collection” apex action to update the Activity Type of 5,000 records! Continue reading →
Hip hip hurray! My unmanaged package Unsubscribe Link is now available for free on AppExchange! This package will allow your constituents to unsubscribe from all emails for your organization.
The package includes an automatic confirmation email, but you can turn that feature off. Watch the video below and/or follow these instructions: Continue reading →
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.
Critics who viewed our sessions at Forcelandia called them “Hilarious!” “Informative!” “The best!” If you’re coming to the big event, don’t miss out!
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.
Allow Recipients to Unsubscribe from All Emails
Follow this tutorial to include an unsubscribe link in promotional emails sent from Salesforce. This post gives you some reasons for considering this feature.
When the recipient clicks to unsubscribe, a flow will look for all contacts and leads who have this as their preferred email address (if you’re in NPSP) or in the Email field. All contacts or leads who meet that requirement will be marked “Email Opt Out.” The email address owner will receive one confirmation email immediately.
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.
Thanks to everyone who expressed an interest in my June 5, 2019 post “Was it worth my time to automate that?” The solution is now available on the AppExchange from Salesforce Labs! Check it out!
Have you ever wondered:
- 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?
- Are the people who requested this automation actually using it? If not, who is?