Hi all - Has anyone faced any issue in using the SOAP webservices and query an Item Fulfilment saved search, where there are over a 1000 rows? We are seeing an issue where the ss shows 1012 rows but when making the query in soap, we see the last 12 rows of data not appear in the response. The 12 that do appear in the response are duplicates from the first page in the xml response.

what do your 2 requests look like

upon investigating further, there is a definite issue with the soap results: NS ss - 1012 unique records soap - 1012 records, some of which are not unique. page 1 - 1000 page 2 - 12 record (some of these exist in page 1). We are using a transactionListQuery against a Saved search script ID. Seeing the same issue with SOAP and when making call restlet with the saved search ID

Use the SOAP Web Services Usage Log to find out what the requets look like, share them here

sure - i've validated that the soap logs include the dupes. the internal ID of the record (custom record) appears twice 12 times (total of 24)

its not really the response thats important, its the request

both requests attached (page 1 and 2)

those requests look mostly reasonable, the only obvious looking thing is to make sure the custom records arent being modified between requests

can confirm the records are not being modified. Have actually changed the sort by on the saved search from Date > to Internal ID and surprisingly not getting the dupe issue in the UI or Restlet call - SOAP still exists.

Is there formulas in your saved search results?

no formulas. it has a few joins to the custom table from the item fulfilment record (base record).

how about grouping?

@Israel cannot group on this search as soap would not work in that case - have raised with ACS