topic Re: returnDistinctValues does not always work in ArcGIS JavaScript Maps SDK Questions

returnDistinctValues does not always work

EdwardSohn2 — Mon, 22 Dec 2014 21:04:54 GMT

Using:

var queryTask = new QueryTask(layer.layerObject.url + "?returnDistinctValues=true");

But sometimes this works and sometimes it does not.

Are there any server settings for each layer (featurelayer) that needs to be specified precisely to make the returnDistinctValues=true work?

Using v. 3.10.

Re: returnDistinctValues does not always work

ReneRubalcava — Mon, 22 Dec 2014 21:16:23 GMT

Looking at the docs, you need to specify the field for distinctValues in the outFields parameter and need server 10.11 minimum. supportsAdvancedQueries of the service also needs to be true, but I think true is the default setting when a service is published.

Does it work consistently when you perform the query via the REST HTML page of the sevice?

Re: returnDistinctValues does not always work

EdwardSohn2 — Mon, 22 Dec 2014 21:32:57 GMT

Seems like the layers for which it does not work are feature collections and those for which it works are feature services... (at least for two of the layers for which it did not work...) Do they really need to be feature services? Is it possible to make it work for feature collections?

Re: returnDistinctValues does not always work

JohnGrayson — Mon, 22 Dec 2014 21:41:23 GMT

From the API help; when dealing with FeatureCollection based FeatureLayers: Does not support queries that need to be performed on the server, e.g. queries with a where clause or non-extent based spatial queries.

FeatureLayer | API Reference | ArcGIS API for JavaScript

Re: returnDistinctValues does not always work

EdwardSohn2 — Tue, 30 Dec 2014 23:28:35 GMT

The layers apparently are both feature services and they both have supportsAdvancedQueries set to true. But the returnDistinctValues=true are still not working... (and yes the field is being sent as outFields parameter in the queries)...

Re: returnDistinctValues does not always work

JohnGrayson — Wed, 31 Dec 2014 00:44:33 GMT

Edward, do you have a jsfiddle or jsbin showing the issue? If not, do you have a rest url endpoint and query parameters that we can try it out?

Re: returnDistinctValues does not always work

EdwardSohn2 — Wed, 31 Dec 2014 03:44:27 GMT

Oh btw, the server url seem to be different:

Those that work are of type:

"https://utility.arcgis.com/usrsvcs/...?returnDistinctValues=true"

Those that don't work all seem to be of type:

"https://services2.arcgis.com/...?returnDistinctValues=true"

i.e. starting with https://services2.arcgis.com/

Here is one example which doesn't seem to work:

"https://services2.arcgis.com/OzJIHUWI4lRJCw0e/arcgis/rest/services/BusStop/FeatureServer/0?returnDistinctValues=true"

Re: returnDistinctValues does not always work

JohnGrayson — Wed, 31 Dec 2014 05:29:52 GMT

Edward,

returnDistinctValues is a property on the JS API Query object, not a parameter of the url of the service, so please don't include it when creating the Query instance. The services you mention are secure services so make sure you include a reference to esri/IdentityManager so the appropriate credentials are obtained and used by the JS API before you make the request.

It would help if you shared some of the JS code so we can figure out what is going on.

John

Re: returnDistinctValues does not always work

EdwardSohn2 — Wed, 31 Dec 2014 17:51:44 GMT

Currently we are using 3.10. returnDistinctValues is not defined until 3.11. Sending as query parameter does work... but only for utility.arcgis.com/usrsvcs...

doesn't work for services2.arcgis.com urls...

I tried upgrading to 3.11 and using

var queryTask = new QueryTask(layer.layerObject.url);

var esriQuery = new Query();

esriQuery.returnDistinctValues = true;

esriQuery.outFields = [attribute];

esriQuery.where = typeof layer.layerObject.defaultDefinitionExpression === "undefined" || layer.layerObject.defaultDefinitionExpression === null ? "1=1" : layer.layerObject.defaultDefinitionExpression;

Got same results:

Worked for utility.arcgis.com/usrsvcs...

doesn't work for services2.arcgis.com urls...

Re: returnDistinctValues does not always work

ReneRubalcava — Wed, 31 Dec 2014 18:05:24 GMT

If you are using 3.10, you'll need to hack it a little bit using setRequestPreCallback as described in this thread.

Re: returnDistinctValues does not always work

EdwardSohn2 — Wed, 31 Dec 2014 18:50:43 GMT

Hi,

I am able to upgrade to 3.11/3.12, and it works, but for some of those urls does not work...

Worked for utility.arcgis.com/usrsvcs...

doesn't work for services2.arcgis.com urls...

API doc says ArcGIS Server 10.1 Service Pack 1 required. Is it poss that services2.arcgis.com fails this requirement..?

Just wondering...