topic Re: eSearch 2.12 potential issue - Query Layers in Web AppBuilder Custom Widgets Questions

eSearch 2.12 potential issue - Query Layers

RodWoodfordOld — Fri, 27 Sep 2019 06:59:28 GMT

Hi Robert,

I'm currently using eSearch 2.12 and am experiencing issues when using query layers with unique value settings. No options are returned even for small services. I have upgraded from 2.6 where I had no issue with the same query layers. Any advice would be useful.

cheers

Re: eSearch 2.12 potential issue - Query Layers

RobertScheitlin__GISP — Fri, 27 Sep 2019 13:01:12 GMT

Any errors in the web console you can share? Is it a public site I can test?

Re: eSearch 2.12 potential issue - Query Layers

RodWoodfordOld — Tue, 01 Oct 2019 00:55:54 GMT

Hi Robert,

I've stripped the query layer back to return only 5 records and still get the following error. There are no null values. Works fine when selecting by point, line, polygon, etc and when building a textual search using by value. It just want work when adding the unique values option.

Widget.js?wab_dv=2.12:2727 Uncaught TypeError: Cannot read property 'hasOwnProperty' of null
at Object.buildWhereClause (Widget.js?wab_dv=2.12:2727)
at Object.search (Widget.js?wab_dv=2.12:2498)
at Object.onSearch (Widget.js?wab_dv=2.12:2201)
at HTMLDivElement.<anonymous> (init.js:64)

Hope this helps.

Re: eSearch 2.12 potential issue - Query Layers

RobertScheitlin__GISP — Tue, 01 Oct 2019 12:40:59 GMT

Rod,

That is not a lot of help. Basically that error is saying that it can not get the string(s)/value(s) that you are searching for in the widgets input.

Please answer all questions.

Do you have more than one input configured for this search?
Again is your site public or the service you are using?

Re: eSearch 2.12 potential issue - Query Layers

RodWoodfordOld — Tue, 01 Oct 2019 12:49:26 GMT

Robert see below.

1 - I have tried single input and multiple inputs with no success when using the unique value option. Like I said all other options work fine, it only fails when i engage the unique values option.

2 - No its not public but potentially will be if I can get it to work.

Hope this helps.

cheers

Re: eSearch 2.12 potential issue - Query Layers

RobertScheitlin__GISP — Tue, 01 Oct 2019 13:00:04 GMT

Rod,

Sorry I am not sure what else I can do to help. As I mentioned the exact error you are getting is based on it not being able to get the value of the search input.

So are you able to see it get all the unique values then choose one of those before you get to this error?

Re: eSearch 2.12 potential issue - Query Layers

RodWoodfordOld — Tue, 01 Oct 2019 13:05:15 GMT

Thanks Robert,

I'll do some more testing tomorrow and get back to you.

cheers

Re: eSearch 2.12 potential issue - Query Layers

RodWoodfordOld — Wed, 02 Oct 2019 11:11:29 GMT

Hi Robert,

I have tried different query layers to no avail in eSearch 2.12 unique values setup. I can advice that all query layers I have generated today work with WABD 2.12 generic widgets such as the QUERY widget for unique values setup. They also work with the EXTRA DATA SOURCE option. So I'm at a loss as to why eSearch 2.12 will not allow me to set unique values for these same query layers. Have you tested query layers with the unique option setup in 2.12?

At this stage all I can do is use the generic WABD 2.12 query widget for unique drop down searches and use eSearch for all other type of searches for these query layers.

Also I had no issue creating the unique value setting option in Esearch when using feature classes in rest end points. Its just query layer rest end points that seem to have this problem.

To answer your question from yesterday;

So are you able to see it get all the unique values then choose one of those before you get to this error? NO, I don't get any values returned when configuring the values, it just hangs.

Hope this info helps at all.

cheers

Re: eSearch 2.12 potential issue - Query Layers

RobertScheitlin__GISP — Wed, 02 Oct 2019 12:07:07 GMT

Rod,

I don't use query layer or have access to any to do testing on it.

Re: eSearch 2.12 potential issue - Query Layers

RodWoodfordOld — Wed, 02 Oct 2019 12:54:41 GMT

Robert,

If I setup a public query layer, would you have time and be happy to test it within eSearch to identity the issue?

cheers

Re: eSearch 2.12 potential issue - Query Layers

RobertScheitlin__GISP — Wed, 02 Oct 2019 13:52:29 GMT

Sure

Re: eSearch 2.12 potential issue - Query Layers

RodWoodfordOld — Wed, 16 Oct 2019 05:06:50 GMT

Sorry for the delay. See below to test. Works at 2.6 without issue.

Layer: PropertyWard (ID: 0)

Re: eSearch 2.12 potential issue - Query Layers

RobertScheitlin__GISP — Wed, 16 Oct 2019 14:07:38 GMT

Rod,

What version of ArcGIS Server are you running on this server?

Re: eSearch 2.12 potential issue - Query Layers

RodWoodfordOld — Wed, 16 Oct 2019 22:37:38 GMT

10.5.1 in prod and 10.6.1 in dev. I've tried both.

Re: eSearch 2.12 potential issue - Query Layers

RobertScheitlin__GISP — Sun, 12 Dec 2021 08:41:26 GMT

Rod,

There seems to be be something particular about QueryLayers that do not allow a query for distinct values to work when you are just querying for count. Using a standard layer has no issue at all with this same query. I have a simple code change for you that will get you past this issue. In my later versions I make a change that utilizes this type of query to expedite unique value results but never tested against query layers as I never use them.

In the widgets PagingQueryTask.js replace the existing execute function with this one:

      execute: function () {
        this.uniqueValues = [];
        this.blankStringExists = false;
        this.iStart = 0;
        this.iMaxRecords = 0;
        this.featuresProcessed = 0;
        this.featuresTotal = 0;

        this.isQuerying = true;
        this.query.returnGeometry = false;
        this.query.outFields = [this.fieldName];
        if (this.version > 10.11) {
          this.query.orderByFields = [this.fieldName];
        }
        this.query.objectIds = null;
        if (this.defExpr && this.defExpr !== "") {
          this.query.where = this.defExpr;
        } else {
          this.query.where = "1=1";
        }
        if (this.uri === '') {
          this.emit('pagingFault');
          return;
        }
        // console.info(this.uri);
        this.queryTask = new QueryTask(this.uri);
        if (this.version >= 10.1) {
          //need to check if the feature count is over maxRecordCount
          var cntQuery = new Query();
          if (this.defExpr && this.defExpr !== "") {
            cntQuery.where = this.defExpr;
          } else {
            cntQuery.where = "1=1";
          }
          cntQuery.returnDistinctValues = true;
          cntQuery.outFields = [this.fieldName];
          this.queryTask.executeForCount(cntQuery, lang.hitch(this, function(count){
            this.featuresTotal = count;
            if(count <= this.maxRecordCount){
              this.allValues = [];
              this.query.returnDistinctValues = true;
              this.queryTask.execute(this.query, lang.hitch(this, this.onSearchFinish), lang.hitch(this, this.onSearchError));
            }else{
              delete this.query.orderByFields;
              this.queryTask.executeForIds(this.query, lang.hitch(this, this.onSearchIdsFinish), lang.hitch(this, this.onSearchError));
            }
          }));
        } else {
          this.queryTask.executeForIds(this.query, lang.hitch(this, this.onSearchIdsFinish), lang.hitch(this, this.onSearchError));
        }
      },‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍

Re: eSearch 2.12 potential issue - Query Layers

RodWoodfordOld — Mon, 21 Oct 2019 00:53:11 GMT

Hi Robert,

Thank you for the update. Just tried this in WABD 2.12 with the test url and it still does not work. I get the "retrieving unique values" spinning around when I select a value. When I look at your code change, I don't see anything different to the original code. Could this be the issue.

cheers

Re: eSearch 2.12 potential issue - Query Layers

RobertScheitlin__GISP — Mon, 21 Oct 2019 12:35:10 GMT

Rod,

You must be placing the change in the wrong location or something. I have tested this with your data and it worked on my end.

Re: eSearch 2.12 potential issue - Query Layers

RodWoodfordOld — Mon, 21 Oct 2019 12:44:17 GMT

I added it into the eSearch PagingQueryTask.js as requested. See below between the italic code.

startup: function () {
this.inherited(arguments);
this.query = new Query();
},

execute: function () {
this.uniqueValues = [];
this.blankStringExists = false;
this.iStart = 0;
this.iMaxRecords = 0;
this.featuresProcessed = 0;
this.featuresTotal = 0;

this.isQuerying = true;
this.query.returnGeometry = false;
this.query.outFields = [this.fieldName];
if (this.version > 10.11) {
this.query.orderByFields = [this.fieldName];
}
this.query.objectIds = null;
if (this.defExpr && this.defExpr !== "") {
this.query.where = this.defExpr;
} else {
this.query.where = "1=1";
}
if (this.uri === '') {
this.emit('pagingFault');
return;
}
// console.info(this.uri);
this.queryTask = new QueryTask(this.uri);
if (this.version >= 10.1) {
//need to check if the feature count is over maxRecordCount
var cntQuery = new Query();
if (this.defExpr && this.defExpr !== "") {
cntQuery.where = this.defExpr;
} else {
cntQuery.where = "1=1";
}
cntQuery.returnDistinctValues = true;
cntQuery.outFields = [this.fieldName];
this.queryTask.executeForCount(cntQuery, lang.hitch(this, function(count){
this.featuresTotal = count;
if(count <= this.maxRecordCount){
this.allValues = [];
this.query.returnDistinctValues = true;
this.queryTask.execute(this.query, lang.hitch(this, this.onSearchFinish), lang.hitch(this, this.onSearchError));
}else{
delete this.query.orderByFields;
this.queryTask.executeForIds(this.query, lang.hitch(this, this.onSearchIdsFinish), lang.hitch(this, this.onSearchError));
}
}));
} else {
this.queryTask.executeForIds(this.query, lang.hitch(this, this.onSearchIdsFinish), lang.hitch(this, this.onSearchError));
}
},

onSearchFinish: function (featureSet) {
var uVal;

Re: eSearch 2.12 potential issue - Query Layers

RobertScheitlin__GISP — Mon, 21 Oct 2019 12:51:42 GMT

Did you add this to the client/stemapp/widgets or a specific app that you are using (i.e. server/apps/[app#]/widgets?

Re: eSearch 2.12 potential issue - Query Layers

RodWoodfordOld — Mon, 21 Oct 2019 12:54:34 GMT

The specific app in the server directory. I tried a couple to no avail.