10
Receiving error message using customer combiner with Primary Key Constraint 'PKCU_CustomerAddressCheck' Cannot insert duplicate key in object 'dbo.CU-Customer AddressCheck. Anyone know of a solution?
*This post is locked for comments
I have the same question (0)
The customer combiner runs through your GP company database looking for fields named CUSTNMBR and will attempt to update any records in those fields with the new customer number you are merging records into.
For native GP tables the process is aware where a primary key exists and has logic to deal with it, but for 3rd party product or addin tables it will blindly attempt to do this rename, even if that field is part of a primary key, this results in the prime key error as two records with the same customer number will be created if one already existed for the customer number you are merging into (Simply, a primary key only allows one record of that name in the table).
So I think that CU_CustomerAddressCheck is a table for some extra product in your GP installation, that does not support the rename functionality. You need to work out what that product or modification is, then approach the vendor or person that made that table so that an appropriate fix can be put in place.
This post mentions the issue you are having:
www.timwappat.info/.../Care-naming-database-objects-in-Dynamics-GP-for-custom-GP-Addins
This post talks more generally about what is going on:
www.timwappat.info/.../Customer-combiner-and-table-not-found-errors
Tim.
Share
Report
All responses (
Answers (
