Thanks Robert, yes if I am understanding this correctly:
if a layer has field(s) visibility configured as 'false' in the AT AND that layer participates in the eSearch, the eSearch will override any 'false' setting and make those fields visible by default when a user displays the layers' attributes in the AT. When the eSearch opens the AT with a result, the visible fields are those configured as true in the eSearch.
It's ok, I just could not figure out why no matter how I set AT fields visibility, all fields would continue to display for layers that also participate in eSearch. And of course now I can compensate when needed-
Just to be sure. Are you saying that you have a layer added to your web map and have configured it in the AT widget by hiding some fields and you also use this layer in the eSearch and the AT widget is not maintaining the field visibility for the non-eSearch version (eSearch search results creates it own layer to add to the map and the AT Widget) of this layer?
Robert Scheitlin, GISP, I am wondering if there is anyway to set the default for the calendar part of the widget when searching against dates?
I have a department that wants the start date, on specific layers to be pre-set. So when I select the layer titled (Current Month Crimes) the calendar should be pre-set to default to that months 1st. Is this an option?
How difficult would it be to add in a variable 'Default Calendar to Today's Date' and then check against it in SingleParameter.js and set to TODAY if yes and leave as it if no?
Are you against me checking out your GIT and pushing an update like that through?
Yep it looks like the current version requires the exprnum parameters also. I am not sure why this changed but I will make it optional in the next release.
Thanks for the feedback. I will work on those CSS issues for the next release. This fix will address the white title in launchpad theme for both Identify and eSearch:
The fix is add this css rule to the Identify widgets style.css file:
Hi Robert - I'm sure I've overlooked something simple, but since I added this update the results info window popup is not displaying results - i.e. its blank. I just updated eSearch in my stemapp, saved my configs, removed and added the new build to my apps and replaced the configs. Am I missing something?
Maybe a bug? I checked to add the results as an operational layer and the results popup info window now populates, but does not populate when I do not add the result as an operational layer . . .
1.) In the result InfoWindow popup the Fieldname is also "Wrapping" to the next line along with the record information.
If you do not want this then turn off "Wrap result text"
2.) How do you remove a field from displaying in the attribute table but still display that field in the Popup window?
That is not possible
3.) What is the proper configuration to select a unique value from a date field? I get a string of numbers in results, no date.
That is not an option. It looks like your date field is not an actual date field type, but a string. If you use the widgets settings UI you will see that things that are not allowed in the widget are disabled so there is no need to work with the json directly because if the settings UI does not allow it then the widget does not support it.
I am only wondering why my search results are not highlighted in the color I specified (red). In the help document it says "if the map service to not return this information" so I wonder if that could be the case. But where would that be specified then?
The widget has three symbology options. It sounds like you have your set to something other than "from layer" (assuming you specified the red by clicking the "Add\Edit Layer Specific Symbology" link). If you set the symbology defaults to red then you need to choose "from default"
Can I somehow use the customized popup from my web map to be shown with the search results? I have seen in another discussion that there are problems with using the web map defined popups with search results. I was hoping that eSearch would solve this. But it seems like I can only say no popup to show from the results list or I get the popup as defined by the widget.
Alternatively: Can I change the result popup somehow the way I did in my web map? For example using a tabulator between Attribute name and value to make the attributes easier to read? Or to define to show the data in a table? In which file would I define this?
Added: I don't want the link that I defined for the popup to show in the results list! In which file is that configured, please?
And another question: Where could I possibly tell the widget to clear the selection when closing the eSearch Widget? I found the function clearSelection in List.js but I don't know how I can "attach" it to the closing X.
I was wondering if (and where) I could add or change the options for the selection: Instead off adding to previous selection I would like to limit the new search to previous search results.
Can I somehow use the customized popup from my web map to be shown with the search results?
Sure this ability was added in version 2.0.1.2.
I don't want the link that I defined for the popup to show in the results list! In which file is that configured
If you are using the popup from the webmap then you just do not include that field in the eSearch results when you configure which fields to display.
Where could I possibly tell the widget to clear the selection when closing the eSearch Widget?
If you un-check "Add Result as Operational Layer" then the search results will be hidden when you close the widget. If you have "Add Result as Operational Layer" then it is assumed that you want the results to stay unless explicitly cleared.
Instead off adding to previous selection I would like to limit the new search to previous search results.
There is no option for "select from current selection".
- Regarding my web map popups: Only when I "Disable search results popup" I get the web map popup when clicking in my feature. But then I loose the nice functionality to get the popup straight from the results list. Is there a way to combine both?
- Link: I tried to make the popup to look about the same as from the web map because of the above mentioned functionality. In my web map popup I have a customized text that shows most of the attributes and on top a link for sending an email. When I add a link in eSearch I cannot specify that it should only show in the popup. Do I?
- Selection: I realized that there is no option "select from current selection" but I thought it can't be too difficult to add. Isn't that mainly a matter of SQL definition? Could you maybe point me to the coding lines where the available options are defined? Then I could see how it looks like.
Regarding my web map popups: Only when I "Disable search results popup" I get the web map popup when clicking in my feature. But then I loose the nice functionality to get the popup straight from the results list. Is there a way to combine both?
I find it strange that you are not seeing the webmaps defined popup. Can you check that you are actually using the latest version of the eSearch in your app? To do this hold the Alt key and click anywhere in the widget body and a message will display showing the widgets version number.
Link: I tried to make the popup to look about the same as from the web map because of the above mentioned functionality. In my web map popup I have a customized text that shows most of the attributes and on top a link for sending an email. When I add a link in eSearch I cannot specify that it should only show in the popup. Do I?
You can check the popup only column in the fields list.
Selection: I realized that there is no option "select from current selection" but I thought it can't be too difficult to add. Isn't that mainly a matter of SQL definition? Could you maybe point me to the coding lines where the available options are defined? Then I could see how it looks like.
Not trying to be sarcastic, but if it were that easy I would have already added it. You can look at the buildWhereClause function but there is a lot more going on with adding or removing of Features from the currentFeatures array.
I downloaded the latest search widget 2.0.1.3. I had to copy the "LayerFieldChooser.js" file from WAB ver 1.2 to ver 2.0 developer edition. It works great!!
I want to customize the results of the buffer/spatial selection to return sum of number attributes (e.g. sum of parcel acres) for all selected/returned parcels. is there an easy way to do it? can i add the returned results feature attributes in widget.html? Can someone guide me here?
I am not sure why you would have needed to copy the LayerFieldChooser.js file from 1.2 as I just checked the zip file and it contains this file. You can setup a filed to sum in the eSearch just see the help doc:
When I ran the widget it gave me an error that its looking for that file in …….\WebAppBuilderForArcGIS\client\stemapp\jimu.js\dijit. But the file was actually located under …..WebAppBuilderForArcGIS\client\stemapp\widgets\eSearch\setting. I copied it and it worked!
I do not have the “sum field values” under edit field format even for number fields….Is that under a different version of the widget?
Based on the fact you are not seeing the sum ability and the issue you had with the LayerFieldChooser.jsI would say that you are not getting the latest version of the eSearch in your chosen app. Are you just copying the eSearch folder to the client/stemapp/widgets folder? If you have an app that already has the widget added then you have to copy the eSearch folder to that specific apps widgets folder as well. I.e. copy eSearch folder to [install dir]\server\apps\[app #]\widgets
Can you hold you Alt key on your keyboard and click in the body of the widget (not the widgets settings page, but the actual widget) and it will show a dialog with the current version of the widget you are using?
Also are you copying the whole eSearch folder from the zip into the client/stemapp/widgets folder?
Easy question here. If I have an existing app and I want to upgrade from 1.3 to 2.0, is there a simple way of doing this without breaking anything? I'm a little hesitant to just copy over the files in the app and the builder because I don't know if that's going to cause me an issue later on. And there seems to be no handy upgrade widget button like in the flex view
I also see that I imported an app from an old version of WABde (I had to wipe out everything and start over). Importing an app with a widget in it seemed to import that widget into the program generally as well. That's interesting.