Skip to main content

Configure State or Country Code Mapping In Salesforce

Follow

Comments

8 comments

  • Megan Callaghan

    I'm still getting the following error after following these instructions, "Error | Billing Country Code: bad value for restricted picklist field: United States |"

    Comment actions Permalink
  • METER Group

    Does this apply for the IO as well as for V2?

    Comment actions Permalink
  • METER Group

    Yes, as a matter of fact, it turns out that it does. It also applies to Canadian Provinces. Can you tell me if it applies to still other countries?

    Comment actions Permalink
  • Docs Support

    Hi Meter Group, 

    The above changes are required for both SFNSIO and v2. Salesforce packages 239 countries and includes the states and provinces of the United States, Canada, Australia, Brazil, China, India, Ireland, Italy, and Mexico. (i.e. 9 countries out of 239 have state picklist). For countries other than 9 listed above, the state list has to be configured. You would have to setup the data (Name, Code and Integration Value) for the new entries.

    The integration application maps the Salesforce State and Country field with NetSuite State and Country codes. You would observe this error when the codes in NetSuite do not match with Salesforce configured state or territory lists. The codes in NetSuite can be 10+ characters, while SF allows only 10 characters, so there are high chances of error for the newly configured states lists. 

    Please let us know if this answers your query. 

    Comment actions Permalink
  • METER Group

    The problem I fear is that now everything else that integrates with SF will be broken instead. Salesloft, Pardot, and an ever-growing list.  Is there no other way? Can we map it with a Lookup, or change the values in Netsuite?

    Comment actions Permalink
  • David Gollom

    Does this apply to the IO version of SF to NS IA as well???  Agree with above comment as well.  Might need to do a lookup or static mapping. 

    Comment actions Permalink
  • Courtney Jordan

    Hi METER Group and David Gollom,

    I'm checking on your questions with our SFNS PM team.

    Comment actions Permalink
  • Docs Support

    Hi Meter Group and David Gollam, 

    The other way would be to map to the Code field instead. 
    We suggest map the incoming value to the Code field instead of changing the integration value. This would work for the IO version also. 
     
    Example - MailingStateCode
     
    Comment actions Permalink

Please sign in to leave a comment.