SQLink Error - List Element Error
When running SQLink with QuickBooks the following message is returned in the SQLink Log: Error adding (Item Name*) 819: There was an error when modifying a (can be any type of name) list, element** "3170000-1189020798". QuickBooks error message: Cannot merge list elements.
- An item in QB can be a customer name, vendor name, inventory item, etc…
- Element “#######-#########” is the QuickBooks unique identifier
Basically either the ‘Name’ or the ‘Element’ is on a list in QuickBooks and therefore the item that SME is exporting will be rejected by QuickBooks.
For example:
Both ListID and the Name are unique keys in QuickBooks. And you modified a customer which prompts to export that Customer with the ListID that matches an existing ListID in QB and the Item Name from another record or the Item Name matches, a more likely scenario, and the ListID is different.
This produces the "Cannot merge list elements" error message back from QuickBooks.
To resolve this issue:
1. Examine the SQLink log: Look at the error:
- Error adding Customer A 819: There was an error when modifying a Customers list, element "3170000-1189020798". QuickBooks error message: Cannot merge list elements.
2. In QuickBooks, locate and edit the name of the vendor/customer:
- Choose Lists > Customer: Job List or Lists > Vendor List, or Lists> Item List, etc… as needs may require.
- Locate and double-click the name noted in the SQLink Log.
- Place a 1 at the end of the name and click OK. Leave QuickBooks and this list open.
3. In SQLink do Data Functions> Export New QuickBooks Data> (List Item). In this case it will be Customers. There should be no error for the specific record and it will export to QuickBooks and sit right next to the QuickBooks Record.
4. In QuickBooks, merge the edited name with the name that has been created by the SQLink:
- In the open list in QuickBooks, double-click the name to which you added a 1.
- Remove the 1 from the name and click OK.
- When asked if you would like to merge the names, click Yes.
5. Do this for all items that have the issue from the SME log.