How to use custom metadata types in process builder?
Since custom metadata types is supposed to be the next generation of custom settings, I would LOVE and NEED custom metadata types to be able to be referenced in process builder (as we can in visual workflow currently) and in formulas and validation rules.
Where can I find custom settings in process builder?
Custom settings are available in process builder – but only in formulas – not in the field selection interface.
How to use custom metadata types in validation rules?
Custom metadata types ARE THE BOMB. Let’s make them EVEN BETTER! A small update on the progress. Custom Metadata Type Records in validation rules are GA now. Our current plan is to deliver support for formula fields and default values in Winter ’19 and focus on Process Builder after.
What’s the difference between custom settings and custom metadata?
Custom Metadata Types have WAY more options that Custom Settings, like picklist fields, long text areas (in Spring ’17), page layouts, and validation rules. You can control the visibility of Custom Metadata Types by specifying it as public or protected.
How does custom metadata work in Salesforce.com?
Custom metadata is customizable, deployable, packageable, and upgradeable application metadata. First, you create a custom metadata type, which defines the form of the application metadata. Then you build reusable functionality that determines the behavior based on metadata of that type. You use records to configure your app instead of settings.
How to activate custom settings in process builder?
If you have a custom setting called “ABCCustomSetting”, then you will see it in Data Loader as “ABCCustomSetting (ABCCustomSetting__c)”. Activate the process builder as it is deployed as inactive into Production. Loading…
When to change the version of process builder?
You need to change your version to 33.0 or 34.0 in package.xml. If not you can add a section to your process builder meta data file.
How to create excact for retreive process builder?
Instead of * , provide the excact name of your process and active version number. My-process-10 . Where “My-process” is the name of your process and “-10” is the active version. Once you deploy a processes to the target org, you need to activate it manually.