Issues with Custom Object retrieval/deployment (Managed Object) - specific fields only

[Eric Alexander]

When adding fields to a managed object, I have the subscription set to only the fields I created.

This results in a .object file that is missing required information to be able to deploy, save etc.

The following information should be retrieved in the XML for a custom object:

    <label>xxx</label>
    <pluralLabel>xxx</pluralLabel>
    <nameField>
        <label>xxx</label>
        <type>xxx</type>
        <displayFormat>xxx</displayFormat>
    </nameField>
    <deploymentStatus>Deployed</deploymentStatus>
    <sharingModel>ReadWrite</sharingModel>

For example, say I have a Managed Custom Object from a third party - ManagedA I add a field to it say FIELDA I update my subscription to NOT include the Object (Cannot ave or deploy it a cannot modify the metadata listed int he file) I include the FIELDA only

This yields a .object file as follows:

<?xml version="1.0" encoding="UTF-8"?>
<CustomObject xmlns="http://soap.sforce.com/2006/04/metadata">
<fields>
        <fullName>Poynt_Response__c</fullName>
        <deleteConstraint>Restrict</deleteConstraint>
        <externalId>false</externalId>
        <label>Poynt Response</label>
        <referenceTo>Poynt_Response__c</referenceTo>
        <relationshipLabel>Transactions</relationshipLabel>
        <relationshipName>Transactions</relationshipName>
        <required>false</required>
        <trackHistory>false</trackHistory>
        <trackTrending>false</trackTrending>
        <type>Lookup</type>
    </fields>
</CustomObject>

This XML cannot be deployed to another org or modified and saved to the current org without the previously specified missing information.

[Scott Wells]

Issue tracker grooming. If this is still an issue, please feel free to reopen, ideally with a concrete reproduction scenario.