A DataExtDefQuery with no OwnerID answers 1, "did not find a matching object", even when definitions exist
Observed 2026-10-03 on QuickBooks Enterprise Solutions 24.0 (US), reporting qbXML 17.0.
A DataExtDefQueryRq with no filter answers status 1, "did not find a matching object", even when the company file holds a custom field definition. In the XSD every element of the request is optional, so a bare query reads as "list every definition", but QuickBooks does not answer it that way.
The same bare query was sent before and after a DataExtDefAdd with OwnerID 0 and DataExtName "SHIP STATUS" succeeded. A SalesOrderQueryRq with OwnerID 0, sent a second before the second query, returned that field's value, so the definition existed. Both times the query was:
<DataExtDefQueryRq/>
and both times QuickBooks answered:
<DataExtDefQueryRs statusCode="1" statusSeverity="Info" statusMessage="A query request did not find a matching object in QuickBooks" />
What to do
Do not read a status 1 from a bare DataExtDefQueryRq as proof that no definitions exist, and do not create a definition on the strength of it. Send an OwnerID with the query: 0 for custom fields, or your application's GUID for its private data extensions, as Intuit's reference describes.
Not observed
- A
DataExtDefQueryRqwithOwnerID0 has not been sent, so that it lists the custom fields is Intuit's reference, not an observation. - Whether a query by
AssignToObjectalone finds anything. - Whether a bare query also misses private definitions with a GUID
OwnerID.
QuBe Sync is a JSON API for QuickBooks Desktop that is built on what these findings show.