SAP Marketing Cloud - Data Import Error "Contact with ID &1 does not have ID &2"

[rebeca_elvetia]

Hello Community,

I have been having this kind of error recently: "Contact with ID &1 does not have ID &2" in the Import Monitor and Data Load Monitor. The message number is the 318 and message class is CUAN_IC, object type CUAN_IMPORT and Service Name API_MKT_CONTACT_SRV.

The number of failed imported records is always 4 consisting of email, permissions and Marketing area.

The Error messages also contain something like this:

• Contact with ID DATAMART-DM0000000XYZ does not have ID EMAIL - name__lastname@email.com
• Contact with ID DATAMART-DM0000000MPQ does not have ID EMAIL- nameNNN_@email2.com
• Contact with ID DATAMART-DM0000000ABC does not have ID EMAIL- name_lastname_@email3.com

Our Database (Datamart) already compiles authenticated and verified emails, the emails (ID &2) exist there for the contacts that present the error as well as the ID&1. In CPI we don't have any error associated with this. So something is preventing the storage in SAP Marketing Cloud.

The emails that are affected as you may see above in the examples have different formats like doble underscore or an underscore before the @domain.com.

Do you think something in SAP Marketing Cloud is preventing the storage of the email like the format?

If so, can we modify that?

Do you think something else must be related?

Thakn you so much for your answers

Regards 

Rebeca

[jan_kaemmerle]

Hello Rebeca,

which API Version of service API_MKT_CONTACT_SRV are you using?
Version 3 or 4?

Please keep in mind, that when you load permission data via the service API_MKT_CONTACT_SRV, the AdditionalIDs need to be loaded in addition. 
With API version 3 you can provide the email address with entity ContactOriginData.
In API version 4 you need to provide the email address with entity AdditionalID.

If you don't provide the email as AdditionalID, then you get the error "Contact with ID &1 does not have ID &2".
If you provide the email as AdditionalID, but you still get the error, then the format of the email address is probably not supported. Then the payload of the AdditionalID fails (then you should also have another error in the Data Load Monitor for that) and therefore the permission record cannot be created.

Please check out the following page for the email validation:
Validation Checks for Email and Phone Numbers | SAP Help Portal

Br,
Ja

[rebeca_elvetia]

Hello.

I think we are using version 4 of service API_MKT_CONTACT_SRV, and we are providing the email.

I just checked the email validation but there is no rule against the email formats MC is failing to import and as you say in consequence the permission record cannot be created as well as the Marketing Area.

If we were using version 3 instead of four, do you think that would explain the error?

Thank you lots!

[jan_kaemmerle]

Hello Rebeca,

[jan_kaemmerle]

Hello Rebeca,

no, you can use the version 4, there is no issue with that. It will lead to the same result.
Just wanted to understand how you send the data.

From my understanding the ContactOriginData and the MarketingArea should be created always.
The AdditionalIds should be created if the email is valid. The Permission/Subscription is related to the AdditionalId. Just when the AdditionalId entity is created correctly, then the Permissin/Subscription can be created.

You should see the errors in the Import Monitor. 

Br,
Jan

[rebeca_elvetia]

Hello Jan, thanks a lot for the reply.

The error the Import Monitor shows is this one:

• [Diagnosis] The imported data refers to a contact to be found via 2 IDs (ID &1 and ID &2).
• [System Response] The system found a contact that has the first ID but not the second ID. This contact was not considered to be the correct one. Therefore no exact match was found.
• [Procedure] A valid matching contact must have all IDs provided.
• Contact with ID ORIGIN - DM0XY does not have ID EMAIL-name_@domain.com

Fails to import 4 records: 

1. CUAN_S_IMPORT_IC_FACET (3 records: IdentityDocuments and Mobile)
2. PERMISSIONS: OUTBOUND_COMM_MEDIUM: WHATSAPP
3. PERMISSIONS: OUTBOUND_COMM_MEDIUM: MOBILE
4. PERMISSIONS: OUTBOUND_COMM_MEDIUM: EMAIL

We checked the database where MC takes the AdditionalID's but there the contact has Email, Phone Number, Permissions and Marketing Area.

CPI also shows that everything was transported successfully but we still got that error in the import Monitor in MC.

We checked the contact created in MC and is missing permissions, marketing area and also the email, but is not missing mobile. I understand now why and how the permissions and AdditionalID's are related.

We thought it was due to the validation checks for email that the import was failing, but there is no rule against the format of the emails that MC is failing to import and as you explained we don't have any other error generated in the Import Monitor.

The Marketing Area in this case seems to be dependent of the Permissions also, since it doesn't import if the when the permissions are not being imported but we'll check the API maybe there is something else.