
Here I am using ‘Org Browser’ extension to fetch the metadata information from Salesforce org. Click on icon Retrieve Source From Org on ‘Custom Object’. Now fetch the Custom Metadata Type definition from your Salesforce org to your local machine. Open your VSCODE IDE and create a project (If you already have project created on your vscode skip this step) Setup> Quick find> search ‘custom metadata’ and click on “New Custom Metadata Type”.Ĭreate the Custom Metadata Type and fields. If you already have (custom metadata type) skip creation/definition steps.

This provides the powerful command line interface (CLI) that makes things super easy for the developers to work with Salesforce Orgs for developing, continuous integration, and delivery.Ĭreate a CustomMetadataType in your Salesforce org. Salesforce Developer Experience (DX) is a new way to manage and develop the salesforce application.

Let’s see how we can do mass CustomMetadataType records insert using Salesforce CLI. This is a recommended approach for this task. The SalesforceDX CLI? Yes, we can now import the CustomMetadataType records using cmdt command. We know “Data Loader” is to load the data but here CustomMetadata is not real data.Īnt Migration Tool ? You can choose this tool for this job but this is not that I recommend. Salesforce Data Loader ? As of now “Data Loader” does not support CustomMetaDataType (We don’t know yet when this will be available in future). Let’s check what options we have to do this: In those XML files, we provide information about our server ( like credentials, login URL, and some other attributes as well, file is build.properties ), information about the operation that we want to perform (these are called targets, like retrieve or deploy, file isīuild.xml), then information about the components that you want to retrieve or deploy( package.xml).Are you facing challenges inserting mass CustomMetadataType records in Salesforce org? this blog post will help you. This tool works with the help of some XML files.


Thus you can make changes in those XML files locally and againĭeploy the changes to any server instance, any target org that you
