topic Re: resultOffset & resultRecordCount Parameters are causing the query to return No records found in ArcGIS Server with JavaScript API Questions

resultOffset & resultRecordCount Parameters are causing the query to return No records found

JoshVan_Kylen — Thu, 05 Apr 2018 16:52:25 GMT

setDefinitionExpression is including the resultOffset and resultRecordCount parameters that are causing the service query to return No records found. If I make the same query without these parameters it returns records.

How can I eliminate these parameters from being added to the query when I set the definition expression?

How can I get the service to return records with these parameters set?

resultOffset=0

resultRecordCount=1000

No records found query

https://gis.maricopa.gov/arcgis/rest/services/Flo2d/Flo2d_Boundaries/MapServer/1/query?f=json&where=admp%20%3D%20%27121_…

If I remove theses parameters &resultOffset=0&resultRecordCount=1000 then it returns the expected 72 records.

https://gis.maricopa.gov/arcgis/rest/services/Flo2d/Flo2d_Boundaries/MapServer/1/query?f=json&where=admp%20%3D%20%27121_…

Also of note if I change the where statement to 1=1 it will return all the records even with the resultOffset and resultRecordCount parameters.

https://gis.maricopa.gov/arcgis/rest/services/Flo2d/Flo2d_Boundaries/MapServer/1/query?f=json&where=1=1&returnGeometry=t…

Re: resultOffset & resultRecordCount Parameters are causing the query to return No records found

RodrigoFelga — Thu, 05 Apr 2018 17:21:08 GMT

I think that question should be on the ArcGIS Server topic.

Folow that link to see if it helps: Error: Pagination is not supported

Re: resultOffset & resultRecordCount Parameters are causing the query to return No records found

JoshVan_Kylen — Thu, 05 Apr 2018 17:29:04 GMT

Thanks,

The service indicates that it supports advanced queries including Pagination.

So, how can I eliminate the resultOffset and resultRecordCount parameters and values from being included in the query that is generated by the setDefinitionExpression?

Re: resultOffset & resultRecordCount Parameters are causing the query to return No records found

RodrigoFelga — Thu, 05 Apr 2018 18:18:58 GMT

I think that could be a bug on ArcGIS Server. It should return the records with the 2 parameters. I don't know how to remove it in the API

Re: resultOffset & resultRecordCount Parameters are causing the query to return No records found

JoshVan_Kylen — Thu, 05 Apr 2018 18:30:54 GMT

Changing the feature layer from MODE_SNAPSHOT to the default MODE_ONDEMAND seems to have solved the issue.

Re: resultOffset & resultRecordCount Parameters are causing the query to return No records found

JackFairfield — Mon, 07 May 2018 21:52:56 GMT

I have experienced the same issue in ArcServer 10.51.

The only workaround that worked for me when using the 4.x api was to enable feature access in the manager under Capabilities

And then to reference the rest endpoint at "FeatureServer" instead of "MapServer"

For Example:

https://domain/arcgis/rest/services/maps/test/FeatureServer

Re: resultOffset & resultRecordCount Parameters are causing the query to return No records found

JackFairfield — Mon, 07 May 2018 21:55:20 GMT

This is only available in the 3.x version of the API. The newer 4.x version doesn't have this property.

Re: resultOffset & resultRecordCount Parameters are causing the query to return No records found

EricO_Neal1 — Tue, 15 Jan 2019 18:27:25 GMT

Remove line 774 of Search.js and it should go away.

https://gis.stackexchange.com/questions/146331/pagination-not-supported-error-occurs-when-searching-feature-layers-using-the/308735#308735

Re: resultOffset & resultRecordCount Parameters are causing the query to return No records found

simoxu — Mon, 09 Mar 2020 23:16:04 GMT

I have the similar issue.

I found the problem is at the REST API level when querying a ArcGIS Server Map/Feature Service with a spatial filter.

If the resultOffset and resultRecordCount are not set, it returns all the matching records, if they are set the query returns wrong number of records. for example, if the resultRecordCount is set to 500, it only returns 36 records with exceededTransferLimit=True.

This issue should affect all the other APIs that wraps the REST API, such as Javascript API, Python API, ArcGIS Runtime SDKs...