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. 

Descriptions:

getAll()

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.

getInstance(recordId)

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

getInstance(developerName)

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

getInstance(qualifiedApiName)

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

Syntax: 

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;

  }

}

Comments

Popular posts from this blog

Maintain Your Platform Developer I Certification for Winter ’25

  Make Invocable Actions Easier to Configure with New InvocableVariable Modifiers Simplify the configuration of invocable actions using new modifiers from Salesforce. Both the defaultValue and placeholderText modifiers will appear in Flow Builder for the Action elements that correspond to an invocable method. Here’s how to use them. defaultValue Modifier : Set a default value for an input parameter. When the action is used, the input parameter will have a predefined value unless changed by the user. placeholderText Modifier : Set custom placeholder text for an input parameter. Text can provide examples or additional guidance to help users understand what to enter in the input field. Accessing these modifiers in Flow Builder makes it easier to configure and use the actions within your flows. This change applies to Lightning Experience and Salesforce Classic in Performance, Unlimited, Developer, Enterprise, and Database.com editions.

Maintain Your Administrator Certification for Spring ’25

  Manage Included Permission Sets in Permission Set Groups via Summaries Update user access more efficiently by specifying which permission set groups include a permission set directly from the permission set’s summary. Previously, to manage included permission sets, you were required to navigate to each permission set group’s page. From Setup, in the Quick Find box, enter  Permission Sets , and select Permission Sets. Select a permission set, and then click  View Summary . In the Related Permission Set Groups tab, click  Add  or  Remove . This change applies to Lightning Experience and Salesforce Classic (not available in all orgs) in Contact Manager, Group, Essentials, Professional, Enterprise, Performance, Unlimited, Developer, and Database.com editions. Sort List Views by Multiple Columns To see your data in a more intuitive way and make your list views more actionable, you can now sort list views on object home pages by up to five columns. Select the c...

Salesforce Architect Certification Maintenance (Winter '25)

  Update Records Using ISO State and Country Codes Standardize and simplify updating address records with two new fields that store the ISO code for country or territory and state or province. Improve data quality and accuracy using this new support for ISO codes, and reduce the risk of errors and inconsistencies that can occur when using names. Previously, the Address component stored only the name associated with the user’s selection. With this new support for ISO codes, you can update the country or territory and state or province fields on records with ISO codes instead of names. This feature can be used for new or existing screen flows. Here are the steps to create a new flow. In Setup, on the State and Country/Territory Picklists page, ensure that Enable Picklists for Address Fields is enabled. In Flow Builder, create a screen flow. Add a Screen element to the flow. Include an Address component in the Screen element. Optionally, specify a default value in the Country Code and...

Translate