|
Label
|
A name used to refer to the object in any user interface pages. |
|
Plural Label
|
The plural name of the object. If you create a tab for this object, this name is used
for the tab. |
|
Starts with a vowel sound
|
If it’s appropriate for your org’s default language, check if your label should be
preceded by "an" instead of "a". |
|
Object Name
|
A unique name used to refer to the object when using the API. In managed packages,
this unique name prevents naming conflicts on package installations. The Object Name field
can contain only underscores and alphanumeric characters. It must be unique, begin with a
letter, not include spaces, not end with an underscore, and not contain two consecutive
underscores. |
|
Description
|
An optional description of the object. A meaningful description helps you remember the
differences between your custom objects when you’re viewing them in a list. |
|
Record Name
|
The name used in page layouts, list views, related lists, and search results. |
|
Data Type
|
The type of field (text or auto-number) for the record name. Records that have unique
IDs instead of names use auto-numbers. An auto-number is a unique number assigned
automatically. It’s always a read-only field. |
|
Allow Reports
|
Makes the data in the custom object records available for reporting purposes.
To
create reports on custom objects, choose the Other Reports report
type category, unless the custom object has a relationship with a standard object. When the
custom object has a master-detail relationship with a standard object or is a lookup object
on a standard object, select the standard object for the report type category
instead.
|
|
Allow Activities
|
Allows users to associate tasks and scheduled calendar events related to the custom
object records. |
|
Track Field History
|
Enables your org to track changes to fields on the custom object records, such as who
changed the value of a field, when it was changed, and what the value of the field was
before and after the edit. History data is available for reporting, so users can easily
create audit trail reports when this feature is enabled. |
|
Enable Divisions
|
If your org has divisions enabled, select this option to enable the custom object for
divisions. Divisions group records for simplified search results, list views, reports, and
other areas within Salesforce. Salesforce adds a Division field to the
custom object. If the custom object is the master in a master-detail relationship, custom
objects on the detail side also get the Division field and inherit
their division from the master record. |
|
Available for Customer Portal
|
This option makes the custom object available through the
Salesforce Customer Portal. |
|
Namespace Prefix
|
In a packaging context, a namespace prefix is a one to 15-character alphanumeric
identifier that distinguishes your package and its contents from packages of other
developers on AppExchange. Namespace prefixes are case-insensitive. For example, ABC and abc
aren’t recognized as unique. Your namespace prefix must be globally unique across all
Salesforce orgs. It keeps your managed package under your control exclusively. |
|
Deployment Status
|
Indicates whether the custom object is visible to other users. |
|
Add Notes & Attachments...
|
Allows users to attach notes and attachments to custom object records. You can attach
external documents to any object record, in much the same way that you can add a PDF or
photo as an attachment to an email.
This option is only available when you’re creating an
object.
|
