Checking for duplicates when importing cards

Post Reply
TransPost Support
TransPost team member
Posts: 42
Joined: Wed 11 Mar, 2015 9:31 pm

Checking for duplicates when importing cards

Post by TransPost Support » Sun 22 Mar, 2015 10:26 pm

TransPost apps all check that a customer card does not already exist before inserting a customer.

If there is no CardID then TransPost will not insert a customer if there is already one with the same name. If you want to allow non-unique customer names we would strongly recommend using cardIDs if possible.

If CardIDs are used then they are used exclusively to identify the Customer. A new customer can have the same name as an existing one as long as the CardID is different.

Customer data can only be updated when CardIDs are being used to identify customers as it is impossible to tell if a Customer with the same name as an existing one is mean to to be an update or a new customer with the same name.

If 'Update data in existing records' is selected and, then if data is imported for an existing customer, it is checked against the current data. If it matches exactly the no update will occur. If there are differences then changes will be imported and the log will reflect that.

In TransPost Plus the above applies to Suppliers too.

Post Reply