topic Re: 'where' parameter is invalid on query on feature layer in ArcGIS JavaScript Maps SDK Questions

'where' parameter is invalid on query on feature layer

PeterHudson — Wed, 11 Sep 2013 00:54:53 GMT

Hi everyone,
it has been a week that I have this problem.
I haven't changed anything on my code but 1 week ago I received a "'where' parameter is invalid" error when this query is executed on a feature service (hosted on Arcgis online):

var statDef = new StatisticDefinition();
  statDef.statisticType = "sum";
  statDef.onStatisticField = "Area";
  statDef.outStatisticFieldName = "Tot Area";
  
  var query = new Query();
  query.returnGeometry = false;
  query.where = "Area>0";
  query.outFields = ["Area"];
  query.outStatistics = [ statDef ];
  query.groupByFieldsForStatistics = ["YearEstabl", "TypeName"];
  query.orderByFields = ["YearEstabl", "TypeName"];
  
  var qt = new QueryTask("http://services1.arcgis.com/Mpa25zPNMAT08GQg/ArcGIS/rest/services/AllPropertiesEstablished/FeatureServer/0");
  qt.execute(query, function(result){
                   ...
  }
  });

I am referencing to //js.arcgis.com/3.6/

Any ideas?

Thanks in advance!

Re: 'where' parameter is invalid on query on feature layer

VinayBansal — Wed, 11 Sep 2013 11:42:39 GMT

Hi,

I tried running the query using Rest API interface using
http://services1.arcgis.com/Mpa25zPNMAT08GQg/ArcGIS/rest/services/AllPropertiesEstablished/FeatureServer/0/query in browser.
Even there where parameter is giving same error you are getting in your code when using with outStatistics

Don't know why it is not accepting the where clause, as Rest API documentation http://resources.arcgis.com/en/help/rest/apiref/ says that

When using outStatistics the only other parameters that will be used are groupByFieldsForStatistics, orderByFields, text, time, and where.

Re: 'where' parameter is invalid on query on feature layer

JasonZou — Wed, 11 Sep 2013 12:31:35 GMT

To use outStatistics, the layer has to support Statistics. The layer you are querying does not support it. Here is one feature layer that supports it. Look for Supports Statistics: entry.

Re: 'where' parameter is invalid on query on feature layer

VinayBansal — Wed, 11 Sep 2013 14:57:28 GMT

Hi Jason,

But the statistics is working on this layer......if we run query without passing the where clause......
Check the attachment.......

Re: 'where' parameter is invalid on query on feature layer

JasonZou — Wed, 11 Sep 2013 15:07:45 GMT

It seems like spaces are not welcomed for outStatisticFieldName.

Try to change:

statDef.outStatisticFieldName = "Tot Area";

To:

statDef.outStatisticFieldName = "TotArea";

Re: 'where' parameter is invalid on query on feature layer

JasonZou — Wed, 11 Sep 2013 15:43:39 GMT

Interesting. This sample does use where clause for the statistical calculation, and it works. The main difference I can tell is the sample uses a feature layer that supports statistics, while rokitmaps uses a feature service.

Re: 'where' parameter is invalid on query on feature layer

VinayBansal — Wed, 11 Sep 2013 16:24:08 GMT

Interesting. This sample does use where clause for the statistical calculation, and it works. The main difference I can tell is the sample uses a feature layer that supports statistics, while rokitmaps uses a feature service.

Yes Jason, not seeing any other difference, other than Supports statistics......
So rokitmaps, atleast you can give it a try by setting SupportsStatistics true for the layer.....

Re: 'where' parameter is invalid on query on feature layer

PeterHudson — Thu, 12 Sep 2013 05:42:52 GMT

Yes Jason, not seeing any other difference, other than Supports statistics......
So rokitmaps, atleast you can give it a try by setting SupportsStatistics true for the layer.....

From here I can see that "supportsStatistics" : true. In fact it worked before.

The query works without the StatisticDefinition. Anyway, I had to rewrite my code and do the group by manually... 😞

Re: 'where' parameter is invalid on query on feature layer

VinayBansal — Thu, 12 Sep 2013 08:10:47 GMT

You can try by accessing the mapservice as MapServer instead of FeatureServer.....