This is a tiny thing I noticed but I don't even know where to begin with what changed. Widget 2.4 on the Left has a X to clear the search field and 2.6 doesn't have that any longer?
Is there a way to set the graphical search to always stay active when the widget is active? I know there is the setting to keep graphical search enabled, but as soon as the onClose function is called and the widget is reopened the graphical search is no longer enabled.
Hi Robert et al: I am finding that thus far, the 2.6.1.1 build is working without error in 2.7 for my tabbed theme. I did change the manifest.json when I brought the widget into the stemapp to read
"wabVersion": "2.7",
otherwise my graphical and query searches are behaving as expected. I am not using any spatial searches. No issues with results formatting our output, the builder gui or anything.
I hope everything is going very well with you! Is it possible to add data from my web map in eSearch Widget? I can find only the rest URL. Since most of widgets work with the direct web map and I want to cooperate with the same data.
you can work with the same data that is in your web map I just don’t provide a user interface to choose a layer from the map. You have to know the url that the web map uses for that layer.
It depends on how you have added your layers to your webmap. If your layers are hosted in your ArcGIS Online org, then the url will look something like this:
Thanks for your reply! I have a secure layer coming from ArcServer and then added the layer in webmap. I am looking a way where I can give my data to eSearch Widget from webmap layer.It is because some of widgets they don't take direct url such as infographic , Situation Awareness, and InfoSummary Widget. For them data must be coming from webmap. I will really like any idea or suggestions.
those other widgets need the layer to come from the web map and the eSearch is not map layer dependent. One of the benefits of the eSearch is that there is no need for the layer that is to be searched to exist in the map. I have no plans to add the convince capability of choosing a layer from the web map to be used in the widget, when it is just as easy to know your data and the url that was used to add the service to the web map originally.
If I do not produce a new widget (i.e. Identify widget is still version 2.5.01) that means that I have had no changes to the code and it will work in the latest versions of WAB.
If Do not have any changes and there is no breaking changes in the latest WAB there is no need for me to just increment the version number of the widget.
As far as moving the the links to the top of the widget. That is a customization of the widget that you will need to start a new thread on. This thread is getting way to big for me to continue to give customization advice on.
Have you ever seen an issue when doing a search on the eSearch it doesn't list all the features. For example it finds 5 features that match, it says Features selected: 5 but only lists out 4 features, and all 5 features are highlighted on the map. I have this happening randomly on my Parcel layer. I am using WAB 2.4 and version 2.4 or the eSearch widget. Below is a link to our live site. If you do a Parcel ID search on 6670 it comes back with 2 results, highlights both on the map in blue but only lists 1 out. Same thing if you search my Parcel/owner name by Smitty it comes back with 20 results but only lists 14 features. We did tweak the widget a little to be able to add our Deed link based on spatial reference. I was hoping you could advise in which direction I should take in troubleshooting.
I was playing around with this widget and was thinking that it could be useful for a Web App that I am building. Right now I am struggling with the "out of the box" Esri widgets because I am trying to view photos from a related table. Is this something that your widget can handle? Viewing images from a related table?
I believe they are stored as attachments. Have you had any experience with feature layers created via the Survey123 connect application? I used Survey123 connect to publish the feature, and in doing so, used the Repeat functionality, to create the related tables that house the attachments. Unfortunately following this approach has prevented me from being able to view the photos like I normally would have been able to do if the attachments were housed within the feature layer, and not the related tables.
I am not very familiar with Survey 123. But the The info provided is enough for me to give you the bad news. My widget will not be able to aide you with viewing the images.
In the 2.7 version of the widget I will be adding a selection highlight when you click on a record in the widgets results, but not a highlight when you hover using the Attribute Table Widget.
I was trying too upgrad the eSearch widget from 2.6 to 2.7 in a applicaiton that is built. I copied\replaced the new 2.7 eSearch widget folder to the \server\apps\12\widgets folder. I opened up the app 12 made some changes to the WAB configuration eSearch widget and saved but the eSearch widget is still showing to be 2.6 (ctrl+alt +click on the widget). what i am doing wrong?
Hmm... Not sure whats going wrong. Your workflow sounds right. Can you check the manifest.json in the zip that you think is 2.7 and verify you have the right zip file?
var home = new HomeButton( { map: map }, "HomeButton"); home.startup();
var fieldName = "PopTot2004";
// the counties map service uses the actual field name as the field alias // set up an object to use as a lookup table to work with user friendly field names
var fields = { "PopTot2004": "Population Totale (2004)", "PopTot2005": "Population Totale (2005)", "PopTot2006": "Population Totale (2006)", "PopTot2007": "Population Totale (2007)", "PopTot2008": "Population Totale (2008)" , "PopTot2009": "Population Totale (2009)" , "PopTot2010": "Population Totale (2010)" , "PopTot2011": "Population Totale (2011)" , "PopTot2012": "Population Totale (2012)" , "PopTot2013": "Population Totale (2013)" , "PopTot2014": "Population Totale (2014)", "NOM" : "NOM"
}; var outFields = ["PopTot2004", "PopTot2005", "PopTot2006", "PopTot2007","PopTot2008","PopTot2009","PopTot2010","PopTot2011","PopTot2012","PopTot2013","PopTot2014","NOM"];
//create popup var popupTemplate = new PopupTemplate({ title: "{NOM}", fieldInfos: [
// create a store and a filtering select for the county layer's fields var fieldNames, fieldStore, fieldSelect; fieldNames = { "identifier": "value", "label": "name", "items": [] }; array.forEach(outFields, function (f) { if (array.indexOf(f.split("_"), "NOM") == -1) { // exclude attrs that contain "NAME" fieldNames.items.push({ "name": fields, "value": f }); } });
I found an issue with the enhanced Search Widget even in this 2.7 version. The date field shows in the Enhanced search widget is different than the Identify widget. The result in Identified widget is correct but not in Enhanced Search Widget.
For instance, the date in my case should be 09/24/1971, but it shows as 09/23/1971. Do you know where should I change the code?
Do you date fields contain a time or just a date? Comparing the Identify with the eSearch is like apples and oranges as the identify uses a completely different task and means of getting the data from the server.
I'm querying very a very large parcels dataset (~1.8M records) and the search fails sometimes. Is there a timeout set to 1 minute or so for queries? I upped the memory based on the AGS error, but it seems like the application is timing out before the server times out or reaches a limit.
Can the enhanced search widget query a related table directly? After setting the data search URL input to the rest services URL of my related table I continue to receive a search failed! error when attempting to perform a search. I have had luck with using the "Add Relate" functionality however, this is insufficient for my needs because I need the "Search Expression" functionality to work with my related records alone. If this is not working by default, is there an easy code work-around?
Please excuse me if this question has already been answered - I had trouble finding the information. Thanks for all the great work Robert.