Expand my Community achievements bar.

We are excited to introduce our latest innovation to enhance the Adobe Campaign user experience — the Adobe Campaign v8 Web User Interface!
SOLVED

CRM Connector - Salesforce State and Country Picklists

Avatar

Former Community Member

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?

1 Accepted Solution

Avatar

Correct answer by
Former Community Member

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)

View solution in original post

5 Replies

Avatar

Level 10

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

Avatar

Former Community Member

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?

Avatar

Correct answer by
Former Community Member

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)

Avatar

Level 10

Thanks for the update, Did you upgraded?

Avatar

Former Community Member

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

The following has evaluated to null or missing: ==> liqladmin("SELECT id, value FROM metrics WHERE id = 'net_accepted_solutions' and user.id = '${acceptedAnswer.author.id}'").data.items [in template "analytics-container" at line 83, column 41] ---- Tip: It's the step after the last dot that caused this error, not those before it. ---- Tip: If the failing expression is known to be legally refer to something that's sometimes null or missing, either specify a default value like myOptionalVar!myDefault, or use <#if myOptionalVar??>when-present<#else>when-missing. (These only cover the last step of the expression; to cover the whole expression, use parenthesis: (myOptionalVar.foo)!myDefault, (myOptionalVar.foo)?? ---- ---- FTL stack trace ("~" means nesting-related): - Failed at: #assign answerAuthorNetSolutions = li... [in template "analytics-container" at line 83, column 5] ----