Out org has some managed packages installed.

When we try to generate the enterprise wsdl, only some of them appear on the list of packages (so we can set the version). Custom fields on the packages that aren't on the list don't show on the wsdl.

p.s.: We already tryed making SOAP calls to our org and we were able to fill those fields. Also, FLS is set as visible to all profiles.

Is there anything we're missing?

  • Is there anything you can use to distinguish the ones that aren't appearing from the ones that are? Are they licensed for the user generating the Enterprise WSDL? Were the problem packages installed with API restrictions? Interestingly, my dev org has 21 packages installed. Only 9 appear for version selection when generating the Enterprise WSDL. – Daniel Ballinger Nov 17 '15 at 19:08
  • Looking closer, only the managed packages are appearing in the list. The rest are unmanaged, and hence don't have a namespace. – Daniel Ballinger Nov 17 '15 at 19:11
  • No. The ones that aren't appearing are also Managed. They have no restrictions and all the settings are equal to the one who do appear. (at least the settings I can see). – Fernando Gavinho Nov 18 '15 at 12:25
  • I also have access to the dev org of those packages and couldn't find any differences. – Fernando Gavinho Nov 18 '15 at 12:26
  • When you say you can make SOAP calls to update the missing fields, how are you doing that. Is that via the Partner API? – Daniel Ballinger Nov 19 '15 at 0:48

Your Answer

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

Browse other questions tagged or ask your own question.