Custom Metadata retrieval error

Update

Salesforce team has applied patches for most of the sandboxes and this issue should now be resolved for the majority of ClickDeploy users. To check if this is fixed for your specific sandboxes, please follow the issue progress here: https://success.salesforce.com/issues_view?Id=a1p3A0000003ek8

Issue

Salesforce Winter 20' recently introduced a bug that results in an error while users attempt to list Custom Metadata in ClickDeploy. This bug also impacts other tooling like Visual Studio Code, Salesforce DX CLI, ...

Until the issue is resolved by Salesforce team, users can work around this by import the metadata selection manually. Please see the workaround section below.

If you setup a CI job to backup metadata to git, please remove the Custom Metadata wildcard for the time being until Salesforce resolves the issue.

ClickDeploy team is currently reaching out to Salesforce team in order to get this resolved. We will post update to this page as soon as more information is available.

Below are references to the issue reported to Salesforce and pending:

https://github.com/forcedotcom/cli/issues/180

https://salesforce.stackexchange.com/questions/278631/custom-metadata-retrieval-fails-in-winter-20

Workaround

While you can't list the custom metadata, you can import the component selection manually via More > Import Component Selections

Screen_Shot_2019-09-19_at_12.25.09_AM.png

Enter the component name using the format: CustomMetadata/CustomMetadataType.CustomMetadataRecordName and click Import.

Screen_Shot_2019-09-19_at_12.27.17_AM.png

To double check that you've entered the component name correctly, perform a retrieval via More > Retrieve Package and check that the component is included in the downloaded package.

If you setup a CI job to backup metadata to git, please remove the Custom Metadata wildcard for the time being until Salesforce resolves the issue.

Did this answer your question?