(Note: This blog post only applies to Lightning Experience. You cannot invoke a flow from a quick action in the Salesforce Classic UI.) The business wants the ability to quickly create an opportunity record from a contact with minimal number of fields and create/associate this contact as the primary contact and “Decision Maker” on the… Continue reading Create a New Opportunity From a Quick Action w/ Specific Record Type Based on the User’s Profile
I am excited to see my Idea listed as one of the ideas to be delivered in the near future at Parker Harris’ True to The Core Dreamforce 17 session and to be in the pilot for referencing custom metadata types in validation rules. Thank you, Vlad! Note: The blog post will cover a description… Continue reading (Spring 18 Preview) Reference Custom Metadata Type Records in Validation Rules (Pilot)
[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
I want to give a shout out to Bryan James, developer at MapAnything, for assistance on identifying the MapAnything customized user settings. Thank you for your help, Bryan! You’re the best! Here are a few lessons learned from implementing this use case: Learn how to automate package license assignment or removal on other criteria that is… Continue reading Automate the Assignment/Removal of MapAnything License and User Settings Based on User Role
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!
When a user is deactivated from Salesforce, there is cleanup work that is needed after the fact if you want to keep your org relatively free of “clutter.” In most cases, leaving inactive users associated to public groups, queues, permission sets, etc. is fairly harmless. As I mentioned before, it’s just clutter in your org.… Continue reading Automated Cleanup When User Is Deactivated – Managed Package Licenses
This blog post walks through the best solution featured in a prior blog post “Build Efficient, Performance Optimized Processes, Part 2.” Here are a few lessons learned from implementing this revised use case: Uses only one record create task flow element to create the task record with different wait times in addition to the appropriate… Continue reading Different Wait Times for Task Creation