function readOnly(count){ }
Starting November 20, the site will be set to read-only. On December 4, 2023,
forum discussions will move to the Trailblazer Community.
+ Start a Discussion
tSoudritSoudri 

Accessing custom object with s-control in Professional Edition

Hello all,
I was wondering if someone might be able to help me with this issue I'm having.We have developed a custom app with an s-control that accesses the API to add/read data from several Salesforce objects (Opportunities, Tasks...). The app also includes a custom object (named h5ro__Recurring_Opportunity__c) that is installed with the rest of the package. The app was developed as a Salesforce Partner, so we have a token in the WSDL to allow Professional Edition users to access the API.
When testing with Professional Edition, however, we are unable to query our custom object. Queries (select, insert) on other objects work fine, but when we try to preform a simple select query on our object we receive the following error:
faultcode:'sf:INVALID_FIELD',
faultstring:'INVALID_FIELD:
h5ro__Duration__c,h5ro__End_Time__c ,h5ro__Opportunity_Name__c, h5ro__Probability__c
^ ERROR at Row:1:Column:154
No such column 'h5ro__Opportunity_Name__c' on entity 'h5ro__Recurring_Opportunity__c'.
If you are attempting to use a custom field, be sure to append the '__c' after the custom field name. Please reference your WSDL or the describe call for the appropriate names.'
 detail:{fault:{exceptionCode:'INVALID_FIELD', exceptionMessage:' h5ro__Duration__c,h5ro__End_Time__c ,h5ro__Opportunity_Name__c, h5ro__Probability__c ^ ERROR at Row:1:Column:154
No such column 'h5ro__Opportunity_Name__c' on entity 'h5ro__Recurring_Opportunity__c'.
If you are attempting to use a custom field, be sure to append the '__c' after the custom field name. Please reference your WSDL or the describe call for the appropriate names.',
row:'1', column:'154', }, }, }
It's as if certain custom fields are not defined, or the app can't access them.
The only thing I can think of that could cause a problem like this is if we didn't define something properly in the packaging of the custom object.
Any ideas on how to solve this problem would be greatly appreciated.