It may be that the Salesforce user who is connected through the session does not have access to the custom field. You can verify this by using our FuseIT SFDC Explorer tool. If you connect as the same user and then expand the object fields you should be able to find the custom field and test it in a SOQL query. If it isn't visible in the FuseIT SFDC Explorer then, in Salesforce, check the Field-Level Security setting for the profile of the current user. If the field still isn't visible please check your C# code against the examples in the S4S simple code examples document.
How can I prevent a "Field does not exist" error when setting a custom field?
Comments
0 comments
Please sign in to leave a comment.