As your Salesforce instance grows, you’ll appreciate following a standard naming convention.
What exactly is a naming convention and why would you bother?
It’s a standard on how to name your objects, fields, buttons, permission sets, flows, flow variables, apex classes, apex variables, reports, and so on.
A common naming convention ensures your Salesforce instance doesn’t look like it was built by a dozen different admins, each with their own language on how to name things.
Imagine seeing a list of flows with names such as:
- “Opportunity Created – Before Save”
- “Update the related contacts when the account becomes inactive”
- “Trigger flow that runs daily – v2 on Nov 15, 2023”
- “ScreenFlow_NewOptyOnAccountPage”
Shoot me now…
Your naming convention can be shared with new Salesforce participants, as part of their on-boarding process. Then review their initial work to ensure they are following the convention.
Creating a naming standard is most useful at the start of a new Salesforce implementation. However, it’s not too late in the middle of a project, or during an improvement sprint. Just be cautious with renaming API names, as they may be tied to integrations.
The takeaway
Having a naming convention is helpful for creating standards and consistent deliverables. The convention itself doesn’t really matter, only that your team is following it.