Note: ListMerge requires the company file to be opened in single user mode.

ListMergeType: may have one of the following values: Account, Class, Customer, ItemDiscount, ItemGroup, ItemInventory, ItemNonInventory, ItemOtherCharge, ItemPayment, ItemSalesTax, ItemSalesTaxGroup, ItemService, ItemSubtotal, Vendor.

ListMergeType true true true
MergeFrom_ListID true false true
MergeFrom_EditSequence true false true
MergeTo_ListID true false true
MergeTo_EditSequence true false true
SameShipAddrOk true false optional
MergedFrom_ListID false true false
MergedFrom_TimeDeleted false true false
MergedFrom_FullName false true false
MergedTo_ListID false true false
MergedTo_TimeCreated false true false
MergedTo_TimeModified false true false
MergedTo_EditSequence false true false
MergedTo_FullName false true false
OperationMerged, Error, Null (potential values on the response)merge (no case sensitive)


What happens in the ListMerge operation?

  • What happens in the merge is that one of the objects, the “merge-from” object, is merged into the other object, the “merge-to” object. For example, suppose the expense account “Paper Reams” is merged into the expense account “Office Supplies.” After the merge, there is only the “Office Supplies” account, and all transactions in the past that referenced “Paper Reams” now automatically reference “Office Supplies.” This means that balances will change in the merged-to object as it receives the merged-from balances.

When can I not do a ListMerge?

  • You cannot do a ListMerge if an accountant copy of the company exists–if you do, you’ll get an error. The idea is that any merges ought to be done in the accountant copy. Beginning with QB 2009 and qbXML 8.0, you can use the Account Copy Exists request to check for this before issuing the list merge request.

Can I undo or reverse a ListMerge?

  • No

What must I do before merging?

The merging rules are not many in number, but they are different for accounts, customers, and vendors. The following table shows the rules applying to each:

Objects to MergeRequired Pre-Merge ConditionsHow to Satisfy the Conditions
AccountsAccounts must be of the same AccountType.
Accounts must be at the same hierarchical level within the chart of accounts.
If the AccountTypes are different, you cannot proceed. You cannot change the AccountType.
You can change the Sublevel of one account so that it matches the Sublevel of the other account. For more information, see “Merging Accounts.”
ClassNo requirementsNA.
Only one of the customer/customer jobs can have child elements.
You cannot merge a customer and a vendor.
If you merge customers, only one of the customers can have customer jobs. If you merge customer jobs, only one of them can have children (sub-jobs).
Cannot change this.
If merging customers and both customers have jobs, you must move jobs from the merge-from customer to the “merge-to” customer before invoking ListMerge. Or, you must make them inactive or delete them.
If merging customer jobs, only one of them may have child jobs (sub jobs). If both have children, you must move child jobs from merge-from object to the merge-to object BEFORE doing the merge. Or make them inactive or delete them.
For more information, see “Merging Customers,” below.
VendorsYou cannot merge a customer and a vendorCannot change this.

Powered by BetterDocs