Dynamics 365 F&O/AX Dynamics 365 CE / CRM Dynamics GP Business Central / NAV UG Dynamics SL Power Platform Fabric UG MS Copilot UG

[Charlotte Sexton]

I am trying to use the Purchasing vendor/Combiner and once I click the process button I receive the following error message:
We attempted using sa to see if it was a security setting but same results. We are on GP 2018 (18.00.0672 R2).. 

Thank you,
Charlotte Sexton 
NBS 
Accounting Operations Manager

——————————
Charlotte Sexton
Accounting Operations Manager
Nation’s Best Sports
Fort Worth TX
——————————

[Aref Karam]

!

Does this happen to all vendors or just this one? Did you try that in a test company/environment?
Do you have third party modules added to GP? Like Mekorma’s Remote Payment Workflow?
If so, there’s maybe a pending item in a workflow for this vendor that needs to be completed/deleted, before you can run the Vendor Combiner Utility.
?

——————————
Aref Karam
Data Consultant
LTI Information Technology
Ann Arbor MI
——————————
——————————————-

[Charlotte Sexton]

. I haven’t attempted with any other vendors but could it be because there are open PO’s for the vendor that I want to move from? PO’s were set up under the incorrect vendor ID (but it is in fact a duplication of the other vendor). Is there an easier way to accomplish this?
We do have third party modules. Mekorma is one but not the remote payment workflow.
My other thought was to set up new PO’s under the correct vendor ID and then cancel the remaining under the incorrect vendor and then make it inactive.

Thanks,
Charlotte
?

——————————
Charlotte Sexton
Accounting Operations Manager
Nation’s Best Sports
Fort Worth TX
——————————
——————————————-

[Blair Christensen]

One thing I’ve noticed about the Combiner/Modifier tools is that they look for ANY column in ANY table in the schema with that column name and attempt to alter the value regardless if it is a Dynamics GP table or not.  We had some custom stuff we were using where we ran into a similar issue as yours – the tool failed because of key constraint errors on our custom stuff.

What I would suggest is to find the offending key’s table and look at the data.  You can use this to get the table:

SELECT COLUMN_NAME
     , TABLE_SCHEMA
     , TABLE_NAME
  FROM INFORMATION_SCHEMA.KEY_COLUMN_USAGE
 WHERE OBJECTPROPERTY(OBJECT_ID(CONSTRAINT_SCHEMA + '.' + QUOTENAME(CONSTRAINT_NAME)), 'IsPrimaryKey') = 1
   AND CONSTRAINT_NAME LIKE 'MEEP%'?

The error is saying that there is already data in the table with values ‘3329’,” which is why the modify is failing.  This is likely old/garbage data which can be removed.

——————————
Blair Christensen
Database Administrator
Oppenheimer Companies, Inc.
Boise Idaho GPUG Chapter Leader
GPUG All-Star
——————————
——————————————-

[Charlotte Sexton]

Thank you for the information. Our IT used the script and cleared the table values and it worked like a charm. Everything moved as expected. Appreciate the help. 
Charlotte

?

——————————
Charlotte Sexton
Accounting Operations Manager
Nation’s Best Sports
Fort Worth TX
——————————
——————————————-