2

I have created a custom field on a managed package object. I know I can retrieve the field or the object using the metadata API

<types>
  <members>TheManagedPackageCustomObject__c.MyCustomField__c</members>
  <name>CustomField</name>
</types>
<!-OR-->
<types>
  <members>TheManagedPackageCustomObject__c</members>
  <name>CustomObject</name>
</types>

I don't think I will be able to deploy the whole object that's for sure. So I was wondering if it's possible to deploy this custom field I created in a managed package via ant script ?

1

We regularly use Ant-based sf:deploy to pull and push individual non-namespaced fields on standard objects and custom objects including custom objects that are part of a managed package.

We also push in namespaced fields that are part of a managed package where, for example, picklist values need to be changed. But I assume any part of the field that is locked down in the managed package will not be changeable this way.

  • Do you deploy what's in the "Referenced Packages" or you add manually the managed package object in the package.xml? – Cloud Ninja Aug 5 '15 at 9:58
  • @brovasi I've only ever manually added. Object and field name will both have the managed package namespace prefix when the field comes from a managed package. – Keith C Aug 5 '15 at 10:10

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.