Determine whether the Salesforce organization is a Sandbox or a Production

-

To determine if a Salesforce organization is a sandbox or a production environment in Apex. Salesforce's sObject Organization has a field called IsSandbox, which is true for sandboxes and false for Production.

Boolean isSandbox = UserInfo.getIsSandbox();

Organization org = [Select Id, Name, IsSandbox from Organization];

if (org.isSandbox) {
    System.debug('The organization is a sandbox.');
} else {
    System.debug('The organization is a production environment.');

}


You can use this check to conditionally execute logic based on whether the Apex code is running in a sandbox or production environment. This can be useful for implementing different behaviors or configurations specific to each environment.

In Salesforce, the Organization object represents metadata and settings for a Salesforce organization. It provides information about the organization's configuration, such as its name, address, edition, features, limits, and more. The Organization object is represented by the Organization SObject in Apex and API.

Here are some common fields available on the Organization object:

Name: The name of the organization.
Address: The address of the organization.
Phone: The phone number of the organization.
IsSandbox: Indicates whether the organization is a sandbox or production environment.
Edition: The edition of Salesforce (e.g., Enterprise Edition, Developer Edition).
NamespacePrefix: The namespace prefix assigned to managed packages installed in the organization.
DefaultNamespacePrefix: The default namespace prefix for unmanaged code in the organization.
Limits: Information about the organization's limits and usage (e.g., daily API requests, file storage).
Features: Flags indicating enabled features and settings in the organization (e.g., Lightning Experience, Chatter, Communities).

You can query the Organization object in Apex using SOQL to retrieve information about the organization. 

For example:

Organization orgInfo = [SELECT Id, Name, Phone, IsSandbox, Edition, NamespacePrefix FROM Organization LIMIT 1];

System.debug('Organization Name: ' + orgInfo.Name);
System.debug('Phone Number: ' + orgInfo.Phone);
System.debug('Is Sandbox: ' + orgInfo.IsSandbox);
System.debug('Edition: ' + orgInfo.Edition);
System.debug('Namespace Prefix: ' + orgInfo.NamespacePrefix);

It's important to note that not all fields on the Organization object are accessible to all users. Some fields may require special permissions or access settings to be queried or modified. Additionally, certain fields may only be available in specific contexts or environme

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