Enhanced Search Widget Version 2.23.1 - 11/22/22

Your widget is amazing! I'm a newbie so forgive me in advance. I've downloaded, installed and
configured without issue. But I'm getting an error with one layer, in particular in Specifying parameters for this search dropdown list it only see’s the first item and returns search failed on the remaining items in the list. I have narrowed it down to that it has a domain. If I remove it from the domain, it works. I am using Version 1.1.7 and have exhausted my resources and any help would be appreciated.

Thanks in advance.

RobertScheitlin__GISP · ‎06-09-2015

Joaquin,

Is your service public?

joaquinfernandez · ‎06-09-2015

No, but I can send the file, It only has two polygons.

RobertScheitlin__GISP · ‎06-09-2015

Joaquin,

Before that can you check your browsers web console (hit F12 on keyboard) and if there are any error copy those and post for me?

RobertScheitlin__GISP · ‎06-09-2015

Line Champagne,

There is currently no way to remove the Search Alias drop down from the UI. I will add this as an enhancement request.

joaquinfernandez · ‎06-09-2015

RobertScheitlin__GISP · ‎06-09-2015

Joaquin,

Actually it's the console tab that I need to see.

joaquinfernandez · ‎06-09-2015

It finds Water but not Sewer but if I change the order of the items in the domain. Sewer first then Water, it finds Sewer not Water.

joaquinfernandez · ‎06-09-2015

this is in IE 11, thank you for your time.

RobertScheitlin__GISP · ‎06-09-2015

Joaquin,

OK now all I should need to see is your config_Enhanced Search.json file. This is located in your C:\[install dir]\server\apps\[app num]\configs\eSearch folder

joaquinfernandez · ‎06-09-2015

Robert,

Below is the Enhanced Search.json

"layers": [

{

"name": "ws",

"url": "http://Server/arcgis/rest/services/MyWASD4/MyWASD4/MapServer/0",

"definitionexpression": "",

"spatialsearchlayer": false,

"zoomScale": 10000,

"shareResult": false,

"addToAttrib": false,

"expressions": {

"expression": [

{

"alias": "SERVICETYPE",

"textsearchlabel": "ws",

"values": {

"value": [

{

"fieldObj": {

"name": "SERVICETYPE",

"label": "SERVICETYPE",

"shortType": "string",

"type": "esriFieldTypeString"

},

"valueObj": {

"value": "Sewer"

},

"prompt": "SERVICETYPE is",

"textsearchhint": "Water or Sewer",

"sqltext": "Upper(SERVICETYPE) = Upper('[value]')",

"operation": "stringOperatorIs"

}

]

}

]

},

"titlefield": null,

"fields": {

"all": false,

"field": [

{

"name": "AASISID",

"alias": "AASISID",

"isnumber": true

},

{

"name": "SERVICETYPE",

"alias": "SERVICETYPE"

},

{

"name": "DIVSECTION",

"alias": "DIVISIONSECTION"

},

{

"name": "ASSETTYPE",

"alias": "ASSETTYPE"

},

{

"name": "ASSETSIZE",

"alias": "ASSETSIZE",

"isnumber": true

},

{

"name": "MATERIAL",

"alias": "MATERIAL"

},

{

"name": "STATUS",

"alias": "STATUS"

},

{

"name": "DISCOVERBY",

"alias": "DISCOVEREDDUETO"

},

{

"name": "REPORTEDBY",

"alias": "REPORTEDBY"

},

{

"name": "CRITICAL",

"alias": "CRITICAL",

"isnumber": true

},

{

"name": "PIPEEXPOSED",

"alias": "PipeExposed",

"isnumber": true

},

{

"name": "COMMENTS",

"alias": "COMMENTS"

},

{

"name": "MODBY",

"alias": "MODBY"

},

{

"name": "MODDATE",

"alias": "MODDATE",

"isdate": true

},

{

"name": "CRTBY",

"alias": "CRTBY"

},

{

"name": "CRTDATE",

"alias": "CRTDATE",

"isdate": true

},

{

"name": "EAMWKORDR",

"alias": "EAMWKORDR"

},

{

"name": "ATLAS",

"alias": "ATLAS"

},

{

"name": "SHAPE_Length",

"alias": "SHAPE_Length",

"isnumber": true

},

{

"name": "SHAPE_Area",

"alias": "SHAPE_Area",

"isnumber": true

}

]

},

"links": {

"link": []

},

"showattachments": false,

"layersymbolfrom": "server"

}

],

"initialView": "graphical",

"multipartgraphicsearchchecked": false,

"addpointtolerancechecked": false,

"keepgraphicalsearchenabled": true,

"autozoomtoresults": true,

"toleranceforpointgraphicalselection": 6,

"bufferDefaults": {

"bufferUnits": {

"bufferUnit": [

{

"name": "UNIT_FOOT",

"label": "Feet"

},

{

"name": "UNIT_STATUTE_MILE",

"label": "Miles"

},

{

"name": "UNIT_METER",

"label": "Meter"

}

]

},

"bufferDefaultValue": 5,

"bufferWKID": 102003,

"simplefillsymbol": {

"color": [

1,

185,

253,

128

],

"outline": {

"color": [

1,

185,

253,

204

],

"width": 0.75,

"type": "esriSLS",

"style": "esriSLSSolid"

},

"type": "esriSFS",

"style": "esriSFSSolid"

}

},

"spatialrelationships": {

"spatialrelationship": [

{

"name": "esriSpatialRelContains",

"label": "entirely contained in"

},

{

"name": "esriSpatialRelIntersects",

"label": "intersected by"

},

{

"name": "esriSpatialRelEnvelopeIntersects",

"label": "intersected by envelope of"

}

]

},

"symbols": {

"simplemarkersymbol": null,

"picturemarkersymbol": {

"angle": 0,

"xoffset": 2,

"yoffset": 8,

"type": "esriPMS",

"url": "http://static.arcgis.com/images/Symbols/Basic/RedShinyPin.png",

"imageData": "iVBORw0KGgoAAAANSUhEUgAAADQAAAA0CAYAAADFeBvrAAAABGdBTUEAALGPC/xhBQAAAAlwSFlzAAAOwQAADsEBuJFr7QAAABl0RVh0U29mdHdhcmUAUGFpbnQuTkVUIHYzLjUuMU7nOPkAAAw2SURBVGhD7Vn7b1PnGQY2CORO7nc7N9txbB/HsWM7ji+5XyAh3EIIsHZQKAgKBQa0sBAoN5FSLqNAB0WsdEWjrdhY6QCtg26l7Uopg1JN2kWttv0w7Q8YYqrad8/zxUfK0DbREhwmzdKjc/E5Pu/zPe/7fO93PGbM/z9ffwSe8dpT9gbdxu/Xe6v3BV3a/pCr6Hfzp4z9+r84Snfu8Dq9u2ur+p8Pe87uD1ZfOxT2fHI47Lmxp8711g6/dnAwUNU2SqF9tcfu9GquAa927ofNdXK80ScvN/vlZFOt2r7SEpADIY8MBlyyG9juc1wd8NinfbUnxPBqBNoz4HXcPtVSJ29MjciZKSF5szMiFzrr5WJXvbw1rQH7DXKmIyhHG7xytN4v+4Me2ey27Y5hmPf2qH3Batdyh/nvZ6aEFYlL0xvlg9mt8t6sZnl3ZrNcxjFxqbtBfj4tIhe57W5UBF+IeKnYwXt7UoyuWqNVvHGk3gsCLQi4Xq73tsmHPa3yLghd7WlR21/PbpErIHexKyJvz2iUX85oVqr9AuRQZ7I/VP1YjML974/Z5tMqH7OaPj+P0f54brvcAJlbfe1DhEDiHZB4n8Sg2NvTm5RSOjnuX+xqkNfag7K1xv77s43BhFEntcVjnzenrFjOo1Y+6etQpG5hexNbkvpoTpvC1ahiv4IyVIdq8num5aXuJtnsscu+OlfHqBPa5K7sbyrMlVfbgooQFSJIiCSuAQycqXdtDrdDuNk7pCbT81pPu2zzOaXfY1s76oS2+7RBR0aa7KmrVoSuQY0rGHWSYLC6OtdxnuAxyXD7IdKQ91xFaq7SKmS1Zu4fdULP1bnWV2WmSVNhvnK2j+d2KGd7B2nFWnkP+ABQKkWNgfv87gZIkdCbU8OyuLJMntTMa0ad0Av1nmBPmUHSJsXLUrtZbiHVWEdMNWXXsOfL00mwSdk5TYA1Q6JDNdcmT9hNMge/sbnGNnXUCTGA9VXWy+G8bEmJi5OFtnL5CKnGYG8iWKpxZWaLIkUzoOtRHZWePW2y1atJVWY60+0v33VXJj8UhNCneZfZym93GgskIz5eWg35crzBp1KPgRN0Pn2f21OtAZlWYpDilFR5xFIiMJcVDwUZPYhnA85Fy5A6M0uKxDI5RbIS4sWflaGC3erT5HC4RlBv8pSrUrqLCyU9IUFMuO7RihIYgukHDw2Z443ehCMRz8yj9TVntnrtsgTF3WcySochT1oKsiWUmyEumEZNZoaYU1OlJCVZ3FnpMq/cIEttZUD5wSccpnEPBaHDYfe3MOq3jmD0D0c8qAe7PO2yyvqqCllmL5cVwPaaoXOPV5bKKij4pGaRDa4K2ea130HH3fxQEMFCbcKeQNUJrG/kR21cKvixLKjCbF+pgl/lMCuQ2IC7UraBVD+2KHrBkgGwyU6/9jkGYfTr5kxH3fgdPueFTW67WuOcRh92IORW6jDgpzD6cCxZ6yQhC5VQpPgd+jUZoGLVVtld68SayCno1F852eybOGpKPReoOrbCYZFDYS/anRCC0mQH8BSUYdBUaC0IPQ1iGxH4DhDaWmNTJJBigmU51LKh1XEIluayw69InRoVQodDnnnrqqyyEm3K6+0heRYrTyqzEUQwy8sWjP4mBL7GYVKk+t1WGUTgOwE93XgNiQ54HBgUDxZ6PtXHwVzWxZQUX24843W8v7CiTLb7XXIRaxmsg4aMAAE+DnejStxn7ej1syfgVLXF7zDXqO/hamoQuA462VwreJHC9LtzbmqoMGak4GhmBHVnRplRTjQF5AKW1TNKi2QdCx+j3gsbZj+2AcfKAKgCFarVsMweSkVeRzJzYevrcMz3C0y7FzEJb8D8BPvfHDNCg7XOWUyrrhIj3guE1EozkJspM0GKoz69pFA6iwuUXZMM020XUm0v3I/GsM3rUCp145peEOL+Fpxnyr2G9F3tRL35nZdjRmiX37mck2a7oUBOw6q5fPZmZ4g1fTIm0XxVM49YiqFaoayACnS7vUi350MupJwN3YBZkebaiQNDQphUqQreDPllCfbXVlX8LaaEFllLVfB7kfuvw647jfmSOWmSFCcnSQTNKdMJPZ3wuoVoabi/RhEtUerxHM1hf9ClvmMLdKLRKy/jTdECSynuN8eOEAxh9jykSiQ/W02aJ/GubSPSyox+LDt+kqSDmCE5UWpyMqS7pED2+m1yMuJSJKksVVmJ+3g831wswbwstEgGWH+d7Kp1RQmZPo2ZQoN+pwZCX9qQYkybzSjwY3i/xvQqTkmUtIlxkj5xolLMCMWWmAtlu9si86BOq6FQ/Lk56OkyxIH7rWmTpSItFQ2rW87i1dd8S5nMKTciBU2/jRkhPgjK/IaNphnBtCH1OKm+1ESHsqoGlGQyoVY+OmmiLCVFPNmZYstIF2NKEogmgnyS6sZZa3wpucFll/rCPKXaYmvpzZgSOhR2L2ENlacmS1FSEkwhE6tUE9xJk+VQiq7HoFXgUKkwkfvY4pjgeVNaitSjC19oLYM72lGTBdJSlIv6KuXcdDqmhDC5jkOnfN6HJQHVmIw047YMS4JAbhYCyxOuXKuxPGBqOfHyhGnmwoqU8KO+AjmZUpuTJR3GQumCKTRDHdYma+tnnZGYdd/6XyBj+ZfIWqflM74YSQEhLrsTx08A4iQHq1Wqx3WPDXVCQh4s8jRseUxYoBAXdm4QqwGxZqjTi/cJB4LVL8VKHZIhuAj7BvDNXbWaZbVmuRlB6mSDBEmlRpEGY5gcNYf0iagp1pVCPOorAWmXrGqrAuSCUJMvR3b7nZfOd0aSYkHoX4jggRMAtvrxbYaCfEyOLy5AMddkp0s2ltz5ifGw74mSOCFOkkCqGMFboo7GlWoB6qkYZCwwlfqCHDUvDQacr/5kSjD1QZLRFeFWKQLEAZOARIBvZiYDGUDWtytKejHHXFgIe+7CRNtlyJG+0jzpxjaEucaPtLJloI6yMiWAY5rKQmsJ57A/YgmxNKq8/swHwmu4KuOjipBICpAOZAN5QBFQApQB5Z7MtHZMlAexDrp9LFwth+ucX/RXW2+vtJu+YOew3G76x4Db9meo+lNgSXNhTlZUcQ4YB+6B/FV5NxmqwtxOixIpwLaYBAArYAecgAuoBlpNpso/hBuaPp09u+/HVrO1y+fz9T3at6CvZ0ZPZ1FREe/JjQ4MlY4HqD4H7oGQ0gtfV4ZkqAqDMAImwAZUATWAH6gDQkAYo7Hd5/VJoDYgVpN1IPo9ryNhkrcAVDUfyARSAf6FQlJUis8fMaV0dYanGZXRyTAYZ5QISdQDTUArwD+B28eNHXcuMSFJCvINX8bHxS/GucbodbzeGx0IqlQKUG2S0pWi4VClESE1PNX4w0wFjh7rhbVCZbRoUFSDREiC76K7AP752zt2zNjPkhKTRNO0v0bP8/t2gBNmBKgFqBZJUSnWIgeNNaqn3ogS0h2ND+CD+ECOZiXgBoJRMgyyE+gGZgCzgAXAn5KTksVms1/H/kxgepTYFGxboqR82DoBDhIHi+Zwt0r3nXa6RQ+vHdoy04IG4ABYC1SHgTFAqqKTmY39HmAT8D1gPcBzw0lxEJiCTD8aSAVgBHIATgOsJT3t7svG9ZuZvyREZ+OIMb//EyH+dchUowIMmsET34mSmXMPhJh2dEzWqE5oxMxBV4gjpBOiQnQjphydjSkXABoAGgFVIqnuKDGqtRxYFCXJY37Ha3gt76GR0Bnpkv9OoREnNDzlWENMByNAh6MpeADd4VjoNAaqxeJnTVEZKkYSPCYRphrTlGQ4IPwNWjhTma+tWEOctGlEI5pydBfdFJjPqQDTjirRkTiiOim6FQ0iArAu6HoMmqASBPd5nkRYe7yHKrMeOUBGgOnGgeN8x8wYkQlWryGdkJ52fAhzmyOodwhm7OsTK4Pj3MJAqRoJEgye4D4VoatRFaYZ76W7sXbooExrXZ0RTbfhxqCrxBQYTooBGADWFInprQ9VY7B6+0OidDEe8zwVoe3zHt5Lq9bJpGKfUwQ7+OHqjIht393HccR0UnwwR5MTLVOQQXGUGSBrgcEyjZiWOnhMNdi88lqdCH+D7RSV0ckwK4a3PvdNCL+neiidFH+cIzZ82cAAmO86MeY/yTEdWdwMmAoS3Cd4nmrQXJi6JJIKUHkOlq7MiJMhof/Jzz8BTd1Yt7q/vtYAAAAASUVORK5CYII=",

"contentType": "image/png",

"width": 20.00025,

"height": 20.00025

},

"simplelinesymbol": {

"color": [

75,

172,

198,

255

],

"width": 6.75,

"type": "esriSLS",

"style": "esriSLSSolid"

},

"simplefillsymbol": {

"color": [

79,

129,

189,

255

],

"outline": {

"color": [

54,

93,

141,

255

],

"width": 1.5,

"type": "esriSLS",

"style": "esriSLSSolid"

},

"type": "esriSFS",

"style": "esriSFSSolid"

}

RobertScheitlin__GISP · ‎06-09-2015

Joaquin,

OK, it is not the issue I though it was going to be. Please start a new discussion new Discussion thread that way you can attach the layer data. Give me any details you can about the field domain and values so that I can try and duplicate your environment. Like that type of Geodatabase are you using (file geodatbase, SDE SQL server, oracle, etc).

joaquinfernandez · ‎06-09-2015

Robert,

As requested started a new thread. see link.

https://community.esri.com/message/526464#526464

thanks.

GerardoGarza · ‎06-10-2015

Hi Robert,

Thanks for the tool.

I think I found the bug that was causing the AttributeTable tool to generate the following errors:

Chrome -- TypeError: Cannot read property 'addChild' of null

Firefox -- TypeError: this.tabContainer is null (this.tabContainer.addChild(cp))

The eSearch._openResultInAttributeTable() method was calling the AttributeTable._openTable method before the data was published and then the AttributeTable.onReceiveData method was calling _openTable again after the data was received.

I submit my solution for your review. In Widget.js of the eSearch 1.1.8 tool I commented out lines 1549-1554 to remove the following lines from the _openResultInAttributeTable method

if(this.wManager) {

var attWidget = this.wManager.getWidgetsByName('AttributeTable');

if(attWidget[0]){

attWidget[0]._openTable();

}

Gerardo

RobertScheitlin__GISP · ‎06-10-2015

Gerardo,

Thanks but I find that if the table is not open before the publish data then once you clear the results the attribute table will not open with any results for the second search and it give this error:

TypeError: layerInfo is undefined

Stack trace:

mo.getConfigInfoFromLayerInfo@http://gislap183:3344/webappbuilder/apps/3/widgets/AttributeTable/utils.js:126:5

AndrewNiederhauser1 · ‎06-11-2015

Hi Robert,

I am using version 1.1.8 and am getting mixed results when performing a search and having the Search Results populate in the Attribute Table.

Sometimes the Attribute Table widget will get populated with results and other times the Attribute Table will just be blank. I've tested this on IE, FF, and Chrome as well as had other staff test on their machines with the same app. We are all experiencing the same mixed results.

I can get the Search Results to successfully populate the Attribute Table each time IF I first open the Attribute Table widget THEN execute the search.

The app is secured but, if possible, I could send you a link and credentials.

Thanks,

Andrew

RobertScheitlin__GISP · ‎06-11-2015

Andrew,

If you look at the web console the error is occurring in the Attribute Table widget and that is outside of my control. The work around that I have found is that when the Attribute Table widget opens but is empty you just need to right click on the layer in the LayerList widget and choose open in attribute table and then it will be fine for each search from that point on. At some point I will discuss this issue with the WAB Dev team and see if we can get some resolution to this.

AndrewNiederhauser1 · ‎06-11-2015

Thanks Robert, we'll adjust the workflow.

AndrewNiederhauser1 · ‎06-12-2015

Is there a way to change the name of the Search Results layer in the print output legend? For example, in the attached image, the legend item in the print output is "graphicsLayer3". Users might find it more helpful if the layer were named something like "Search Results - Layer Name". Should this question be posted outside of the eSearch widget thread?

Thanks,

Andrew

RobertScheitlin__GISP · ‎06-12-2015

Andrew,

This is one of those strange things that the JS API does. I add all the searches to the map in the same fashion but some layers print like yours with graphicsLayerXX and some print just fine like this one

I guess I will have to get with tech support and see if I can get this one figured out.

JohnHainsworth1 · ‎06-15-2015

Hi Robert,

In the attribute search, is there a way to "Limit results to maps extent" by default? It doesn't matter if it is accomplished with a checkbox or not. I am trying to streamline the interface for end-users and would like the widget to always limit the results to map extent.

Working with other widgets I have been able to change the default check box settings from 'false' to true', but in your eSearch app it is not as obvious to find.

Thank you for all of the great work on these widgets,

John

RebeccaStrauch__GISP · ‎06-15-2015

this is for attribute tables, but may be related. Can attribute table results be limited to map extent by default?

Some me other tips are also included in this/my blog post Tips (LocalLayer widgets) for more customization and Updating (may help with others too)

JohnHainsworth1 · ‎06-15-2015

Thanks Rebecca, that information got me thinking in a different direction and I figured it out. It wasn't a matter of changing 'false' to 'true' because the 'limitMapExtentCbx' was not called out. I added a new line to control that checkbox on start up, and it seems to be working.

The new line was added in widget.js line 355: this.limitMapExtentCbx.setValue(true);

RebeccaStrauch__GISP · ‎06-15-2015

Glad to hear you got it working John. Sometimes all you need is a push past your current thinking. At least that seems to help me (that is, soon as I write it down and press send.....)

TimJacobsen · ‎06-23-2015

Gerardo,

I think I have the same issue as you, chrome was throwing 'addChild' of null errors and the attribute table would never get populated. Commenting out the lines you mentioned initially works, the first search the esearch and attribute table are really fast. The get and content download are way under a second. After the initial search it slows to about 12 seconds for the get and download esearch content, and 25 seconds to get and download content for the attribute table. That may be due to the record count of our service, using the find command at the rest endpoint of the service it takes 12 seconds to return a find. Oddly it looks like the attribute table content is downloaded twice. Did you experience similar behavior, and were you able to refine a solution?

GerardoGarza · ‎06-24-2015

Tim,

The searches are consistent now for me by commenting out those lines. I do not get the same lag you are getting nor do I get multiple attribute table calls. The data to the attribute table should be sent once and can be checked by setting a breakpoint in the Attribute Table code. For 1000 records, the attribute table populates fairly quickly after the eSearch content. How many records are you pulling for display? Are you using version 1.1 of the WAB? Are you watching network traffic with Chrome tools or Fiddler? I will be modifying my service to have more records so may have different results with a larger dataset. Now as a side note, I was having problems with proxy.js that was causing my searches to hang and cause timeout issues (Problems hitting REST services when running App on Node.js server ). I have not yet tested the suggestions for modifying the proxy timeout so cannot report anything else.

paulgarcia · ‎06-24-2015

Thanks for this great widget!

I've implemented eSearch to search on our parcel layer which has quite a large number of attribute fields. I've easily configured a link to our assessor parcel maps, but the link shows at the bottom of a very long list of attributes.

Is there an easy way to have that link show up at the top of the attribute list and not at the bottom of Results?

thanks!

Anonymous User · ‎06-24-2015

Hi Paul, yes. You can adjust the order of each attribute with the Up and Down buttons. Plus, you can decide for each attribute whether you want it in the list on the right or not. Check off Popup Only to take it out. He just added that recently and it was a lifesaver for me because I had a ton of attribs for each record, probably like yourself, and it made the list on the right not useful. I went through and removed everything but a pink and a name and address for our properties and now it's perfect! Give it a shot, let us know if that works!

paulgarcia · ‎06-25-2015

Thanks for the reply Kevin. What I'm really hoping to do is avoid having our users scrolling thru a long list of attributes to get to the linked parcel map. I can see in the eSearch setup dialogs that the attribute list can be re-ordered, but the widget seems to handle the Search Links as a separate code block in the config json file. My parcel map link is not part of the attribute list.

In the image, you can see that I've scrolled all the way to the bottom of the attribute list, and the Parcel Map link at the bottom.

RobertScheitlin__GISP · ‎06-25-2015

Paul,

So what Kevin is suggesting is that you not have all though attributes present in the widgets search results (by choosing popup only). You can just choose a couple of main attributes to display in the search results and then the link. I do this for my main site just listing owner name, Parcel ID, Parcel Number, and address. The rest of the attributes will still be available just in the attribute table or the popup instead.

Currently there is no configuration to allow the link to appear at the top of the results.

paulgarcia · ‎06-25-2015

I see!

I'm going to give that a go.

Again, thanks for the widget development work and thanks Kevin for the quick and helpful reply!

TimJacobsen · ‎06-25-2015

I’m usually pulling one record at a time and combing thru chrome tools to find errors. The lagging behavior is same when it is pulling hundreds of records however. After trial and error I realize the search/zoom/open attribute table is very fast when it is not returning “Uncaught TypeError: Cannot read property 'geometry' of undefined”. I don’t have a good feel as to why this error occurs. Using the default attribute search “(Parcel Number (APN)” on http://betamaps.mcassessor.maricopa.gov/ and search a string such as 20140001 should reveal this behavior. Sometimes I get the error, other times I don’t.

DAVIDDAS1 · ‎06-28-2015

Hi Robert,

Is there a discussion thread on GeoNet with links to download all your custom widgets that you developed for the last and final version of the FlexViewer 3.7 based on the ArcGIS API 3.7 for Flex?

I know of the following 21 Custom Widgets that you released for FlexViewer 3.7.

I could be missing some.

1.

Aloha Threat Zone Widget 3.7

http://www.arcgis.com/home/item.html?id=06e2c33649c34c478a15dace967d0cdd

2.

Copyright Widget 3.7

http://www.arcgis.com/home/item.html?id=3893f396489344aa9f8fcdef15b3fe1b

3.

Dynamic Legend Widget 3.7

http://www.arcgis.com/home/item.html?id=f60406b9f52340d59eb557bf64136af6

4.

Enhanced Bookmark Widget 3.7

http://www.arcgis.com/home/item.html?id=720f032374c448189f48e71195e39c22

5.

Enhanced Draw Widget 3.7

http://www.arcgis.com/home/item.html?id=91a0014160fc4a9caadc2c7fd7089c1b

6.

Enhanced Layer List Widget 3.7

http://www.arcgis.com/home/item.html?id=58d9bb5693c94918a3934781d7234d18

7.

Enhanced Locate Widget 3.7

http://www.arcgis.com/home/item.html?id=e147c73451bb4c93b1cf150f4f316775

8.

Enhanced Map Switcher Widget 3.7

http://www.arcgis.com/home/item.html?id=7156b0acf6574f848ddfd3d7e155746b

9.

Enhanced Search Widget 3.7.4

http://www.arcgis.com/home/item.html?id=5d4995ccdb99429185dfd8d8fb2a513e

10.

Enhanced Splash Widget 3.7

http://www.arcgis.com/home/item.html?id=8492794bf5bf4358bca6cce29db31b14

11.

Enhanced Time Slider Widget 3.7

http://www.arcgis.com/home/item.html?id=24824e4bf3d446578e0ceefc241d393b

12.

Export Map Widget 3.7

http://www.arcgis.com/home/item.html?id=12430e982e534fdabe15635828405e45

13.

Feature Layer Tips 3.7

http://www.arcgis.com/home/item.html?id=ce63f1bdd5e64068b9a4fadd2028e379

14.

Google Street View Widget 3.7

http://www.arcgis.com/home/item.html?id=b4259b1cf73e4fa3b04e7bdf75fee29b

15.

Identify Widget 3.7

http://www.arcgis.com/home/item.html?id=39cf66d58c234279ba728c50461a1a89

16.

Link List Widget 3.7

http://www.arcgis.com/home/item.html?id=df56092010f043589b6847b3f9cf0947

17.

Link Widget 3.7

http://www.arcgis.com/home/item.html?id=5e4717fe1bb247f89b9092308e569c30

18.

Point Buffer Widget 3.7

http://www.arcgis.com/home/item.html?id=a950162cd17a4acc985132d40adfe38f

19.

Route Widget 3.7

http://www.arcgis.com/home/item.html?id=992b1f691f44489aa4dcbafe2db66700

20.

Shapefiles Widget 3.7.1

http://www.arcgis.com/home/item.html?id=2e9096c5d5044d39a264df759611686f

21.

Swipe Spotlight Widget 3.7

http://www.arcgis.com/home/item.html?id=b9767b3f300142488c798953a94906fc

This is an extraordinary amount of time and effort you have put in over the last decade to make the Flex platform the Gold Standard of Web Mapping!

Over the next few years as users migrate to the JavaScript API, we hope to see more of your Flex Widgets translated to the Web AppBuilder.

You deserve a Lifetime Achievement Award in GIS for the sheer amount of code you have shared along with all the helpful tips and 24/7 support to our GIS Community.

Tapas

RobertScheitlin__GISP · ‎06-29-2015

Tapas,

Thanks for the kind words. Your list was only missing one (for 3.7). I have 4 others that were retired before version 3.7 for different reasons. My plan is to migrate most (some just don't make sense to migrate as the functionality exists in WAB already).

Basemap Fader-Enhanced Map Switcher 3.7

http://www.arcgis.com/home/item.html?id=7156b0acf6574f848ddfd3d7e155746b

DAVIDDAS1 · ‎06-29-2015

Robert,

Thanks for the reassurance that you will be porting most of your Flex Widgets to the Web AppBuilder to give it the same level of functionality.

We are grateful that you are working round the clock on this massive task!

CarlosPiccirillo · ‎06-30-2015

Hi Robert,

Thanks for the great tool! I am having a printing problem with the enhanced search widget. The search functionality works fine and I currently have it set to "Add Result as Operational Layer." I am searching against a point layer. Everything looks great until I use the out of the box print tool. When I do a print, the point symbols come out huge. Changing the symbol or its size has no effect. I have also tried changing all of the Advanced settings, map scale, extent, etc. with no luck.

I am using Widget Version 1.1.6 and Web AppBuilder 1.1.

Do you have any idea what the problem might be?

The first image is how it looks on the screen.

This is what the printout looks like.

Thanks!
Carlos

RobertScheitlin__GISP · ‎06-30-2015

Carlos,

I have not seen that before or have I had anyone else report the issue. I will have to look into this.

CarlosPiccirillo · ‎06-30-2015

Robert,

Thank you! If I can help you debug/test things please don’t hesitate to contact me.

Carlos

CarlosPiccirillo · ‎06-30-2015

Robert,

Thank you! If I can help you debug/test things please don’t hesitate to contact me.

Carlos

DAVIDDAS1 · ‎06-30-2015

Hi Robert,

I found a minor usability issue with your Enhanced Search Widget version 1.1.8

I am using this example web app to explain this issue:

http://www.tapasdas.com/Maps/Phones/app26/

Open the Enhanced Search Widget

Open the Layer List

Close the Enhanced Search Widget without selecting a layer.

The Layer List remains open, even though the Enhanced Search Widget is now closed.

To make this orphaned Layer List go away, you would have to click anywhere on the map.

Your Identify Widget 1.1.2 exhibits the same behavior.

Open the Identify Widget

Open the Layer List

Close the Identify Widget without selecting a layer.

The Layer List remains open, even though the Identify Widget is now closed.

To make this orphaned Layer List go away, you would have to click anywhere on the map.

Thanks,

Tapas

RobertScheitlin__GISP · ‎07-01-2015

Tapas,

Thanks for reporting this I will look into it and get this fixed for the next release.

CarlosPiccirillo · ‎07-01-2015

Thanks Robert, I REALLY appreciate it!

RobertScheitlin__GISP · ‎07-01-2015

Carlos,

Can I see your config_Enhanced Search.json?

CarlosPiccirillo · ‎07-01-2015

Robert,

Here is the eSearch widget config.json

{

"layers": [

{

"name": "Monitoring Stations",

"existObjectId": true,

"url": "https://mapstest.sfwmd.gov/map_ssl/rest/services/Monitoring/Stations_FS/FeatureServer/18",

"spatialsearchlayer": false,

"zoomScale": 10000,

"shareResult": false,

"addToAttrib": false,

"expressions": {

"expression": [

{

"alias": "Site Name",

"textsearchlabel": "Search by Site or Station",

"values": {

"value": [

{

"fieldObj": {

"name": "SITE",

"label": "SITE",

"shortType": "string",

"type": "esriFieldTypeString"

},

"valueObj": {

"value": ""

},

"prompt": "Sites or Stations",

"textsearchhint": "Example: BC102TN1, S356, BF1",

"sqltext": "UPPER(SITE) = '[value]' OR UPPER(STATION) = '[value]'",

"operation": "stringOperatorIs"

}

]

}

]

},

"titlefield": "SITE",

"fields": {

"all": true,

"field": [

{

"name": "SITE",

"alias": "SITE"

},

{

"name": "STATION_DESC",

"alias": "STATION_DESC"

},

{

"name": "STATION",

"alias": "STATION"

}

]

},

"showattachments": false,

"layersymbolfrom": "config"

}

],

"initialView": "text",

"multipartgraphicsearchchecked": false,

"addpointtolerancechecked": false,

"keepgraphicalsearchenabled": true,

"autozoomtoresults": true,

"toleranceforpointgraphicalselection": 6,

"bufferDefaults": {

"bufferUnits": {

"bufferUnit": [

{

"name": "UNIT_FOOT",

"label": "Feet"

}, {

"name": "UNIT_STATUTE_MILE",

"label": "Miles"

}, {

"name": "UNIT_METER",

"label": "Meter"

}

]

},

"bufferDefaultValue": 5,

"bufferWKID": 102003,

"simplefillsymbol": {

"color": [

1,

185,

253,

128

],

"outline": {

"color": [

1,

185,

253,

204

],

"width": 1,

"type": "esriSLS",

"style": "esriSLSSolid"

},

"type": "esriSFS",

"style": "esriSFSSolid"

}

},

"spatialrelationships":{

"spatialrelationship":[

{

"name":"esriSpatialRelContains",

"label":"entirely contained in"

},{

"name":"esriSpatialRelIntersects",

"label":"intersected by"

},{

"name":"esriSpatialRelEnvelopeIntersects",

"label":"intersected by envelope of"

}

]

},

"graphicalsearchoptions":{

"enablepolyselect": true,

"enablefreehandpolyselect": true

},

"symbols": {

"simplemarkersymbol": null,

"picturemarkersymbol": {

"url": "/widgets/eSearch/images/i_search.png",

"height": "20",

"width": "20",

"type": "esriPMS",

"angle": "0"

},

"simplelinesymbol": {

"type": "esriSLS",

"style": "esriSLSSolid",

"color": [

255,

0,

204

],

"width": 2

},

"simplefillsymbol": {

"color": [

255,

0,

128

],

"outline": {

"color": [

255,

0,

204

],

"width": 2,

"type": "esriSLS",

"style": "esriSLSSolid"

},

"type": "esriSFS",

"style": "esriSFSSolid"

}

RobertScheitlin__GISP · ‎07-01-2015

Carlos,

Any reason you are not using 1.1.8 instead of 1.1.6?
The config you provided does not have the yellow doughnut symbol for your search results, so I can not duplicate your issue so far.

Edit:

I did grab the yellow doughnut from Tapas's site json as shown below:

"picturemarkersymbol": {

"angle": 0,

"xoffset": 0,

"yoffset": 0,

"type": "esriPMS",

"url": "http://static.arcgis.com/images/Symbols/Cartographic/esriCartographyMarker_77_Yellow.png",

"imageData": "iVBORw0KGgoAAAANSUhEUgAAAEAAAABACAYAAACqaXHeAAAABGdBTUEAAYagMeiWXwAAAAlwSFlzAAAOwwAADsMBx2+oZAAAABl0RVh0U29mdHdhcmUAUGFpbnQuTkVUIHYzLjUuNUmK/OAAAAZrSURBVHhe7ZsNiJRFGMetRZdc8sILLzQ86pJLLrnMTEtL66qLjjrqoIOCDgoMDIyKkoqSPqioyMhISEhIMCoqSiokREQkpMIioqLgCAkJiUMiIg52mt8wcwzbu7vv+8zMscs2MLx47s7M83++//PunDn/j+QIdOsdJvTcpucOPQ/aeVI/lZ3ub2/bz23Vz4HkJ0u4Qb9e+0E9D3tCOmGLPCctaEMJzxp1aTT9sy90qXRadWx0iXrikeXqzZ2XqgOfXmXmH8dvVtOnxsw8tH+j+dsnH6w3n9u8qU8tWXxGLVBTet0X9eyKeuJIi6GhL53gXV1z1e3jS9U7e9aqv07eMiOoEzjv8+sjQ+qBLctU3/kVHwyAwLpKkc4etEyf/vY+J3jPorJ647VLxAI3AubooWvUurXdPhC4x1jQ6QO/jLlPIzwaf+rxgSBt57WKj969QvUvO9MH4kN9hnKgLIW/TkQ3h8Bff5+8KYnWG4Hy+isrVdeCuVV7ji/0k2yTfID0HjYluL21a/WsC+6D8v1X16vepfOdNRB8cclkg+hr0hrIE7Xzmm3Kz2F9q1ae5UCgtliTAgE0b4QH8W+PXtcSwjtgT50YVaMjix0If+pzRi+idiI86ei3X0ZaSnjfuu68o9d3h2j1AtFeVSqlaqtpvta1qDnWrF7oQPgshisM6kX+BgCKmpS+HGvtX3+8Uel6xGWH50JAIK0cR/iH7+9vC+H90posZVOkuFjazgLD1/a0lfAOBOoEC8AJ/SxcKPVg+qD40zfD0QFgTdcU8Txy4OroewDE4IouB8J9RV3BRH2iaizfpOPbdNd5+GfddphURscY0kD5531/7+UiK6Camo6lfbSNG1lzdM8f9L8P1kzTV7hag5o/BvgSK9gdS/tos1w+3QUj2tin9YQsyRrk7bv1POaAoKX+Z+rWICCKWkEllvZffeliX+v0D0WaFfp9AFNDGxcpKr0Qa/CsYLxZLBhlU/rukA3hBDyTv6fZpnX+nxqECK42rD87yBJeeGaFOw+cY8Nhgt+zT14kBgAWpzxvxuzFOdieslc/g2sRukarEABtOAhO4rSEqXr0VVAV5p1yHW7JueAMpZbpZZ+63SLR36Qp6SYQmhZpCIqYnN1jrIsvS89GCrZnY63Mga+q28bOFW0Cy+sxNBuamVrB/6eSM/GAqC4BYe/uy3zlZG6PyaqXnx8UbeCVnuT3FINqzgRECQA0Sc3igMn/ICXZYOSGc9wGEymk12uSRk2BJkmLVJcWAOJJ5qB/Vvs/vrIwABQr8AV2A/qIVIPYIm7N9RkdCBRd/xnmYkNCenhpBmIy5TBu+uhDFxZWElbtZahM8tQEGQnlRUdntf95Sun12veyDxFd4qYeW5SZCk2uldTeXoSl5E05KKwUd40SALw4NZJ1SDEA3A9YC2hrAMQuQIVmAYhCRDYwIVOrpHIBcRDk4tIC8F1K+9dr004nC4LiNEhetiQkbkRLnWqYM0qv5Lw0mNmaBxVCXoQdTiQ9vQW3PqJMlacQCiqFoc6tGwBkijHE+lyNSzJAnlI4qBmC+/PcIMUtLT2GuFfJ0wwFt8Pe3VzsdEjeNt2mpA/AYvK0w5htECGCFURkg5wb0VuYV+p4C0Vi/nwnDyHChsGUmNcWc+h6DHDeGAEPQHlteEpJlYrwNZRYQ6ImCikKnW0DIiCsyittzedIp0b47oXzqgQxqfaLkKJRaHE05YFA6oLmLkKRwSgdQ3heyECDUuFrrsjG8yjD1AMxrsW2bL7Ap8cn9bqwOjC9WQNz54D7rPWogeULVIjmEb7oxQgHi3o1RquMIE4o+0S7pDV/miKHWZlfqmK2Up/3rUVyNQYIu2JZAYdBEMpXCFevHK0FxQQ6OEkJJ5HlIhLtO9Mk9SS7Hsen/etxbo5DfLzed6XadyBsxwo69QUJQKBjCr6WSqHZZmtiUTFekQGEQVwBS+jEl6ScK3Bn37GvyTkQTIncqS9KAgJFymFA6NRXZQGB2xQDQgu/LD2lz1f3+tuZc8gTS6DX78jX5X3gtgECs0V+MAGjnUl0hmi72Xcn9Ac69iczDhwap5nubZZ/NEWRxlVZSwwYW9O/myDZQT+bq0Uft+CKfKbTS/DDyVn3dYmJwQXCApm0GTAhUXboiYW17UBjWAaZA2EcCWKYXjvd396zn9uqn9F/99O2CKY8+L9SiYnS6UxmCQAAAABJRU5ErkJggg==",

"contentType": "image/png",

"width": 20.00025,

"height": 20.00025

},

But Even using that I can not get the results you posted when printing with the otb print widget.

CarlosPiccirillo · ‎07-01-2015

Robert,

I’ve only been working with Web AppBuilder for two months. I’ve been programming since 1991 (Arc/Info aml, ArcView Avenue, VBA and C#) but Web AppBuilder and Javascript is a whole new world so I have a BIG learning curve ahead of me.

The only reason I am using the older version is because that is what I started with and didn’t realize there was a newer version. I will update the widget, try again and let you know what happens.

I was using the same symbol as Tapas, marker 77 yellow but from my tests, the symbol does not matter, I tried four different symbols and had the same issue. As far as I can tell, the issue is limited to just points, Lines and polygons display correctly on the printout.

Carlos

RobertScheitlin__GISP · ‎07-01-2015

Carlos,

This is strange as here is a pdf output that uses the same symbol as Tapas for points and there is not issue.

http://gis.calhouncounty.org/WAB/V1.1.1/_ags_9400a43fe8174b31804605fb9c822f59.pdf

CarlosPiccirillo · ‎07-01-2015

Robert,

Do you know if Tapas’ output matches what he sees on the screen? The symbols look pretty big to me on his pdf, granted not as big as they are on mine. Maybe Tapas was zoomed out more than I was. I was zoomed in pretty close.

CarlosPiccirillo · ‎07-01-2015

Robert,

Updated the widget to 1.1.8 and changed the symbol as well but the problem still persists.

Here’s screen capture after search.

Here’s printed pdf.

RobertScheitlin__GISP · ‎07-01-2015

Carlos,

Please start a new thread on this issue so that you can attach things (comments on the document do not allow for attachments or the use of the advanced editor).

Start a new thread link

Enhanced Search Widget Version 2.23.1 - 11/22/22

Enhanced Search Widget Version 2.23.1 - 11/22/22

Widget Downloads