Our current Salesforce org has custom fields named things like 'Field 1' or 'New Temp'. It is impossible to tell what they do or who created them. I want to implement a strict naming convention before it gets any worse.
Does anyone have a template for naming conventions that includes naming objects, fields, flows, and validation rules? I would love to hear how you enforce this in a team with multiple developers and admins who have different styles.
A standardized Salesforce metadata naming convention should follow a prefix-based schema incorporating the functional area, business process, and specific descriptor to ensure maintainability and clarity across development teams.
1 answer
Stop treating your metadata like a junk drawer and implement a prefix-based schema immediately. Use the format [FunctionalArea]_[BusinessProcess]_[Description] for fields and flows, and enforce it by failing any pull request that ignores the convention.
If you lack the discipline to reject non-compliant deployments at the gate, no template in the world will save your org from becoming a technical debt disaster.
