In testing dev org (
org A) CustomMetadata was made and added to the package.
This package was retrieved via metadata API (VS Code + ForceCode plugin).
Now I am trying to deploy (migrate) all changes made in
org A to another dev
org B for future development. Custom Metadata has
Metadata Relationship(Field Definition) and metadata API gives an Error
Metadata relationships to Field Definition require a controlling field when I'm trying to deploy it to
Here is how this
FieldDefinition looks as metadata:
<fields> <fullName>Field__c</fullName> <externalId>false</externalId> <fieldManageability>DeveloperControlled</fieldManageability> <label>Field</label> <referenceTo>FieldDefinition</referenceTo> <relationshipLabel>Some_Settings</relationshipLabel> <relationshipName>Some_Settings</relationshipName> <required>false</required> <type>MetadataRelationship</type> <unique>false</unique> </fields>
Same metadata object has
EntityDefinition relationship and there is no problem with that one. There is a couple Custom of Metadata objects with
FieldDefinition and all of them are throwing the same Error when deployed via metadata API to
1. I removed
FieldDefinition field from metadata
Replicate it in
No more Errors
a. Is this a known issue or I made some mistake?
b. How about packaging metadata and it's records? So far it is not part of the managed package, that's why development done in isolated org. Can it brake managed package the same way as basic metadata transfer?