How to Create Fields and Best Practices

A practical guide to creating custom fields in Salesforce and best practices for field creation.

  • 5 min read

Creating Custom Fields in Salesforce: A Practical Guide

Salesforce is a powerful customer relationship management (CRM) platform that enables organizations to customize their data model to meet specific business needs. Custom fields are fundamental to this customization, allowing you to track information unique to your organization.

This guide covers creating custom fields in Salesforce and best practices for field creation that will help you build an effective, maintainable data model.

Steps to Create Custom Fields in Salesforce

Creating custom fields in Salesforce is straightforward. Follow these steps:

  1. Sign in to your Salesforce organization
  2. Click the Gear icon in the top-right corner and select “Setup”
  3. Navigate to Object Manager in the left navigation menu, where you can manage objects and their components, including custom fields

Creating a New Custom Field

  1. In Object Manager, select the object where you want to add the custom field
  2. Click on “Fields & Relationships” to access the fields management area
  3. Click the “New” button to create a new custom field
  4. Choose a data type for your custom field. Options include:
    • Text (various lengths)
    • Number
    • Date/Date Time
    • Picklist
    • Checkbox
    • Email
    • Phone
    • URL
    • And many more
  5. Click “Next” and configure field properties:
    • Field Label: The display name users will see
    • Field Name: The API name (auto-generated from label)
    • Help Text: Optional description for users
    • Default Value: Optional default value
    • Required: Whether the field must be populated
  6. Set field visibility and field-level security to control who can see and edit the field
  7. Add the field to page layouts so users can see and interact with it
  8. Click “Save” to complete the field creation

Best Practices for Field Creation

Following best practices ensures your Salesforce org remains organized, maintainable, and user-friendly:

1. Plan Before Creating Fields

Before creating fields, map out your organization’s data requirements. Identify:

  • What information needs to be tracked
  • Which objects need new fields
  • How fields relate to each other
  • Whether existing fields can be reused

Why This Matters: Creating duplicate or unnecessary fields leads to data inconsistency, user confusion, and maintenance challenges. Planning helps you build a clean, efficient data model.

2. Use Clear, Descriptive Names

Field labels and names should be:

  • Clear and descriptive
  • Consistent with naming conventions
  • Free of abbreviations (unless widely understood)
  • Aligned with business terminology

Why This Matters: Clear naming helps users understand what each field represents, reducing training time and user errors.

3. Choose the Right Data Type

Selecting the appropriate data type is crucial for:

  • Data validation and quality
  • User experience (proper input controls)
  • Reporting and analytics capabilities
  • Integration with external systems

Best Practices:

  • Use Email data type for email addresses (enables email validation)
  • Use Number data type for numeric values (enables calculations)
  • Use Picklist for standardized options (ensures data consistency)
  • Use Date/Date Time for temporal data (enables date-based reporting)

4. Set Default Values When Appropriate

Default values can:

  • Save users time on data entry
  • Ensure consistency across records
  • Reduce errors from manual entry
  • Improve data completeness

When to Use Defaults:

  • Common values that apply to most records
  • Calculated values that don’t change
  • Values that serve as starting points for user input

5. Implement Field-Level Security

Field-level security controls who can:

  • View field data
  • Edit field data
  • Create records with field values

Best Practices:

  • Restrict sensitive data to authorized users only
  • Use profiles and permission sets for security
  • Regularly audit field-level security settings
  • Document security requirements

6. Enable Field History Tracking

Field history tracking records changes to field values, providing:

  • Audit trails for compliance
  • Change history for troubleshooting
  • Data quality monitoring
  • User activity tracking

When to Enable:

  • Critical business fields
  • Fields subject to regulatory requirements
  • Fields used in important business processes
  • Fields that change frequently and need tracking

7. Organize Fields Logically

Organize fields in page layouts by:

  • Grouping related fields together
  • Using sections to separate field groups
  • Placing most important fields at the top
  • Maintaining consistent organization across layouts

Why This Matters: Logical organization improves user experience, reduces training time, and makes data entry more efficient.

8. Test Before Deploying

Always test custom fields in a sandbox before deploying to production:

  • Test with various data scenarios
  • Verify field-level security works correctly
  • Ensure page layouts display properly
  • Validate formulas and default values
  • Test with different user profiles

Why This Matters: Testing reduces the risk of errors, data issues, and user confusion in production.

Common Field Types and Use Cases

Text Fields

Use For: Names, descriptions, notes, comments Best Practices: Use appropriate length limits, consider rich text for formatted content

Number Fields

Use For: Quantities, amounts, percentages, scores Best Practices: Set appropriate decimal places, use currency format for money

Picklist Fields

Use For: Standardized options, categories, status values Best Practices: Keep options concise, use dependent picklists for related choices

Date/Date Time Fields

Use For: Dates, timestamps, deadlines, milestones Best Practices: Use Date for dates only, Date Time for precise timestamps

Lookup/Master-Detail Fields

Use For: Relationships between objects Best Practices: Understand the difference between lookup and master-detail relationships. See our guide on master-detail relationships.

Resources

Conclusion

Creating custom fields in Salesforce is a fundamental skill for administrators. By following best practices—planning ahead, using clear names, choosing appropriate data types, implementing security, and testing thoroughly—you can build a data model that supports your organization’s needs while remaining maintainable and user-friendly.

Master the art of custom field creation and unlock the full potential of your Salesforce platform.