Issue with Temporary Contacts when converting to State/Country Picklists

[mhatfoodcorps]

Greetings, our organization is currently evaluation State/Country Picklists, and has been successful in converting. However, when we attempt to process temporary contacts in sandbox, we encounter this error.

• Household State/Province: There's a problem with this state, even though it may appear correct. Please select a state from the list of valid states.
• Insert failed. First exception on row 0; first error: FIELD_INTEGRITY_EXCEPTION, There's a problem with this state, even though it may appear correct. Please select a state from the list of valid states.: [MailingState]---236-------(CnP_PaaS)

Is there a way to modify temporary contact records to include the state/country picklist. We have set some default custom mapping in our account and contact to assign US to each contact/account record as BillingCountryCode and MailingCountryCode. Currently, we do not have a field in our FaaS form for BillingCountry, in switching to State/Country Picklists, will this be required before switching.

Hope it helps,

Our Sandbox Org Is: 00D0S000000Cqai

[CnP.Support.AM]

Good day @mhatfoodcorps

Would you please share the order number of the temp contact which you are referring to? Also, let us know the ContactID you would like to merge with?

[mhatfoodcorps]

Sure it's 1701201825055751111, and we just want to create a new contact. It's really more of a general thing in which we can create populate a temporary contact with the picklists enabled.

[CnP.Support.AM]

Good day @mhatfoodcorps

Sorry for the late reply. We don't have access to your Sandbox instance. Would you please extend the access so that we can continue the review?

[mhatfoodcorps]

Access Granted for one week. Hope it helps,

[CnP.Support.AM]

Good day @mhatfoodcorps

Do you still have any issue with processing temp contact? We have processed above order number from temp contacts without any issues.

[mhatfoodcorps]

I still do but for now I'll mark as solved. We were intrrested in a native Salesforce feature but I addressed with Kamran earlier and resolved. We'll stick with text fields for now.