This Week in QuickBooks: Web Connector Pitfalls, API Limits, and File Fixes

• Web Connector duplicate loop — enqueuing the same record on every sync creates unlimited duplicates; the fix is tracking the last successful MsgId returned by QuickBooks so your service never re-sends a record already processed.
• QBO API caps queries at 100 rows — the API returns a startPosition and maxResults field in every response; increment startPosition by the number of rows returned and re-query until the result count drops below your page size.
• SyncToken errors on customer updates — constructing a customer object from scratch and calling Update fails because the API requires the current SyncToken value; always issue a FindById first, modify the returned object, then submit.

Web Connector: Stopping the Duplicate Loop and Empty-Queue Crashes

The duplicate-record problem stems from a subtle design flaw: the Web Connector calls your sendRequestXML method repeatedly until you return an empty string, and if your queue logic re-populates on every call, the same customer or transaction gets enqueued indefinitely. The concrete fix is to maintain a persistent cursor — after QuickBooks processes a record, store its ListID or TxnID and the returned MsgId, then skip any queued item whose ID matches. When the queue is genuinely empty, your receiveResponseXML method must return a valid strHCPResponse with statusCode set to 0; returning a malformed or null authentication response triggers the SOAP parse error that puzzles many developers. For scheduled syncs, register a serverVersion or clientVersion login hook to enqueue only records modified since the last run — query customers, estimates, and sales orders by TimeModified ranges rather than pulling everything each cycle.

QBO API: Pagination, SyncTokens, and Tax Code Values

Beyond the 100-row limit, two other API pitfalls surface this week. First, updating a customer fails with a validation error when you build a fresh Customer object and set its Id — the API demands the exact SyncToken from the last read or write, so retrieve the object first via FindById, modify it, and submit the same instance. Second, invoice lines reject numeric tax code IDs in US company files; the API expects the literal strings TAX or NON on each line, not the internal TaxCode.Id. If you need the actual tax rate applied, pull it separately from the TaxCode and TaxRate endpoints after the invoice posts.

Desktop: Error -6130, Bloated Files, and COM Registration

Error -6130 on company file open typically points to a broken .ND or .TLG file or a stalled database service — rename the .ND and .TLG files, restart the QuickBooksDB Windows service, and reopen the file. Separately, bulk time-clock imports through the Web Connector generate thousands of individual timesheet entries that bloat the company file and degrade performance; batch imports into summary entries where possible, and monitor file size closely. Finally, custom apps throwing “Class Not Registered” on deployment need the QuickBooks integration components installed on the target machine — the SDK alone is not enough; run the QuickBooks installation with integration support enabled.