Salesforce Configuration from Custom Metadata Types



Salesforce Configuration from Custom Metadata Types

Custom Metadata Types are a very powerful capability in the Salesforce platform it can in process builder, formulas, and validation rules. I wanted to give some background and examples to help admins understand how it could be used in their orgs. The main advantage to using the custom metadata types is you can add both definition and records in the package or changeset.

Advantages to Custom Metadata:

1. You can control the visibility of Custom Metadata Types by specifying it as public or protected.
2. We can create fields like Picklist fields, long text areas also able to do with page layouts, and validation rules.
3. Asynchronous (without using remote site settings) insert/update in Apex via Metadata.MetadataOperations.enqueueDeployment()
4. Custom Metadata have a option for access for edit the records with “Configure Application” but you require “Author Apex” to edit the configuration.
5. Custom metadata is also visible for test class so no need to insert records for testing.

Some use case are following :

1. Process Builder with Formula

We have a requirement to update one field dynamically and admin can easily update accordingly without renovate the Process builder.

Step are following :
1. Create Custom Metadata for default value with the help below snapshot :

2. Create Records in Custom Metadata with the help below snapshot :
3. Create Process Builder for Update Record via custom metadata records with the help below snapshot :
4. Output :

2. Validation Rules

We have a requirement to update Discount field dynamically and admin can easily update accordingly without renovate the validation rule.

Step are following :
1. Create Custom Metadata for default value with the help below snapshot :

2. Create Records in Custom Metadata with the help below snapshot :
3. Create Validation Rule for Check Record before insert or update via custom metadata records with the help below snapshot :
4. Output :

Note : But there is a one limitation that we can't create dynamic error message for validation rule.


For more details : Custom Metadata Types


Happy Sharing...

Everyone has their own favorites, so please feel free to share yours in the comments below!

Comments

Post a Comment

Popular posts from this blog

Salesforce LWC : Compact Layout on Hover

Image
Salesforce LWC : Compact Layout showing on Hover Sometime we have requirement to show Account name link on standard views, a popup with the Compact Layout shows the details of that record. LWC Parent Component : Template (HTML Code) LWC : JS (Process Code) import { LightningElement,api } from 'lwc'; export default class AccountComponent extends LightningElement { @api recordId; @track objRecordId; handleMouseover(event) { console.log(this.recordId); this.objRecordId = null const toolTipDiv = this.template.querySelector('div.ModelTooltip'); toolTipDiv.style.opacity = 1; toolTipDiv.style.display = "block"; // eslint-disable-next-line window.clearTimeout(this.delayTimeout); // esli
Read more

Salesforce LWC With Third Party JS : D3

Image
Salesforce Lightning Web Component With Third Party JS : D3 Third-Party JavaScript Libraries Using JavaScript to manipulate the DOM isn’t recommended because the Lightning Web Components engine does it more efficiently. However, there are some third-party JavaScript libraries that take over the DOM. Manipulate the DOM with JavaScript Using JavaScript to manipulate the DOM isn’t recommended because the Lightning Web Components engine does it more efficiently. However, there are some third-party JavaScript libraries that take over the DOM. If a call to appendChild() manipulates the DOM, styling isn’t applied to the appended element. When using these libraries in a Lightning web component, add lwc:dom="manual" to any HTML element that you want to manipulate with JavaScript. When the engine sees the directive, it preserves encapsulation. Add the lwc:dom="manual" directive to an empty native HTML element. The owner of the component calls appendChild()
Read more

Communications between Lightning Components : Salesforce

Image
Communications between Lightning Components : Salesforce Salesforce have new lightning framework to create components in lightning framework which is fast with high performance to pass data from one lightning component to another. For this salesforce provides various ways to communicate between lightning components. Below are the list of ways you can communicate :- 1. Using attribute in lightning components. 2. Using aura:method to pass data. 3. Using component type event. 4. Using application type event. 5. Using System Events. 1. Using Attributes :- we have a parent component in which we have a Boolean attribute which i want to pass to child component for further processing. c:parentComponent.cmp <aura:component> <aura:attribute name=”showTable” default=”false” type=”boolean”/> <lightning:button label=”show table” onclick=”{! c.showBoolean }” /> <c:childComponent tableDisplay=”{!v.showTable}”/> </aura:component> c:parentCompone
Read more