I have an import scenario where I would like to use address line 1 and the postal code of the customer’s account as key fields instead of the customer ID and then update 2 user defined fields. This current import mapping isn’t working.
Question
Designate non-key fields as a key field
I have this updated scenario that still doesn’t work but I think it’s closer to what is needed?
As a side note I have had a similar scenario work when using a customer ID and was able to update the UDF the same way as I am doing in this one.
Translate
I have this updated scenario that still doesn’t work but I think it’s closer to what is needed?
As a side note I have had a similar scenario work when using a customer ID and was able to update the UDF the same way as I am doing in this one.
I wasn’t able to get this to work either, for the main reason being that an Address is not necessarily unique.
Think about that within the same building there can be multiple businesses and you would have to narrow this down quite drastically to make it unique.
Best alternative might be a substitution list where you export all available address fields, try to make it one unique field and map it to the customer id.
If somebody has gotten this to work or a different idea, I am all ears!
Translate
Hi
Translate
+8Hi
I think you should add the Customer Key field (AcctCD) and Action:Cancel. You should also add AddressLine1 and PostalCode after the key fields and search to map the actual values from your DataProvider. That will reference the correct record and then you can update with what you have in your mapping.
Hope that will work for you!
Translate
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.