Custom objects have an associated name field that is defined by your Salesforce administrator. Custom fields must have unique names within the same object. In the API, the names of custom fields are identified by a suffix of two underscores immediately followed by a lowercase “c” character.
Full Answer
What are namespace prefixes in Salesforce?
The Salesforce application supports the use of namespace prefixes. Namespace prefixes are used in managed AppExchange packages to differentiate custom object and field names from names used by other organizations. When creating a namespace, use something that’s useful and informative to users.
How to work with text formula fields in Salesforce?
Tips for Working with Text Formula Fields Standard Action Overrides Using the Metadata API to Deploy a Site Style Pane Properties Configure Salesforce Sites Planning and Implementing a Site.com Website Duplicating a Site.com Site Manage Salesforce Sites Standard Pages
What features are supported by Salesforce connect picklist limitations?
More Features Supported by Salesforce Connect Picklist Limitations Define and Manage Platform Events Salesforce Connect Learning Map Salesforce Connect Adapters Included per Add-On License External Data Sources With Salesforce Connect Salesforce Console Salesforce App Named Credential as Callouts for Salesforce Connect OData 2.0 or 4.0...
How to recover deleted fields in Salesforce classic?
Manage Deleted Fields in Salesforce Classic Deactivate and Reactivate Values Set Up the External Data Source and the External Object Record IDs for Salesforce Connect External Objects
Objects That Support Custom Fields
To identify the standard objects that support custom fields, see the table in Relationships Among Custom Objects.
Naming Conventions for Custom Fields
Custom objects have an associated name field that is defined by your Salesforce administrator. Custom fields must have unique names within the same object.
External ID Attribute on Custom Fields
In the user interface, you can identify one custom field on an object as being an external ID field. The field type must be a text, number, or email field. An external ID contains record IDs from a system outside of Salesforce. You can match against this field during import or integration, or when upserting records.
Uniqueness for Custom Fields
In the user interface, you can specify that a custom field on a custom object contain unique values across all the records of that custom object type. The uniqueness can be either case sensitive or case insensitive.
Default Values in Custom Fields
The user logged in for API activity must be have the “Customize Application” permission.
Managed Packages and API Names
If you have an unmanaged package and a managed package version becomes available, the API names of custom fields, custom objects, and Scontrol objects in the package change. A namespace prefix is added to each component to make it unique: name __c becomes prefix __ name __c.