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.
Articles in this section
- Identifying issues that are hard to find!
- Determining your S4S Version
- How can I write C# code to access Salesforce?
- How can I improve the response times when accessing Salesforce?
- If S4S is unlicensed, when will the connector functionality expire?
- Is my licensing impacted by a Sitecore upgrade?
- “Null Reference Exception” thrown from Profile Provider
- I'm receiving a "Response is not well-formed XML" error!
- Why am I getting a "Salesforce Password Expired" exception?
- Why can't I log in to the Sitecore website with my Salesforce credentials?