Considerations for Creating Custom Objects
Before you create a custom object, make sure that you review these considerations.
Required Editions
| Available in: both Salesforce Classic and Lightning Experience |
| Available in: Contact Manager, Group, Professional, Enterprise, Performance, Unlimited, and Developer Editions |
Object Creation
- Establish object relationships first, before adding all custom fields, page layouts, and related lists.
- The standard Name field is required on custom object related lists and page layouts.
- Provide meaningful names for your custom objects. The plural label of the custom object is used as the label of the custom tab based on that object.
- When you create a custom object, you specify the data type of the Record Name field: Auto Number or Text. If you select the Auto Number data type, there could be issues when inserting a high volume of records, for example, via the API. If you anticipate a high volume of record inserts, use the Text data type.
- When creating an object from a spreadsheet:
- Skipping the import step creates an empty custom object that uses the fields in the spreadsheet as a template.
- You can click
to preview the object data. Only
the first 24 rows of data are displayed in preview. - These field types aren’t supported:
- Auto Number
- Formula
- Roll-Up Summary
- Lookup Relationship
- Master-Detail Relationship
- External Lookup Relationship
- Text Area (Rich)
- Text (Encrypted)
- Time
Object Permissions
In Enterprise, Unlimited, Performance, Professional, and Developer editions, when you create a custom object, the Read, Create, Edit, and Delete permissions for that object are disabled for profiles that have View All Data or Modify All Data disabled. Enable access to custom objects in permission sets or custom profiles, and assign them to the users who need access.
In Contact Manager and Group editions, when you create a custom object, the Read, Create, Edit, and Delete permissions for that object are enabled for all profiles.
Sharing Model
An org-wide default setting controls the data sharing model for custom objects. For more information, see Custom Object Security.
Delegating Custom Object Administration
After you create a custom object, you can delegate its administration to non-admin users.
Queues
After you create a custom object, you can define queues to distribute ownership of custom object records to your users.

