ADM-201 Customization: Fields

Customization: Fields Detailed Explanation

Customization in Salesforce allows administrators to tailor the platform to fit specific business requirements. Fields play a fundamental role in storing data, and understanding how to customize them ensures the system meets unique business needs while maintaining data integrity.

5.1 Field Types

Fields in Salesforce are the building blocks of data storage. They represent individual data points, such as names, phone numbers, or custom calculations.

Standard Fields

• What They Are:
  • Predefined fields included in Salesforce for every object.
  • Examples: Account Name, Created Date, Owner.
• Key Points:
  • Cannot be deleted but can be customized to some extent (e.g., editing field labels or adding help text).

Custom Fields

Custom fields are user-defined fields that meet specific business requirements beyond what standard fields provide.

How to Create a Custom Field

1. Navigate to Setup.
2. Select the object (e.g., Account, Opportunity) where you want to add the field.
3. Under Fields & Relationships, click New.
4. Choose the appropriate field type, define the field properties, and save.

Common Field Types

1. Text:

   • Purpose: Stores alphanumeric characters.
   • Example: "Contact Name" or "Notes."
   • Length: Define a maximum character limit (e.g., 255 characters).

2. Lookup:

   • Purpose: Links one object to another, creating a relationship.
   • Example: Linking a Contact to an Account.
   • Use Case: Allows users to associate a record from one object with another.

3. Master-Detail:

   • Purpose: Creates a stronger, dependent relationship between two objects.
   • Example: Invoices (Detail) and Accounts (Master).
   • Key Points:
     • Child (detail) records cannot exist without a parent (master).
     • Changes to the master record cascade to the detail records.
     • Roll-up summary fields can calculate data (e.g., total invoice amount) on the master record.

4. Formula:

   • Purpose: Dynamically calculates field values based on other fields or logic.
   • Example:
     • Field: "Annual Revenue Per Employee"
     • Formula: Annual Revenue / Number of Employees
   • Key Points:
     • Formula fields are read-only.
     • Automatically update when referenced field values change.

Practical Example

• A business wants to track "Project Status" on Accounts. They create:
  • A Custom Picklist Field for Status (e.g., Not Started, In Progress, Completed).
  • A Formula Field to calculate "Days Left to Deadline" using Deadline Date - Today().

5.2 Validation Rules

Validation rules enforce data quality by ensuring only valid data is entered into fields.

What Are Validation Rules?

• Logical expressions that evaluate whether data entered in a field meets specific conditions.
• If a record fails the validation, Salesforce prevents it from being saved.

How to Create a Validation Rule

1. Navigate to the object where the rule is needed.
2. Under Validation Rules, click New.
3. Define the Error Condition Formula.
4. Add an Error Message to guide the user in fixing the issue.
5. Save and test the rule.

Common Use Cases

1. Ensure "Order Quantity" > 0:

   • Formula: Order_Quantity__c <= 0
   • Error Message: "Order quantity must be greater than zero."

2. Validate Email Format:

   • Formula: NOT(REGEX(Email, "^[A-Za-z0-9._%+-]+@[A-Za-z0-9.-]+\\.[A-Za-z]{2,4}$"))
   • Error Message: "Please enter a valid email address."

3. Require a Field Based on Another Field:

   • Formula: AND(ISPICKVAL(Status__c, "Closed"), ISBLANK(Resolution_Notes__c))
   • Error Message: "Resolution notes are required when status is Closed."

Practical Example

A sales team requires "Expected Close Date" on opportunities:

• Validation Rule:
  • Formula: ISBLANK(Expected_Close_Date__c)
  • Error Message: "Expected Close Date is required for all opportunities."

5.3 Dependent Fields

Dependent fields create dynamic field behavior, improving data accuracy and simplifying data entry.

What Are Dependent Fields?

• Dependent fields restrict available values in one field based on the selected value in another field.
• Two key components:
  1. Controlling Field: Determines the available values in the dependent field.
  2. Dependent Field: Displays filtered values based on the controlling field’s selection.

How to Create Dependent Fields

1. Navigate to the object and open Fields & Relationships.
2. Select or create a picklist field to act as the Dependent Field.
3. Click Field Dependencies and choose a Controlling Field.
4. Map controlling field values to corresponding dependent field values.
5. Save and test.

Example Use Case

• Controlling Field: Country
• Dependent Field: City
  • If "Country" = "USA," only "New York, Chicago, Los Angeles" appear as options in the "City" field.
  • If "Country" = "India," only "Delhi, Mumbai, Bangalore" appear.

Practical Scenarios

1. Product and Sub-Category:

   • Controlling Field: Product Category (e.g., Electronics, Furniture).
   • Dependent Field: Sub-Category (e.g., Phones, TVs for Electronics).

2. Region and Sales Rep:

   • Controlling Field: Region (e.g., North America, Europe).
   • Dependent Field: Assigned Sales Rep (e.g., "John" for North America, "Maria" for Europe).

Step-by-Step Summary

1. Field Types:

   • Use Standard Fields for predefined data points.
   • Add Custom Fields for specific business needs.
   • Leverage Lookup and Master-Detail relationships for linking objects.
   • Use Formula fields for real-time calculations.

2. Validation Rules:

   • Enforce data quality by creating rules to prevent invalid entries.
   • Add clear error messages to guide users.

3. Dependent Fields:

   • Simplify user input by dynamically filtering picklist options.

Key Takeaways for Beginners

• Understand the difference between Standard and Custom Fields.
• Use Validation Rules to maintain data accuracy and integrity.
• Implement Dependent Fields to streamline data entry and reduce errors.

Customization: Fields (Additional Content)

1. Roll-Up Summary Fields (Aggregating Data in Parent Records)

Why is it important?

• Roll-Up Summary Fields allow automatic calculations based on related child records, but they only work in Master-Detail Relationships.
• Useful for tracking totals, averages, and counts of child records in a parent record.

Use Cases

• Summarize numerical values from child records:
  • Count the number of related records.
  • Calculate the total (SUM) of a numeric field.
  • Find the maximum (MAX) or minimum (MIN) value of a date or number.

Example Scenario

• Business Need: A company wants to see the total revenue of all Opportunities related to an Account.
• Configuration:
  • Create a Roll-Up Summary Field on the Account object.
  • Select Opportunities as the child object.
  • Choose SUM of the Opportunity Amount field.
  • Now, each Account record will display the total value of all its related Opportunities.

Key Limitations

• Only available for Master-Detail Relationships (not Lookup Relationships).
• Cannot reference formula fields in the child object.
• Only works with numeric, currency, and date fields.

2. Auto-Number Fields (Generating Unique Record Identifiers)

Why is it important?

• Auto-Number Fields generate unique record numbers automatically, making them useful for tracking records like orders, cases, and contracts.
• Helps maintain data consistency and avoid duplicate record names.

How to Configure Auto-Number Fields

1. Navigate to Setup → Go to the object → Click Fields & Relationships.
2. Click New → Select Auto-Number.
3. Set the Display Format:

• Example: ORD-{0000} → Generates ORD-0001, ORD-0002, ORD-0003...

4. Define the Starting Number (e.g., 1000 instead of 1).
5. Save the changes.

Example Scenario

• A company wants to generate unique Work Order numbers.
  • Auto-Number field format: WO-{000000}.
  • Generated numbers: WO-000001, WO-000002, WO-000003.

3. Geolocation Fields (Storing Latitude and Longitude Data)

Why is it important?

• Geolocation Fields store latitude and longitude coordinates, allowing for location-based insights and map integrations.
• Useful for tracking customer locations, optimizing sales territories, and calculating distances.

How to Configure Geolocation Fields

1. Navigate to Setup → Go to the object → Click Fields & Relationships.
2. Click New → Select Geolocation.
3. Define:

• Decimal Places (typically 6 for precision).
• Units of Measurement (Miles or Kilometers).

4. Save the field.

Example Scenario

• Optimizing Sales Territory Assignments:
  • A sales manager needs to assign the closest sales rep to a customer.
  • Geolocation fields store customer location coordinates.
  • A custom formula calculates the distance between the customer and sales rep’s office.

4. Global Picklists (Standardizing Dropdown Values Across Objects)

Why is it important?

• Global Picklists allow administrators to define a single picklist value set that can be used across multiple objects.
• This ensures data consistency and reduces duplicate picklists.

Common Use Cases

Object	Field Using Global Picklist
Leads	Industry (IT, Healthcare, Finance)
Accounts	Industry (IT, Healthcare, Finance)
Opportunities	Industry (IT, Healthcare, Finance)

How to Configure a Global Picklist

1. Navigate to Setup → Search for Picklist Value Sets.
2. Click New Global Picklist → Enter Picklist Name.
3. Define picklist values (e.g., IT, Healthcare, Manufacturing).
4. Save and apply it to multiple objects.

Example Scenario

• A company wants Leads, Accounts, and Opportunities to use the same Industry list.
  • Instead of creating separate picklists, they use one Global Picklist for all three objects.

5. Default Values (Pre-Filling Fields for Faster Data Entry)

Why is it important?

• Default Values help users enter data faster and reduce errors by pre-filling fields with common values.
• Can be set manually or dynamically using formulas.

How to Set Default Values

• Default values can be set for:
  • Picklist fields (e.g., Default "Lead Source" to "Website").
  • Checkbox fields (e.g., Default "Active" checkbox to "True").
  • Date fields (e.g., Default "Close Date" to Today() + 30 days).

Example Scenario

• A sales team always expects Leads to originate from the company website.
  • Instead of requiring reps to select "Website" manually, it is set as the default Lead Source.
• A company wants new Opportunities to have a default Close Date of 30 days from today.
  • The formula for default value: TODAY() + 30.

6. Field History Tracking (Auditing Changes to Critical Fields)

Why is it important?

• Field History Tracking logs changes made to fields, helping with audit trails, compliance, and data validation.
• Stores who changed the field, when it changed, and the old/new values.

Key Features

• Can track up to 20 fields per object.
• History is stored for 18 months (or longer with Salesforce Shield).
• Works for standard and custom objects.

How to Enable Field History Tracking

1. Navigate to Setup → Go to the object → Click Fields & Relationships.
2. Click Set History Tracking.
3. Select fields to track (e.g., Opportunity Stage, Close Date, Account Status).
4. Save changes.

Example Scenario

• Tracking Sales Pipeline Changes:
  • Sales managers want to track how Opportunities progress through stages.
  • Field History Tracking logs:
    • Stage changed from "Prospecting" to "Negotiation" on May 10, 2024.
    • Stage changed from "Negotiation" to "Closed Won" on May 15, 2024.
  • This allows managers to analyze sales trends and identify bottlenecks.

Final Summary

Feature	Description	Best Use Cases
Roll-Up Summary Fields	Aggregates child record data in a parent record	Total revenue of Opportunities in an Account
Auto-Number Fields	Auto-generates unique identifiers for records	Order numbers, contract IDs, case numbers
Geolocation Fields	Stores latitude/longitude for location-based analysis	Assigning nearest sales rep to a customer
Global Picklists	Creates a standardized picklist shared across objects	Industry list used in Leads, Accounts, Opportunities
Default Values	Pre-fills fields to reduce manual data entry	Default Lead Source to "Website"
Field History Tracking	Logs changes to critical fields for auditing	Tracking Opportunity Stage changes