Skip to main content

Platform Developer I Certification Maintenance (Winter '22)

 As we know Salesforce always add new features and based on that there are releases. This maintenance is all about Custom Metadata Type in apex. You no longer need to write a Salesforce Object Query Language (SOQL) to access custom metadata records in Apex.

How: Use the new Apex getAll(), getInstance(recordId), getInstance(qualifiedApiName), or getInstance(developerName) methods to retrieve custom metadata type records. 



Returns a map containing custom metadata records for the specific custom metadata type. The map's keys are the IDs (as String) of the records and the map's values are the record sObjects.


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


Returns a single custom metadata type record sObject for a specified developerName field of the custom metadata type object.


Returns a single custom metadata type record sObject for a qualified API name.


MetadataTypeAPIName__mdt variable = MetadataTypeAPIName__mdt.getAll();

For Exam Replace Code after creation of MetaData Type and Record:

Create a Custom Metadata Type:

Label: Country Code

Plural Label: Country Codes

Add a Custom Field:

Data Type: Text

Field Label: Country Code

Length: 3

Enter a Country Code by clicking "Manage Country Codes":

Label: Canada

Country Code: CAN

Create a Class CountryCodeHelper and Paste the below code:

public class CountryCodeHelper {

  public static String getCountryCode(String country) {

      Country_Code__mdt countryCode = Country_Code__mdt.getInstance(country);

    return countryCode.Country_Code__c;




Popular posts from this blog

Platform Developer I Certification Maintenance (Winter '23)

 Maintain Your Platform Developer I Certification for Winter ’23 1. Field update actions have changed in API Version 54.0. Which record-triggered flows do field update actions now execute? Answer: Before-Save after After-Save 2. Which Apex class is used to determine the hostnames for the domains that Salesforce hosts for your org? Answer: System.DomainCreator 3. Which modules can be used for notifications in a Lightning web component instead of native APIs? Answer: LightningAlert, LightningConfirm, and LightningPrompt 4. What determines an org’s “shape” in Salesforce? Answer: Features, settings, edition, limits, and licenses 5. Which lightning-modal-* component is required to create a modal? Answer: Body 6. How do you call an invocable action from Apex code? Answer: Reference Invocable.Action Get Hands-On With Apex Assertions 1. Create Two Apex class: Copy and Paste below codes (A.) TestFactory @isTest public class TestFactory {    public static Account getAccount(String accountName, B

Custom Table In LWC

I'm assuming you've Basic understanding of Lightning Web Component, I'll be explaining you the syntax that will be generic. HTML: < template > <!-- Header Part -->      < lightning-card   title = "Custom Data table in Lightning Web Components" >          < div   class = "slds-grid slds-gutters" >              < div   class = "slds-col" >                  < span ></ span >              </ div >              < div   class = "slds-col" >                  < span > <!--A Button For extra feature-->                      < lightning-button   label = "Show Selected Contacts"   onclick = {showContacts}   style = "margin-left: 40%"   variant = "brand" > </ lightning-button >                  </ span >              </ div >          </ div >< br />

LWC js-meta.xml Configuration File Tags

Each Lightning web component folder must include a configuration file named <componentName>.js-meta.xml. The configuration file defines the metadata values for the component, including the design configuration for the Lightning App Builder and Community Builder. Some Standard Key metadata values: apiVersion : A double value that binds the component to a Salesforce API version. isExposed : If isExposed is false, the component is not exposed to Lightning App Builder or Community Builder. To allow the component to be used in Lightning App Builder or Community Builder, set isExposed to true and define at least one <target>, which is a type of Lightning page. Some Standard Optional metadata values: description : A short description of the component, usually a single sentence. masterLabel : The title of the component. Appears in list views, like the list of Lightning Components in Setup, and in the Lightning App Builder and in Community Builder. targets : Specifies wher