06-06-2014, 03:03 AM
Good and bad news... afterall... good news!
The contact ID field is now recognized by the CRM Field column, however instead of merging the records corebos is actually creating new ones. Yes I made sure to select the duplicate checkbox and select the "merge" option. I've tried it twice and each time the records are created instead of being merged.
EDIT: I figured out why it does this. When importing I was actually choosing ISO-8859-1 as the encoding (as for some reason using UTF-8 screws up special characters). I also chose several fields for identification namely: contact ID, first name and last names. I beleive that for the first and last names Corebos was interpreting the data as if it was different (due to the encoding) thus creating new records instead of merging them.
I have actually found a way to resolved this and also keeping the ISO-8859-1 encoding . It's by ONLY using the Contact ID as identifier in Step 3.
All contacts are now merged. Thanks Joe.
The contact ID field is now recognized by the CRM Field column, however instead of merging the records corebos is actually creating new ones. Yes I made sure to select the duplicate checkbox and select the "merge" option. I've tried it twice and each time the records are created instead of being merged.
EDIT: I figured out why it does this. When importing I was actually choosing ISO-8859-1 as the encoding (as for some reason using UTF-8 screws up special characters). I also chose several fields for identification namely: contact ID, first name and last names. I beleive that for the first and last names Corebos was interpreting the data as if it was different (due to the encoding) thus creating new records instead of merging them.
I have actually found a way to resolved this and also keeping the ISO-8859-1 encoding . It's by ONLY using the Contact ID as identifier in Step 3.
All contacts are now merged. Thanks Joe.