I need to migrate Custom Metadata type using a package.xml
.
Can someone please let me know what should I put to get the metadata along with data successfully get migrated? Suppose Custom Metadata type name is Call_Duration_Zip_abv__mdt
.
Salesforce Stack Exchange is a question and answer site for Salesforce administrators, implementation experts, developers and anybody in-between. It only takes a minute to sign up.
Sign up to join this communityI need to migrate Custom Metadata type using a package.xml
.
Can someone please let me know what should I put to get the metadata along with data successfully get migrated? Suppose Custom Metadata type name is Call_Duration_Zip_abv__mdt
.
From the Document
A custom metadata type is defined as a custom object and is stored in the objects folder. Custom metadata types have a suffix of
__mdt
(instead of__c
for custom objects). Custom metadata type field names have a suffix of__c
, like other custom fields. Custom metadata type field names must be dot-qualified with the name of the custom metadata type to which they belong.
This excerpt from a package.xml
file shows the use of dot notation and the __mdt suffix. If you’re using a namespace, for example picklist1234
, the full name of ReusablePicklistOption__mdt
would be picklist1234
__ReusablePicklistOption__mdt
.
<?xml version="1.0" encoding="UTF-8"?>
<Package xmlns="http://soap.sforce.com/2006/04/metadata">
...
<types>
<members>PicklistTest__c.PicklistTestField__c</members>
<members>ReusablePicklistOption__mdt.Picklist__c</members>
<members>ReusablePicklistOption__mdt.SortOrder__c</members>
<members>PicklistUsage__mdt.Field__c</members>
<members>PicklistUsage__mdt.Picklist__c</members>
<members>PicklistUsage__mdt.SObjectType__c</members>
<members>ReusablePicklist__mdt.AlphaSort__c</members>
<name>CustomField</name>
</types>
...
<types>
<members>PicklistTest__c</members>
<members>ReusablePicklistOption__mdt</members>
<members>PicklistUsage__mdt</members>
<members>ReusablePicklist__mdt</members>
<name>CustomObject</name>
</types>
...
<version>39.0</version>
</Package>
Go through this if you need more information. Let us know if this works for you or not.