Randomly Generated Universally Unique Identifier (UUID)

-

Salesforce is a platform that keeps improving by introducing new features, and one such feature is the ability to generate UUIDs in Apex, which was introduced in the Spring 24 Release. With this new functionality, developers can create unique identifiers for records and objects within their Salesforce organization without needing external libraries or custom code. This feature allows developers to save time and effort while ensuring the uniqueness of identifiers

UUID Class and Usage

The UUID Class offers various methods to perform operations like generating a version 4 universally unique identifier (UUID), comparing UUIDs, and converting UUID instances to a string. The generation of UUID is done using a cryptographically strong pseudo-random number generator, and the UUID is represented as 32 hexadecimal values.

Here's a brief overview of each method:

equals(obj): Compares a UUID instance with the specified object.

fromString(str): String representation of a UUID to a UUID instance.

hashCode(): Returns the hashcode corresponding to the UUID instance.

randomUUID(): Randomly generates a version 4 UUID.

toString(): String representation of the UUID instance

How to Generate a UUID?

UUID randomUUID = UUID.randomUUID();

system.debug(randomUUID); // Prints the UUID string that was randomly generated

//8D8AC610-566D-4EF0-9C22-186B2A5ED799

Convert UUID From String

String uuidStr = '8D8AC610-566D-4EF0-9C22-186B2A5ED799';

UUID fromStr = UUID.fromString(uuidStr);

Convert UUID To String

String uuidStr = randomUUID.toString();

Note: UUID (can be outdated or unavailable during release preview) . Please refer to the latest Salesforce Documentation. 

Here are some of the uses of UUIDs in Salesforce:

Integration with External Systems: When integrating Salesforce with other enterprise systems, UUIDs can provide a reliable way to maintain unique identifiers across systems, avoiding duplicate records.

Data Migration: During data migrations, especially when merging records from multiple sources, UUIDs can help maintain unique records and prevent conflicts.

Custom Development: Developers can use UUIDs to reference custom objects, records, or processes uniquely, ensuring that custom development work remains consistent and compatible with Salesforce's standard functionality.

Avoiding Duplicates: In scenarios where new data is frequently imported or created, UUIDs can prevent duplication by guaranteeing that each new record is unique.

Temporary Unique Identifiers: UUIDs can act as temporary identifiers in complex processes where records are pending before they receive a final Salesforce record ID.

Asynchronous Processing: Salesforce often involves asynchronous operations; UUIDs can help track these operations across multiple transactions and systems.

Decoupling Data: UUIDs allow data to be decoupled from Salesforce IDs, which is useful for app exchange applications that must work across multiple Salesforce orgs.

Multi-tenant Environments: Salesforce is a multi-tenant platform, and UUIDs ensure that identifiers are unique within a single org and across all organizations on the platform.

Logging and Auditing: UUIDs can be used to track changes and log for auditing purposes, where each transaction or event needs a unique reference.

Resources -

UUID Class

UUID Version 4 (random)

Comments

Post a Comment

Popular posts from this blog

Introduction to Salesforce Agent Script: Build Predictable AI Agents

-
Image
Please visit here for more details - https://ayaninsights.com/guestblogs/introduction-to-agent-script/ In my latest blog, I introduce Salesforce Agent Script and explain how it helps teams build AI agents that are more predictable, controlled, and aligned with business processes. Large language models are flexible, but relying only on natural-language instructions can sometimes produce inconsistent results. Agent Script addresses this challenge by combining the conversational capabilities of an LLM with structured business logic. The blog explains how developers can use conditions, variables, actions, topics, and transitions to control how an Agentforce agent behaves. Agent Script supports familiar logic such as if/else conditions, value comparisons, sequential actions, and checks for missing data. I also cover its core structure, including system settings, configuration, global variables, languages, connections, and topic blocks. The start_agent topic acts as the entry point for each...
Read more

Anti-Patterns in Salesforce Agentforce: What to Avoid When Building AI Agents

-
Image
Salesforce Agentforce is powerful because it allows teams to build AI agents that can understand user intent, retrieve grounded information, execute actions, and support business workflows across Salesforce. But like any powerful platform, the quality of the implementation matters. A good Agentforce implementation does not start with “How many things can the agent do?" It starts with “What problem should the agent solve reliably?” That is where anti-patterns come in. Anti-patterns are common implementation habits that look useful at first but eventually create confusion, poor user experience, inconsistent answers, or hard-to-maintain agents. Below are some of the most common Agentforce anti-patterns and how to avoid them. 1. Trying to Build One Agent That Does Everything One of the biggest mistakes is designing a single agent to handle every business process, every department, and every possible customer question. At first, this feels efficient. One agent, many use cases. Bu...
Read more

MCP vs. Traditional APIs: Choosing the Right Integration Approach

-
Image
Enterprise integration has traditionally been built around APIs. Applications send structured requests, services process them, and predictable responses are returned. This model has supported everything from payment processing and customer portals to mobile applications and large-scale system integrations. The rise of AI agents introduces a different integration challenge. An AI agent does not always follow a fixed sequence designed in advance. It may need to determine which system to use, discover the operations available to it, gather relevant context, and select the appropriate action based on a user’s request. This is where the Model Context Protocol, or MCP, becomes relevant. MCP and traditional APIs are related, but they solve different problems. APIs expose system capabilities. MCP provides a standardized way for AI applications to discover and use those capabilities as tools and contextual resources. Understanding this distinction is important when designing enterprise AI solut...
Read more