CRM Connector - Salesforce State and Country Picklists | Community
Skip to main content
A
Anonymous
June 12, 2017
Solved

CRM Connector - Salesforce State and Country Picklists

  • June 12, 2017
  • 5 replies
  • 1595 views

We're running the CRM connector in Campaign 6.1, connecting to a Salesforce Org which has State and Country Picklists enabled.  We're not able to see the fields MailingStateCode and MailingCountryCode on the Contact record.  We know they're available in the API, but cannot see them in Campaign - where should we be looking?

    This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
    Best answer by

    We've isolated the issue: Adobe Campaign is using Salesforce API v.21, and State & Country Picklists were only released in v.27 - we need to upgrade (note the current API is v.40)

    5 replies

    Amit_Kumar
    Amit_Kumar
    Level 10
    June 12, 2017

    Hi Alastaird514,

    MailingStateCode or MailingCountryCode is actually a part of address field which is a compound field , A compound field is comprised of several different fields. When referencing any of compound fields there are some limitations i.e

    • Compound fields are read-only. To update field values, modify the individual field components(you have to asks salesforce developer to grant your users the edit access from sales-force).

    Read more about the limitations here: Salesforce Developers

    Best regards,
    Amit

    A
    Anonymous
    June 13, 2017

    Hi Amit,

    to expand on the issue, we're able to access all the other fields within the Address, such as MailingStreet, MailingCity and MailingState, however, the MailingStateCode isn't visible in the Campaign interface.  It is visible through other tools which are using the Salesforce API.

    Thoughts?

    A
    Anonymous
    Accepted solution
    June 14, 2017

    We've isolated the issue: Adobe Campaign is using Salesforce API v.21, and State & Country Picklists were only released in v.27 - we need to upgrade (note the current API is v.40)

    Amit_Kumar
    Amit_Kumar
    Level 10
    June 15, 2017

    Thanks for the update, Did you upgraded?

    A
    Anonymous
    June 18, 2017

    Amit Kumar​ we have to test before upgrading, but this is in progress.

      Terms & ConditionsAccessibility statement

      Loading footer...