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
- Individualization with Sitecore and Salesforce
- How can I write C# code to access Salesforce?
- How can I improve the response times when accessing Salesforce?
- I'm receiving a "Response is not well-formed XML" error!
- Why am I getting a "Salesforce Password Expired" exception?
- Why am I getting a “The Salesforce Provider is not Enabled” error?
- Why am I getting an InvalidOperationException after installing the S4S connector into Sitecore?
- Why does Salesforce return an INVALID_LOGIN exception?
- What are some useful resources for installing S4S?
- What is the S4S.Config file used for?