function readOnly(count){ }
Sign Up ›
Starting November 20, the site will be set to read-only. On December 4, 2023,
forum discussions will move to the Trailblazer Community.
Learn More

Browse by Topic
ShowAll Questionssorted byDate Posted
+ Start a Discussion
twongopenairtwongopenair 

describeSObject, custom object and partner API issue

Hi, 

 

We integrate with our customers' Salesforce instances using the Partner WSDL and we have a partner ID. We have run into an issue with using a describeSObject call on a custom object for one of our customers. describeSObject works fine on standard objects like Opportunity, Account, etc.. but there is a custom object that we need access to but describeSObject is returning that it is an invalid type. We are using the API name specified for the custom object. So if the custom object API name is OA_Projects__c, we're seeing 

 

sObject type 'OA_Projects__c' is not supported. If you are attempting to use a custom object, be sure to append the '__c' after the entity name. Please reference your WSDL or the describe call for the appropriate names.

 

We have integrated with custom objects for other customers using the Partner WSDL and have not had any issues with describeSObject.  

 

Does anyone have any ideas what this might be? 

 

Thanks in advance, 

 

Tony

 

 

SuperfellSuperfell

The user running the call to describeSObject does not have access to the object, could be because of their profile setup, package licensing or package access controls (it depends exactly how the custom object got there, and what context exactly your code is running in).
twongopenairtwongopenair

Hi Simon,

 

We've tested with a user with an administrator profile but we still cannot see the custom object with describeSObject. 

 

Do you mean that it is possible for a user with an admin profile to not have access to custom objects in the SF API from an installed package? 

 

Thanks for your help! I really appreciate it. 

 

Tony

 

 
SuperfellSuperfell

If the objects are from a licensed managed package, then the use (even if an admin) will need a license for the package.
twongopenairtwongopenair

Thanks, Simon. This is helpful. 

 

It turns out that the custom object is not a part of a licensed package. Strangely we are not able to access the one we need even with an admin user with the API. But we are able to access other custom objects in that same account. Very strange but we're still investigating. Hopefully will have an answer to this soon but if you do have some other ideas, I'd much appreciate it. 

 

Best, 

Tony
SuperfellSuperfell

check the profile settings, and check that its marked as deployed and not in development.