Custom Settings vs. Custom Metadata

 

1. What Are Custom Settings?

Custom Settings in Salesforce function like custom objects but are optimized for storing reference or configuration data that can be accessed efficiently in Apex without requiring SOQL queries.

Types of Custom Settings:

  • List Custom Settings: Stores static data accessible to all users in the organization.
  • Hierarchy Custom Settings: Provides user- or profile-specific settings.

Key Features of Custom Settings:

✅ No SOQL required (improves performance)

✅ Supports user-specific or profile-specific configurations

✅ Data is cached, ensuring faster access

🚫 Not deployable via metadata API (requires Data Loader or manual data migration)

When to Use Custom Settings?

  • When you need user-specific or profile-specific configurations
  • To store frequently accessed org-wide settings
  • To improve performance by reducing SOQL queries

2. What Is Custom Metadata?

Custom Metadata is similar to Custom Settings but is stored as metadata rather than data records. This makes it deployable across environments and useful for application configurations.

Key Features of Custom Metadata:

✅ Deployable and packageable like other metadata components

✅ No SOQL required (improves performance)

✅ Data is stored as metadata (does not count against org storage limits)

✅ Can be referenced in validation rules, flows, and formulas

🚫 Does not support hierarchy-based configurations

When to Use Custom Metadata?

  • When you need deployable configurations across multiple orgs
  • To store reference data that should be included in managed packages
  • To replace hardcoded values in Apex, flows, or validation rules

3. Custom Settings vs. Custom Metadata: A Quick Comparison

Article content

4. Choosing the Right One for Your Use Case

  • If you need user-specific settings, go with Custom Settings (Hierarchy Type).
  • If you need deployable configurations, Custom Metadata is the better choice.
  • If you need faster access and don't require deployment, Custom Settings are more efficient.
  • If you want to reference data in validation rules or flows, only Custom Metadata supports this.

Comments

Post a Comment

Popular posts from this blog

My Trigger Scenario's

 Scenario 1 : Prevent Contact Update by Same User Within 1 Hour ? Trigger TimeLastmodified on Contact (Before update) {     Set<Id> contactIds = new Set<Id>();     for (Contact con : Trigger.new) {         contactIds.add(con.Id);     }     for (Contact newCon : Trigger.new) {         if (newCon.LastModifiedById == UserInfo.getUserId()) {             Long minutesSinceLastUpdate = DateTime.now().getTime() - newCon.LastModifiedDate.getTime();             minutesSinceLastUpdate = minutesSinceLastUpdate / (60 * 1000); ...
Read more

Configure types Of Products in CPQ and Revenue Cloud ?

Image
 1) Non-Subscription/One-Time Product : In CPQ :  1)As the name suggests such products are sold as one-time purchases or do not involve recurring billing        or subscription-based pricing.  2) These products are typically purchased once and do not require ongoing payments or renewals.                                          In Revenue Cloud :  2) Subscription Product :   Subscription products are sold as services that last for a specific period (whether that's days, months, or years). Subscription products have recurring payments associated with them. Upon contracting these products become a Subscription  associated with the Contract and renewals can be generated. Example:  Netflix or Amazon Prime. Or buying a cell phone subscription for a month.   In CPQ : Required Fields a...
Read more

Steps for Calculate Derived Pricing in RCA ?

Image
 Step 1) Create Normal Product and Price Book Step 2) Create  One More Product with Pricing to make Is Derived = True Step 3) Now Create Derived Pricing Record Like Below. Step 4) Open " Discovery Procedures " Object and Open existing " Default Discovery Procedure "                         Record.             Update existing " Context Definition " as " SalesTransactionContextMK ". Step 5) Open " Default Discovery Procedure V1 " Procedure.   Update "Asset Discovery" Node and Save and Activate. Step 6) Go Decision Table's and Refresh "Price Book Entries V2" and "Derived Pricing Entries"   Then test add the Product's Quote Line Here is the expected output In "Derived Price" Object While creating the Record, If Pricing Source is "Header"                          Expected Output
Read more