Latest Contributions by RodWoodfordOld

Thanks Robert, That works well when setting the "between date field" option, but does not work for other date setting options. Can you please investigate. Also I can setup a test app re the resetting of unique values after every "clear field" click. Would that be ok? cheers ... View more

I agree, but I'm not holding my breath now that ESRI are focusing on Experience builder. Hopefully a widget can be built for WABD!! ... View more

Thanks Robert, I have resolved the date issue. Thank you for your fix re query layers. Can you advice when this fix is included in your next release. cheers ... View more

Thanks I'll try that and get back to you. cheers ... View more

Yep I can set that up. Can you tell me what you changed in the code? I cant see a difference between what you posted and the original. ... View more

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

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; ... View more

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 ... View more

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

Sorry for the delay. See below to test. Works at 2.6 without issue. Layer: PropertyWard (ID: 0)  ... View more

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 ... View more

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 ... View more

Thanks Robert, I'll do some more testing tomorrow and get back to you. cheers ... View more