Salesforce Custom Metadata Types Explained: Benefits, Setup, and Examples

Salesforce's powerful Custom Metadata Types functionality lets developers and administrators make deployable, adjustable configurations and settings. The application cache contains all of the custom metadata, allowing access without requiring repeated database queries.


How to create Custom Metadata Type

1. Search Custom Metadata Type in Setup Quick Find.




2. Click New Custom Metadata Type




3. Fill all required fields and click save





Accessing Custom Metadata Type in Apex


1. Using getAll() - returns map of developer name to metadata type record list. 

Datatype returned by the method - Map<String, Games__mdt>

List<Games__mdt> mcs = Games__mdt.getAll().values();

boolean textField = null;
if (mcs[0].GameType__c == 'PC') {
   textField = true;
}
system.assertEquals(textField, true);


2. Using getInstance(recordId)

Returns a single custom metadata type record sObject for a specified record ID.

Games__mdt mc = Games__mdt.getInstance('m00000000000001');


Using getInstance(developerName) - assume ‘FirstRecord’ is developerName of one record of custom metadata type Games__mdt.

Games__mdt mc = Games__mdt.getInstance('FirstRecord');


Using getInstance(qualifiedApiName)

The namespace prefix and developerName are concatenated to generate the qualifiedApiName, which has the following format: namespacePrefix__developerName.

Games__mdt mc = Games__mdt.getInstance('MyNamespace__FirstRecord');


Limitations with Custom Metadata Type

1. Longer text fields are truncated in custom metadata type records because only the first 255 characters are returned for every field if you use getAll(), getInstance(recordId), getInstance(developerName) method. Use a SOQL query to retrieve all the field data from a custom metadata type record.

Comments

Post a Comment

Popular posts from this blog

How to Add a Dynamic Child List to Parent in Apex Class || Trigger using map

Last Updated: 13-01-2024 Map<parentId, List<child>>  Code without comments Map<id, List<object>> parentIdAndChildRecordsMap = new Map<id, List<object>>(); for(object childRecord : Trigger) { if(parentIdAndChildRecordsMap.containsKey(childRecord.parentId__c)) { parentIdAndChildRecordsMap.get(childRecord.parentId__c).add(childRecord); } else { parentIdAndChildRecordsMap.put( childRecord.parentId__c, new List<object>{childRecord} ); } } Code with comments // Define a map to store parent IDs and their associated child records Map<id, List<object>> parentIdAndChildRecordsMap = new Map<id, List<object>>(); // Iterate through each object in the Trigger context (likely a trigger context variable) for(object childRecord : Trigger) { // Check if the map already contains the parent ID if(parentIdAndChildRecordsMap.containsKey(childRecord.parentId__c)) { // Parent ID found, so add the child record to the existin
Read more

A - Z Guide to Using the Wire Decorator in LWC Salesforce

Image
Certainly! In Salesforce Lightning Web Components, the "wire service" is a feature that brings data to your component. Imagine this data as a never-ending river of information, and each piece of information in this river is like an updated version of the one before it. What's special is that once you receive a piece of data, it's like taking a snapshot in time; you can't change it. Instead, as new data becomes available, it replaces the previous one in the stream. This way, your component always has the latest and most up-to-date information without you having to constantly ask for updates. It's like having a continuous flow of fresh data at your fingertips. Syntax // Wire to a property @wire (methodName, {parameterName: '$value'}) result; // Wire to a function @wire (methodName, {parameterName : value}) callbackFtn(result) { const {data, error} = result; if(data) { // Add logic }   else if(error) {} } When you should use wire to function when
Read more

(Salesforce Apex 2024 Release) getSalesforceBaseUrl method is deprecated

Image
  The getSalesforceBaseUrl() method is no longer available and deprecated in API versions 59.0 and beyond. Alternatively, use getCurrentRequestUrl() to obtain the URL of a complete request on a Salesforce instance, or getOrgDomainUrl() to obtain your organization's URL. A compilation error occurs when the deprecated method in API version 59.0 and later is attempted to be used. System.debug(URL.getOrgDomainUrl());
Read more