(This solution works in both Classic and Lightning Experience.) Your company is using Salesforce campaigns. You need to also give your contacts the ability to opt out of marketing campaigns. Currently, a contact who has opted out of marketing campaigns may be added to a campaign. The marketing user then needs to run a report… Continue reading Remove a Contact from Campaign(s) When Opt Out Marketing Campaigns
(This solution works in both Classic and Lightning Experience.) This blog post was inspired by a use case from Stephanie Herrera where she needed to push an opportunity record’s multi-select picklist values to a custom object for data quality review. Ok, ok, ok…I know, multi-select picklists are evil. This is the infamous image from… Continue reading Passing Multi-Select Values From One Object to Another Object
[Note: This use case/solution can be implemented in both Classic and Lightning Experience.] I’d like to give a shout out to my community friend, John Lay, for being the inspiration for this blog post. He had recently reached out to me on advice on this very error in his process. Ever create a process that… Continue reading The flow failed to access the value for myVariable_Field because it hasn’t been set or assigned.
[Note: This use case/solution can be implemented in both Classic and Lightning Experience.] While process builder has the ability to post to chatter, its capabilities are a bit simplistic. In process builder, you can post to a user, a chatter group or the record. There is no ability to @mention multiple users dynamically. Users can… Continue reading Automate Chatter Post That @Mentions Several Users
This blog post was inspired by Randi Thompson. Here’s to you, Randi! Here are a few lessons learned from implementing this use case: Learn how to invoke flow from process builder. Use custom labels to avoid hardcoding Salesforce record type Ids in flow. Provide descriptions, where provided, in Salesforce. This may be tedious step, I… Continue reading Create a Person Account For New Email-to-Case
Developers know that it is not a best practice to hardcode IDs in code, as documented in the Salesforce Developers site. https://developer.salesforce.com/page/Best_Practice:_Avoid_Hardcoding_IDs It is a big pet peeve of mine when I see hardcoded IDs in formulas, validation rules, process builder, flow, etc. The same best practices apply on the declarative side as with the development… Continue reading Did I Just See You “Hardcode” a Salesforce ID? Aw, Hell No!