What does this post cover?
- Understand the value of naming conventions in your org
Use Case:
If you have ever been to a hotel more than once you probably have noticed there is a system to finding where your room is located. Does your room say 5100? Great - head the elevator and go to the 5th floor and then find a door with the number 100 on it. The first number assigned (5) refers to the floor level. The numbers trailing (100) refer to the actual number on your door. Why do this? It's efficient. Hotel workers spend less time directing guests and more time doing things they actually need to get done. This system they use is the same type of organization we want to apply to your Salesforce org.
[INSERT MY OWN IMAGE HERE TO EXPLAIN]
Terms to Know:
PascalCase = PascalCase is a naming convention in which the first letter of each word in a compound word is capitalized. Software developers often use PascalCase when writing source code to name functions, classes, and other objects.
camelCase = camelCase is a naming convention in which the first letter of each word in a compound word is capitalized, except for the first word. Software developers often use camelCase when writing source code.
SNAKE_CASE = Snake case is a naming convention in which a developer replaces spaces between words with an underscore.
Natural Text = Natural text is how you would formally write.
Instead of myself coming up with how you should name your items in salesforce I went and found the best practice from Salesforce themselves to link here for you.
I also researched and found that Amanda Bailey had published a great article on Focus on Force that focused on naming conventions for admins. Those screenshots are below ↓
