Special Data Types in Apex

Date Support in Apex

The Date data type in Apex is used to store calendar dates without any time information. It represents a specific day, month, and year, making it ideal for managing birthdays, contract start dates, invoice dates, order dates, holidays, and other date-related business information.

Unlike DateTime, the Date data type stores only the date portion and does not include hours, minutes, or seconds.

---

Why Do We Need Date?

Many Salesforce business processes depend on dates rather than exact times. Organizations use Date fields to schedule activities, track contracts, calculate deadlines, monitor warranties, and manage customer information.

---

Simple Date Example

The following example creates a Date object and displays it in the Debug Log.

// Execute Anonymous Window

Date joiningDate = Date.newInstance(2026, 7, 15);

System.debug(joiningDate);

Debug Log Output

USER_DEBUG [3]|DEBUG|2026-07-15

The Date.newInstance() method creates a Date value by specifying the year, month, and day.

---

Real Business Scenario

---

Common Date Operations

---

DateTime Support in Apex

The DateTime data type in Apex is used to store both the date and time in a single variable. Unlike the Date data type, which stores only the calendar date, DateTime includes the year, month, day, hour, minute, and second.

DateTime is commonly used in Salesforce to record when an event occurs, such as record creation, user login, email delivery, case updates, scheduled jobs, and API transactions.

---

Why Do We Need DateTime?

Many Salesforce business processes require precise timestamps rather than just dates. DateTime helps developers track exactly when an activity starts, finishes, or is modified.

---

Simple DateTime Example

The following example creates a DateTime value and prints it in the Debug Log.

// Execute Anonymous Window

DateTime meetingTime =
DateTime.newInstance(
2026,7,15,10,30,0
);

System.debug(meetingTime);

Debug Log Output

USER_DEBUG [6]|DEBUG|2026-07-15 10:30:00

The DateTime.newInstance() method creates a DateTime object by specifying the year, month, day, hour, minute, and second.

---

Real Business Scenario

---

Common DateTime Operations

---

Time Support in Apex

The Time data type in Apex is used to store only the time of day without any associated date information. It records the hour, minute, second, and millisecond, making it useful for applications that need to track specific times rather than complete dates.

Unlike the Date data type, which stores only the calendar date, or the DateTime data type, which stores both date and time, the Time data type focuses solely on the time component.

---

Why Do We Need Time?

Many business processes depend only on time rather than a complete date. For example, office working hours, meeting schedules, store opening times, lunch breaks, or customer support timings all require only the time portion.

---

Simple Time Example

The following example creates a Time value and displays it in the Debug Log.

// Execute Anonymous Window

Time meetingTime =
Time.newInstance(
10,
30,
0,
0
);

System.debug(meetingTime);

Debug Log Output

USER_DEBUG [6]|DEBUG|10:30:00.000Z

The Time.newInstance() method creates a Time value by specifying the hour, minute, second, and millisecond.

---

Real Business Scenario

---

Common Time Methods

---

Id Support in Apex

The Id data type in Apex is a special Salesforce data type used to uniquely identify every record stored in the Salesforce platform. Every Account, Contact, Opportunity, Lead, Case, Custom Object, and many other records automatically receive a unique Record ID when they are created.

Unlike a normal String, the Id data type is specifically designed to represent Salesforce Record IDs. It provides built-in validation and helps developers safely reference Salesforce records throughout Apex applications.

---

Why Do We Need the Id Data Type?

Business applications frequently need to retrieve, update, delete, or relate specific Salesforce records. Instead of searching by record name, Salesforce uses the unique Record ID to identify the exact record.

Using Record IDs improves performance, ensures data accuracy, and eliminates ambiguity when multiple records have similar names.

---

Simple Id Example

The following example stores a Salesforce Account Record ID in an Apex variable.

// Execute Anonymous Window

Id accountId =
'0015g00000ABCDeAAH';

System.debug(accountId);

Debug Log Output

USER_DEBUG [4]|DEBUG|0015g00000ABCDeAAH

The Id variable stores a valid Salesforce Record ID that can later be used to retrieve or update the corresponding Account.

---

Real Business Scenario

---

Using Id in SOQL

Record IDs are commonly used to retrieve specific Salesforce records using SOQL.

Id accountId =
'0015g00000ABCDeAAH';

Account acc = [

    SELECT Id, Name

    FROM Account

    WHERE Id = :accountId

];

System.debug(acc.Name);

Debug Log Output

USER_DEBUG [10]|DEBUG|LearnFrenzy Technologies

---

Id vs String

---

Common Uses of Id in Salesforce

---

Blob Support in Apex

The Blob data type in Apex is used to store binary data instead of regular text or numbers. A Blob can represent files, images, PDF documents, Excel spreadsheets, ZIP files, email attachments, and other binary content that cannot be stored as plain text.

Salesforce developers commonly use Blob when working with file uploads, document generation, email attachments, REST API integrations, and Base64 encoded data.

---

Why Do We Need Blob?

Business applications often need to store and exchange files rather than simple text values. Since files contain binary data, Apex uses the Blob data type to handle them efficiently.

---

Simple Blob Example

The following example converts a text value into a Blob object.

// Execute Anonymous Window

Blob fileData =
Blob.valueOf('Welcome to LearnFrenzy');

System.debug(fileData);

Debug Log Output

USER_DEBUG [4]|DEBUG|Blob[24]

The Blob.valueOf() method converts a String into binary data that can be stored or transmitted by Apex.

---

Real Business Scenario

---

Common Blob Operations

---

Where is Blob Used in Salesforce?

---

Enum Support in Apex

The Enum (Enumeration) data type in Apex is used to define a fixed set of constant values. Instead of allowing any value to be assigned to a variable, an Enum restricts the variable to predefined options, making your code safer, easier to read, and less prone to errors.

Enums are commonly used to represent business values such as order status, payment status, approval stages, priorities, and user roles where only a limited number of valid options exist.

---

Why Do We Need Enum?

In many business applications, certain fields can have only a limited number of valid values. Instead of using plain text values that can be typed incorrectly, developers use Enums to enforce consistency throughout the application.

---

Simple Enum Example

The following example creates an Enum that represents different order statuses.

// Execute Anonymous Window

public enum OrderStatus{

    New,
    Processing,
    Delivered

}

OrderStatus status =
OrderStatus.Processing;

System.debug(status);

Debug Log Output

USER_DEBUG [10]|DEBUG|Processing

The variable status can store only the values defined in the OrderStatus Enum.

---

Real Business Scenario

---

Advantages of Using Enum

---

Enum vs String