If Salesforce objects are like database tables, then fields are the columns — each one stores a specific piece of information about a record. Fields are the fundamental unit of data storage in Salesforce, and mastering them is one of the first skills every Salesforce Admin must develop.
For example, the standard Account object contains fields like Account Name, Phone, Website, and Annual Revenue. Each of these fields has a specific data type that determines what kind of data it can hold and how users interact with it.
Every field in Salesforce belongs to one of two broad categories: Standard Fields and Custom Fields.
Key Concept: Fields = Columns in a Database Table. Objects = Tables. Records = Rows. Understanding this analogy is the foundation of Salesforce data modeling.
Standard Fields vs. Custom Fields in Salesforce
Standard Fields
Standard fields are pre-built by Salesforce and exist on every object by default. You cannot delete them, but you can customize some of their properties such as labels, help text, and picklist values.
Common examples of standard fields include:
- Name — Every record has a Name field. It can be a plain text field or an auto-number field.
- Owner — Links a record to the user responsible for it. Critical for access control, queues, and assignment rules.
- Created By / Last Modified By — System-managed read-only fields that automatically track who created or last changed a record and when.
- Record Type — Controls which page layout and picklist values a user sees, based on their profile and the selected record type.
- Identity Fields — 15-character (case-sensitive) or 18-character (case-insensitive) unique identifiers automatically assigned to every record.
Custom Fields
When standard fields cannot capture the data your business needs, you create custom fields. Custom fields are identified by the __c suffix in their API name (e.g., Preferred_Contact_Time__c).
Custom fields give you the freedom to tailor Salesforce to your exact business processes — for example, adding a “License Expiry Date” field to the Account object for a software company, or a “Vehicle Registration Number” field for an automotive business.
Custom fields can be added to any standard or custom object, and Salesforce allows up to 800 custom fields per object (limit varies by edition).
Standard vs. Custom Fields — Quick Comparison
| Feature | Standard Fields | Custom Fields |
|---|---|---|
| Created By | Salesforce (pre-built) | You (Admin/Developer) |
| API Name Suffix | e.g., Name, OwnerId | Ends with __c |
| Can Delete? | No | Yes |
| Editable Properties | Limited | Full control |
| Counts Toward Field Limit? | No | Yes |
All Field Data Types in Salesforce — Explained with Examples
Choosing the right field data type is one of the most important decisions a Salesforce Admin makes. Once a field is created and data has been entered, changing its type can cause data loss. The table below covers every field type available in Salesforce along with its best use cases.
| Field Type | Description | Best Use Case |
|---|---|---|
| Auto Number | Automatically assigns a unique number to each record | Invoice IDs, Case numbers, Order references |
| Checkbox | True or false toggle for a record attribute | Is Active, Opted-In, Verified Status |
| Currency | Stores monetary values in the org’s currency | Deal Amount, Annual Revenue, Price |
| Date | Captures a calendar date | Contract Start, Birth Date, Due Date |
| Date/Time | Stores both a date and a time of day | Meeting Scheduled At, Last Login |
| Validated email address up to 80 characters | Contact Email, Support Email | |
| Geolocation | Latitude and longitude coordinates | Store Locations, Field Service Mapping |
| Number | Numerical values; leading zeros removed | Quantity, Score, Age, Rating |
| Percent | Decimal stored and displayed as a percentage | Discount Rate, Win Probability |
| Phone | Any phone number up to 40 characters | Mobile, Office Phone, Fax |
| Picklist | Single value from a predefined list | Stage, Priority, Industry, Status |
| Picklist (Multi-Select) | Multiple values from a predefined list | Products Interested In, Skills |
| Text | Letters, numbers, symbols up to 255 characters | Short descriptions, codes, labels |
| Text (Encrypted) | Encrypted text up to 175 characters | License keys, sensitive identifiers |
| Text Area | Up to 255 characters displayed on separate lines | Notes, brief descriptions |
| Text Area (Long) | Up to 131,072 characters on separate lines | Detailed notes, meeting summaries |
| Text Area (Rich) | Formatted text with images and hyperlinks | Knowledge articles, email templates |
| URL | Valid website address up to 255 characters | Company website, LinkedIn profile |
| Formula | Read-only value calculated from other fields | Full Name, Days to Close, Discount Amount |
| Roll-Up Summary | Aggregates child record values (Master-Detail only) | Total Opportunity Amount, Child Count |
| Lookup Relationship | Links records between two objects | Contact’s Account, Opportunity’s Owner |
| Master-Detail Relationship | Tight parent-child relationship | Order Items to Orders, Cases to Accounts |
Special Field Types: Formula, Roll-Up Summary & Geolocation
Formula Fields
Formula fields are read-only fields that automatically calculate their value based on expressions you define. They draw from other fields, functions, and operators to produce a result — and they update in real time whenever the referenced fields change.
Formula fields can return different data types: Text, Number, Date, Date/Time, Checkbox (Boolean), Currency, or Percent. A few powerful real-world examples include:
- Full Name:
CONCATENATE(FirstName__c, " ", LastName__c) - Days to Close:
Close_Date__c - TODAY() - Is High Value:
IF(Amount > 50000, TRUE, FALSE) - Discount Amount:
Amount * Discount_Percent__c
Formula fields do not consume storage space and are one of the most powerful tools in a Salesforce Admin’s toolkit. They are heavily tested in the Salesforce Admin Certification exam.
Roll-Up Summary Fields
Roll-Up Summary fields are only available on Master-Detail relationship objects. They aggregate data from child records and display it on the parent record. Salesforce supports four aggregation types:
- COUNT — How many child records exist
- SUM — Total of a numeric field across all child records
- MIN — The smallest value across child records
- MAX — The largest value across child records
Example: On the Account object (parent), a Roll-Up Summary field can show the total value of all Opportunity records (child) in a Master-Detail relationship, giving sales managers an instant portfolio value at a glance.
Geolocation Fields
Geolocation fields store a physical location using latitude and longitude coordinates. They are used in SOQL queries to calculate distances and in custom map-based applications. This field type is especially useful in industries like field service, retail, real estate, and logistics.
A Geolocation field is actually stored as two separate Number fields internally (Latitude and Longitude), which you can reference individually in formulas and reports.
Admin Tip: Geolocation fields count as three fields against your custom field limit — the geolocation field itself, plus the latitude component field and longitude component field.
How to Create Custom Fields in Salesforce — Step-by-Step
Creating a custom field in Salesforce is a core Admin task. Here is the standard process using Setup:
- Navigate to Setup by clicking the gear icon in the top-right corner.
- In the Quick Find box, type Object Manager and click it.
- Select the object you want to add the field to (e.g., Account, Contact, Opportunity, or a custom object).
- Click on Fields & Relationships in the left panel.
- Click the New button.
- Select a Field Data Type from the list and click Next.
- Fill in the Field Label, and optionally the Field Name (API Name), Description, and Help Text.
- Configure Field-Level Security to control which profiles can see or edit the field.
- Choose which Page Layouts to add the field to.
- Click Save. Your new field is now live!
Best Practice: Always fill in the Description and Help Text fields when creating custom fields. This helps your team understand the field’s purpose directly in the UI — especially valuable in orgs with large, complex data models.
Field-Level Security and Accessibility
Field-Level Security (FLS) is a critical concept for Salesforce Admins. It controls which users can view or edit each field, based on their assigned Profile or Permission Set. Even if a record is accessible to a user, they may not see all of its fields if FLS restricts access.
Salesforce provides three FLS settings per profile for each field:
- Visible — Users can see the field value on record detail and edit pages
- Read-Only — Users can view the field but cannot change its value
- Hidden (neither Visible nor Read-Only checked) — The field is completely invisible to users with that profile
FLS is separate from page layout visibility. A field can be on a page layout but hidden via FLS — in which case users will not see it. This layered approach is what makes Salesforce’s access model powerful and precise.
Security Reminder: Always configure FLS after creating a sensitive custom field (such as SSN, Bank Account, or Salary). If a field is not restricted by FLS, all users with record access can see it by default — even if it’s not on a page layout, it will appear in reports and list views.
Field Mapping in Salesforce
Field mapping is the process of matching fields from one Salesforce object (or external system) to corresponding fields in another. It is essential in several common admin scenarios:
Lead Conversion Field Mapping
When a Lead is converted, Salesforce maps Lead fields to Contact, Account, and Opportunity fields. You can customize this mapping in Setup to ensure your valuable Lead data flows correctly into the converted records. For example, mapping a Lead’s “Company” field to Account’s “Account Name”, or a custom Lead field to a corresponding custom field on Contact.
Integration Field Mapping
When integrating Salesforce with external tools — such as marketing automation platforms, ERP systems, or data warehouses — field mapping ensures data syncs correctly between systems. Misaligned field mappings are one of the leading causes of data quality issues in integrated Salesforce orgs.
Data Import Field Mapping
When using the Data Import Wizard or Data Loader to import records, you map columns in your CSV file to Salesforce fields. Getting this mapping correct is essential for accurate data migration and bulk imports.
Fields in Salesforce — Exam Tips for Admins
Fields are heavily tested in the Salesforce Certified Administrator exam. Here are the key concepts you must know before exam day:
- Formula fields are read-only and update automatically — you cannot manually edit them.
- Roll-Up Summary fields are only available on the Master (parent) side of a Master-Detail relationship.
- Changing a field’s data type after records have data can cause permanent data loss — this is a high-risk operation.
- The
__csuffix in the API Name denotes a custom field;__rdenotes a relationship field in SOQL. - A Picklist (Multi-Select) field cannot be used in roll-up summaries, certain formula types, or grouping in reports.
- Geolocation fields count as 3 fields against the custom field limit.
- Text fields have a maximum of 255 characters; use Long Text Area for larger content.
- Field-Level Security overrides page layout visibility — FLS is the governing control.
Frequently Asked Questions About Fields in Salesforce
Q: What is the difference between a Text field and a Text Area field?
A Text field holds up to 255 characters in a single line of input. A Text Area also holds up to 255 characters but displays them across multiple lines, making it better for short notes or multi-line addresses. For longer content, use Long Text Area (up to 131,072 characters) or Rich Text Area (supports formatting and images).
Q: How many custom fields can I create per object?
The limit depends on your Salesforce edition and the object type. Most objects allow up to 800 custom fields in Enterprise and Unlimited editions. Some objects have lower limits. Relationship fields and special types like Geolocation count as multiple fields against this limit.
Q: Can I delete a standard field?
No. Standard fields cannot be deleted. You can hide them from page layouts and restrict their visibility using Field-Level Security, but the fields will always exist in the data model. You can, however, delete custom fields — though doing so permanently deletes all data stored in that field.
Q: What is a dependent picklist?
A dependent picklist is a custom or standard picklist whose available values are filtered based on the selection in another picklist (the Controlling Field). For example, if the Controlling Field is “Country”, the Dependent Field “State” would only show states relevant to the selected country. This is a powerful way to guide data entry and maintain data quality.
Q: Can I use a formula field in a roll-up summary?
Yes, you can reference formula fields in a Roll-Up Summary if the formula field returns a Number, Currency, or Percent data type. However, Roll-Up Summary fields themselves are not available on Lookup relationships — only Master-Detail relationships support them.
Conclusion — Mastering Fields in Salesforce
Fields in Salesforce are far more than simple data columns. They are the foundation of your entire data model — they drive automation, power reports, enforce security, and enable integrations. As a Salesforce Admin, your ability to understand, design, and manage fields directly impacts the quality and usability of your entire Salesforce org.
Whether you are building a brand-new object from scratch, customizing a standard object for a business use case, or preparing for the Salesforce Certified Administrator exam, a deep understanding of field types and behaviors is non-negotiable.
Here is a quick recap of what we covered:
- The difference between Standard Fields and Custom Fields
- All 22+ Salesforce field data types with real-world use cases
- Special field types: Formula, Roll-Up Summary, and Geolocation
- Step-by-step process for creating custom fields in Salesforce
- Field-Level Security and how it governs data access
- Field Mapping for Lead conversion, integrations, and data imports
- Key exam tips for the Salesforce Admin Certification
Ready to Become a Salesforce Certified Administrator?
If this guide gave you a solid foundation on fields in Salesforce, imagine what a structured, exam-focused course could do for your career.
- Expert-led, hands-on curriculum
- Real-world scenarios and practice exams
- Lifetime access to course materials
- Community support from fellow learners
The MyTutorialRack Salesforce Admin Certification Course is designed to take you from beginner to certified — covering every topic on the Salesforce Certified Administrator exam, including Data Modeling, Fields, Automation, Security, Reports, and much more.
