Salesforce objects and fields are analogous to database tables and the table columns. Objects and fields structure your data. For example, the central object in the Salesforce data model represents accounts—companies and organizations involved with your business, such as customers, partners, and competitors.
The term “record” describes a particular occurrence of an object (such as a specific account like “IBM” or “United Airlines” that is represented by an Account object). A record is analogous to a row in a database table.
Objects already created for you by Salesforce are called standard objects. Objects that you create in your organization with the user interface or with the Metadata API are called custom objects. Objects you create that map to data stored outside your organization are called external objects.
While this insight describes all of the objects available in the API, your applications work with only the objects that you are authorized to access. Programmatic access to objects is determined by the objects defined in your organization, your organization configuration, your user permissions and access settings (which are configured by your organization’s Salesforce admin), your data sharing model, and other factors related specifically to the object.
Most of the objects accessible through the API are read-write objects. However, there are a few objects that are read-only. This fact is noted in the description for the object.
For details about the data types and size restrictions for each object’s fields, see the Salesforce Field Reference Guide.
- Salesforce Objects Release Notes
Use the Salesforce Release Notes to learn about the most recent updates and changes to Salesforce Objects.
- Primitive Data Types
- Field Types
- API Field Properties
- Required Fields
- System Fields
- Frequently Occurring Fields
In addition to system fields, these fields are found on many objects.
- Compound Fields
Compound fields group together multiple elements of primitive data types, such as numbers or strings, to represent complex data types, such as a location or an address. Compound fields are an abstraction that can simplify application code that handles the values, leading to more concise, understandable code.
- Custom Objects
In the user interface, you can extend your org’s data by defining custom objects. Custom objects are custom database tables that allow you to store information unique to your organization. For custom objects, the custom flag—a Boolean field in the describe results—is true.
- Custom Fields
- AppExchange Object Prefixes and the API
- Relationships Among Standard Objects and Fields
- Factors that Affect Data Access
Some factors affect access to your organization’s data.
- Field and Type Differences in Salesforce Apps and APIs
- External Objects
External objects are supported in API version 32.0 and later. External objects are similar to custom objects, but external object record data is stored outside your Salesforce organization. For example, perhaps you have data that’s stored on premises in an enterprise resource planning (ERP) system. Instead of copying the data into your org, you can use external objects to access the data in real time via web service callouts.
- Big Objects
A big object stores and manages massive amounts of data on the Salesforce platform. You can archive data from other objects or bring massive datasets from outside systems into a big object to get a full view of your customers. Clients and external systems use a standard set of APIs to access big object data. A big object provides consistent performance, whether you have 1 million records, 100 million, or even 1 billion. This scale gives a big object its power and defines its features.
- Object Interfaces
An object interface defines the business logic that an object implements. The object that implements the interface, called the implementor, stores the data and implements the business logic.