An iterated query by ListID or FullName answers 3150 for a missing MaxReturned, which the XSD forbids beside an id, so an iterator can never be combined with an id
Observed 2026-10-02 on QuickBooks Enterprise Solutions 24.0 (US), reporting qbXML 17.0.
An iterated list query that looks a record up by ListID or FullName is refused with 3150, "There is a missing element: "MaxReturned"". It is the same answer as for any iterated query without MaxReturned. In the XSD, ListID, FullName and the filter group are branches of one choice, and MaxReturned belongs to the filter branch, so a query cannot carry both an id and MaxReturned. An iterator beside an id can therefore never be answered.
By ListID, for a customer that exists:
<CustomerQueryRq requestID="1" iterator="Start"><ListID>80000020-1790716232</ListID></CustomerQueryRq>
<CustomerQueryRs requestID="1" statusCode="3150" statusSeverity="Error" statusMessage="There is a missing element: "MaxReturned"." />
By FullName:
<CustomerQueryRq requestID="2" iterator="Start"><FullName>WF Real 085202</FullName></CustomerQueryRq>
<CustomerQueryRs requestID="2" statusCode="3150" statusSeverity="Error" statusMessage="There is a missing element: "MaxReturned"." />
What to do
Leave the iterator attribute off any query that names records by ListID or FullName. Iterate only a query that uses the filter branch, and give it a MaxReturned.
Not observed
- A query with both an id and
MaxReturned, which the XSD does not allow, has not been sent. - Transaction queries by
TxnIDorRefNumberwith an iterator. OnlyCustomerQueryRqwas tried.
Error codes on this page
QuBe Sync is a JSON API for QuickBooks Desktop that is built on what these findings show.