Is there any progress on this? We can’t delay indefinitely.
Sent you a Google Drive link.
Yes, we can share the company file with you. FYI, it’s 1.20GB.
How do you want it shared? Dropbox, http://FTP…?
I literally just did that a few days ago and had exactly the same problem.
I removed the primary key from the two tables I’ve been having issues with (buildassembly and transaction), and tried to run the populate operation again. The error is essentially the same:
Cannot insert duplicate key row in object ‘dbo.buildassembly’ with unique index ‘buildassemblyIdIndex’. The duplicate key value is (2A64E9-1457553398).: componentitemline in table buildassembly:-2147217873
We just bought this software, and haven’t ever been able to run a full populate operation. This issue is blocking our bulk item number updates, and the deployment of our new manufacturing control software. We need an immediate solution.
I’m looking at the Browser in tree view, but there are no child tables under Items.
Obviously there are references using the same item IDs in other tables, such as itemsites. Will *all* references to the item IDs in the items table be updated when that table is changed? Or do they need to be explicitly changed as well–and if so, which tables contain references that need changing?
Okay, will do.
We’re running QuickBooks Enterprise Manufacturing and Wholesale 17.
I grabbed an older copy of our QuickBooks file and created a new database for it (from OpenSync directly). Set up a Populate from QB operation from it and ran it for the first time. Same error.
Any more ideas?
Initially yes. The same problem occurs when running the “Refresh from QB” operation.
That was a brand-new database being populated for the first time. Why would the second attempt work differently?
After removing the buildassembly table, we’re also getting:
Failed: Violation of PRIMARY KEY constraint ‘PK_transaction’. Cannot insert duplicate key in object ‘dbo.transaction’. The duplicate key value is (35F142-1506010688).: Memo in table transaction:-2147217873
Log files sent.
We’re simply excluding that table from the task for the time being.