In my salesforce report I have the ContactID in a 15character digit format. When I import in Marketing Cloud it automatically imports with the 18 digit Character and I know the 18 digits is the format used when importing data from Salesforce into Marketing Cloud.

What I don't understand is that sometimes I get the CaseSensitiveSalesforceID. So why in some instances I get this error message in my import and sometimes Marketing Cloud automatically imports with 18 digits?

thank you, Giulietta enter image description here

enter image description here

  • What error message are you seeing? – sfdcfox Mar 15 '18 at 15:19
  • 4
    You may want to censor your image so business contact names and emails are not shared on a public site. Also it looks like in your report you are filtering based on a field called "18 Char Contact Id" but you appear to be looking for this data in the standard ID field which will show you the 15 digit ID. Can you not add the 18 character field to the report? – JaredT Mar 15 '18 at 15:28
  • Thanks Jared. I have edited the pics. Reason why customer used this field is that contactID in the report upon the import creates a Sendable Salesforce Data Extension; whereas using 18 character it creates a non sendable ''non salesforce'' data extension. But this also doesn't explain the behaviour I see. So the report in the pics imported into marketing cloud with the 18 digits, even though in Salesforce we have the 15 digits; but I have other reports where if I use the same 15 digits Contact ID in Salesforce when I attempt to import it in Marketing Cloud I get the validation errors. Thanks!G – Giulietta Mar 16 '18 at 9:17
  • I digged into this deeper and looks like different report types show different behaviours. Report Type: Contacts & Accounts " Imports with 15 characters Contact ID (comes from Contact object) Bookings with Booking Passengers and Components " Fails to import the 15 character Contact ID (Consultant Contact ID comes from Booking Object) Requests - Customer - Booking Imports the 15 character as the 18 character (contact ID comes from Requests object). I understand this is quite unique setup but I was wondering if anyone encountered this behaviour in their SF environment? Thanks. G – Giulietta Mar 20 '18 at 10:37
  • Issue was related to the fact that in different report I had a different naming for Contact ID and therefore upon the import I was seeing different behaviours – Giulietta Apr 23 '18 at 9:26

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Browse other questions tagged or ask your own question.