force:cmdt:record:insert causes deployments to fail if there is a Metadata Relationship data type

[louisskelton]

Summary

Using force:cmdt:record:insert generates XML with Metadata Relationship data types tagged as xsi:type="xsd:undefined". When deploying the resulting Custom Metadata Records the following error is received:

ERROR running force:source:deploy: Deploy failed

Replacing xsi:type="xsd:undefined" with xsi:type="xsd:string" fixes the issue.

Steps To Reproduce:

1. Create two metadata type objects linked with a Metadata Relationship
2. Create CSVs for both metadata types
3. Run force:cmdt:record:insert to create XML Custom Metadata Records for each Type
4. Deploy Custom Metadata Records

Expected result

Deploy should be successful

Actual result

Deploy fails with ERROR running force:source:deploy: Deploy failed

Additional information

Replacing xsi:type="xsd:undefined" with xsi:type="xsd:string" in the XML generated with force:cmdt:record:insert fixes the issue.

Version: sfdx-cli/7.68.6-d37008df83 darwin-x64 node-v12.18.3

[clairebianchi]

@louisskelton I will share your issue with the cmdt team. Thank you

[SalesforceRocks]

@clairebianchi this issue also occurs for force:cmdt:record:create. Can you have someone create a bug report and pass it to the right team? I guess it's the same issue. The solution is the same.

[Yeackley]

I'm currently hitting this issue as well trying to create records from CSV file. Any updates?

[shetzel]

I've asked for an update from the cmdt team. I'll pass along any details they give me if no one responds here directly.

[uip-robot-zz]

This issue has been linked to a new work item: W-8969685

[github-actions]

We have determined that the issue you reported exists in code owned by another team that uses only the official support channels. To ensure that your issue is addressed, open an official Salesforce customer support ticket with a link to this issue. We encourage anyone experiencing this issue to do the same to increase the priority. We will keep this issue open for the community to collaborate on.

[sudhakar6]

any update on this , or is there any workaround available except the Replacing xsi:type="xsd:undefined" with xsi:type="xsd:string" in the XML

[colinregan1]

Any update?

[gongambino]

Hi Github community - I'm the Salesforce PM for the Custom Schema area which owns CMDTs. Unfortunately due to other competing priorities, we don’t currently have it on our roadmap to resolve this issue. Hopefully, the identified workaround gets most customers out of this situation.

In order for us to get this prioritized we would need to see overwhelming feedback on the Trailblazer Community / IdeaExchange and/or large volume of high-severity support cases.