Data Modelling :Creating custom object and fields
Note: All credit goes to Salesforce, I am just a developer who enjoy playing trailhead and try to make note to myself.
Best Practices for Custom Objects and Fields
- Unique naming: Make object and field names and labels concise, specific, and descriptive. And very importantly, unique. For example, if your recruiting app’s Position object has a field named Skill Set, use something like Candidate Skill Set on the Candidate object to describe applicants’ skills.
- Thoughtful architecture: When adding fields to an object, what’s the cleanest and most efficient way to capture data? For example, instead of a long list of checkboxes to track the regions that currently have a particular position open, use a picklist.
- Default field values: Don’t assign default values to fields that are both required and unique, as this can cause uniqueness errors.
- Careful renaming: If you’ve renamed objects or fields, check that these items reflect the new names:
- List view names
- Standard report names or descriptions that include the objects or fields
- Email templates that contain the object or field names
- Any other items you customized along with the renamed object or field — custom fields, page layout, or record types
- Global data updates: Before changing a field type (for example from checkbox to picklist), make sure the change makes sense for all records that have that field.