You need to sign in to do that
Don't have an account?

WSDL ignores all fields not included in page layout
Since the introduction of the Winter '08 release, we have come across this peculiar situation. It seems that the WSDL (we are using the Enterprise WSDL) only includes fields that are displayed in the object's page layout. When fields that we want to completely remove from the page layout for all users (utility fields or other unimportant-to-the-user fields), but still want access to via the API so we may continue to associate the info with the object are not present in the page layout, we lose all ability to access them.
Here is the error I receive:
INVALID_FIELD: Field name provided, Custom_Field__c is not readable for Object__c
Is this a Winter '08 update? If so, why would this limitation be imposed now? Is this documented anywhere in the release notes? Is there any way to get around this so we may access all fields, not just the ones included in the page layout?
Thanks in advance!
Here is the error I receive:
INVALID_FIELD: Field name provided, Custom_Field__c is not readable for Object__c
Is this a Winter '08 update? If so, why would this limitation be imposed now? Is this documented anywhere in the release notes? Is there any way to get around this so we may access all fields, not just the ones included in the page layout?
Thanks in advance!
Message Edited by jpizzala on 11-09-2007 04:09 PM
Thanks for the clarification.