I can't understand why the Update action in an import workflow duplicates the profiles.
I explain better:
I have this workflow:
The file csv that I have to import has different columns. We have a customer ID, emails, first name and so on.
In the file there are 221.506 profiles with these caractheristics:
- for one email we can have different customer ids ( firstname.lastname@example.org can have 5 different customer id)
- for one customer id we can have only one email
The strange thing is when there is a Update action (insert or update profiles) with reconciliation criteria by Customer id and email, the outgoing population is larger than the incoming population.
There are about 500 duplicate profiles.
I can't understand why the update action duplicate the profiles.
Someone have any suggestion?
sorry for my late.
I checked and I don't have duplicates.
I solved the problem by setting the reconciliation criteria only by Customer IDs because I am sure that they are unique.
This setting works fine.
in my case the reconciliation is used to have an idea of existing profiles vs new profiles.
@eveline8: can you check in your profiles table if you have duplicate on customer ID and email?
I'm doing the same thing to Insert or Update my customer, and I have a custom ID too. I don't understand why you're using a reconciliation activity in your workflow ?
Here you can see mine :
My reconciliation with Profile table is directly in the Update data activity :
I confirm that in the file there aren't empty values in the email and customer id fields.
Can you please confirm if the email field in your file have some empty value (assuming that your customer ID is not nullable)?
If it's the case then you need to add a default value (example 0) instead of keeping the empty value.
The reason is ACS is not able to identify empty field when doing a reconciliation or data update.