Salesforce Flow Naming Convention
Create Salesforce Test Records with Ease
May 8, 2019
What Happens When a Salesforce Record is Saved?
August 29, 2020
One of the things I’ve learned over the years of writing code, is that following a good naming convention makes my life so much easier. Consistency is good as it allows me to more quickly identify what I’m working with and find common items. It simply makes life easier.
When I started using Salesforce Flow, I struggled for a bit as I wasn’t sure how to approach this idea of a naming convention for Flow. I did a little digging to see what others had done. I then pulled together what I felt was a couple of good options. The images below represent what I’ve found to be quite effective.
It’s not important that my naming convention be followed as much as you find what works for you. Be consistent. You’ll find it will save you much heartache later. Your work will appear more professionally written and others will more quickly be able to understand your flows.
Another helpful article from TerrysTidbits about using a good naming convention when building #Salesforce #Flows Click To TweetHope you found this tip helpful. If you have more ideas regarding Flow Naming Conventions, I’d be glad to hear it in the comments below.
2 Comments
Thanks for the post. I am not sure I personally like using prefixes like this in flows. Inside the flow builder under the manager, all the resources and elements are separated by type. When I am looking for something I like to see the descriptive name first without the type prefix to the left of it. But I do understand the value of using these in some situations.
That is true, but if you use a prefix you can also do a search in the Search box and see all related items.