nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

New Search in HeaderController (Flex Viewer 3.1)

TristanKnowlton

This applies to the 3.1 version of the viewer. I have configured the HeaderControllerWidget.xml to search my own data. To do so I disabled the geocoding tags (<geocoding></geocoding>). However when performing a search against my own address field in my parcel layer, the search is still using the geocoding service as well as my own data. I don't know what else to try in order to completely disable the geocoding service. Very annoying!!

Anyone have any ideas?

Finde mehr Beiträge mit dem Tag

Accepted answers

RobertScheitlin__GISP

Darryl,

Here is the changes in red. I am still struggling with the result grphic being added to the map when I think it should though.

find src\com\esri\viewer\components\singleLineSearch\SingleLineSearch.mxml and change the red lines.

           private function search():void             {                 currentState = "normal";                  if (!searchTerm)                 {                     return;                 }                  const hasCurrentSearchInProgress:Boolean = totalResultsToProcess > 0;                 if (hasCurrentSearchInProgress)                 {                     cursorManager.removeBusyCursor();                 }                  cursorManager.setBusyCursor();                 map.infoWindow.hide();                 totalResultsToProcess = 0;                 searchResults.removeAll();                                  if (!isFindEnabled){                     totalResultsToProcess++;                 }                  if (isFindEnabled)                 {                     totalResultsToProcess += searchLayers.length;                 }                  lastSearchTimestamp = getTimer();                                  if (!isFindEnabled){                     const addressData:Object = {};                     addressData[singleAddressFieldName] = searchTerm;                     var locatorParams:AddressToLocationsParameters = new AddressToLocationsParameters();                     locatorParams.address = addressData;                     locatorParams.outFields = [ "Ymax", "Ymin", "Xmax", "Xmin" ];                     locatorParams.location = map.extent.center;                     locatorParams.distance = calculateExtentRadius();                          locator.addressToLocations(locatorParams, new AsyncResponder(locator_resultHandler, locator_faultHandler, lastSearchTimestamp));                 }                  if (isFindEnabled)                 {                     var searchLayer:SearchLayer;                     for (var i1:Number = 0; i1 < searchLayers.length; i1++)                     {                         searchLayer = searchLayers[i1];                         findTask.url = searchLayer.layerURL;                         var findParams:FindParameters = new FindParameters();                         findParams.contains = true;                         findParams.layerIds = searchLayer.layerIds;                         findParams.searchFields = searchLayer.searchFields;                         findParams.searchText = searchTerm;                         findParams.outSpatialReference = map.spatialReference;                         findParams.returnGeometry = true;                          findTask.execute(findParams, new AsyncResponder(findTask_resultHandler, findTask_faultHandler, lastSearchTimestamp));                     }                 }             }

All comments

BjornSvensson

Just wanted to follow up and let everyone know that the 3.2 release fixes all (we hope) of these issues:

work with all projections
turning off locator in appbuilder
configure mapservices in appbuilder
specifying sourcecountry (only with widget tag, not in appbuilder)

FYI: if you want to see what other viewer code changes made it into 3.2, look at the 58 closed and verified issues for 3.2:
https://github.com/Esri/arcgis-viewer-flex/issues?labels=verified&milestone=1&state=closed

JaredYost

Has anyone else had any problems with the view extent not going to the geocoded item after running the search? I am not using the default projection, I have set my config file to match my data wkid="2243" .

After running the search it takes me to a blank view, way out of my extent, probably trying to set the view extent based upon wgs84 values? The interesting thing is that if I use the zoom to extents, to get me back to my map, I can generally see the geocoded point labeled correctly on the map. i.e. geocode respects my projection, extents do not not appear to.

Ideas?

Thank you

HeatherGonzago

We will definitely take this into consideration as it does appear that others besides yourself have asked for this functionality.

Thanks for suggestions.

TristanKnowlton

Thanks for the information Heather. In future versions I hope that an option is provided to turn off the geocoding service. As it stands now, if you use your own layers in the search bar, they show up last in the drop down list. It took me a while to figure that out. I thought it was not searching the data in my layers until I figured out that I needed to scroll to the bottom. That made the functionality unusable until Robert provided the code update. Sadly I don't think most of the users for our applications would figure that out and it would only confuse them.

Thanks!

HeatherGonzago

Hi everyone,
Just a little clarification to help ease any confusion.

The Search Header is currently designed to work to always use the geocoding locator service, whether you specify the default or one of your own. If you do choose to work with your own layers as well and add the <searchlayers> tag, it will use both the locator AND the layers you specify.

The documentation has been updated to reflect this as to hopefully avoid anymore confusion.

http://resources.arcgis.com/en/help/flex-viewer/concepts/index.html#/Header_Controller_widget_tags/01m30000000n000000/
http://resources.arcgis.com/en/help/flex-viewer/concepts/index.html#/Header_Controller_widget/01m30000003s000000/

Thanks for all your patience, and enjoy the new functionality:-)

RobertScheitlin__GISP

Darryl,

Don't forget the most important step of the forum process which is marking the thread as answered.

Don't forget to click the Mark as answer check on this post (step 1 in the graphic below).
Follow these steps as shown in the below graphic:

TristanKnowlton

Thanks a lot Robert! That did the trick. I really appreciate your help.

I think this is the best enhancement that has come to the viewer since they released the supported flex viewer. The original search widget is too complicated for average users.

RobertScheitlin__GISP

           private function search():void             {                 currentState = "normal";                  if (!searchTerm)                 {                     return;                 }                  const hasCurrentSearchInProgress:Boolean = totalResultsToProcess > 0;                 if (hasCurrentSearchInProgress)                 {                     cursorManager.removeBusyCursor();                 }                  cursorManager.setBusyCursor();                 map.infoWindow.hide();                 totalResultsToProcess = 0;                 searchResults.removeAll();                                  if (!isFindEnabled){                     totalResultsToProcess++;                 }                  if (isFindEnabled)                 {                     totalResultsToProcess += searchLayers.length;                 }                  lastSearchTimestamp = getTimer();                                  if (!isFindEnabled){                     const addressData:Object = {};                     addressData[singleAddressFieldName] = searchTerm;                     var locatorParams:AddressToLocationsParameters = new AddressToLocationsParameters();                     locatorParams.address = addressData;                     locatorParams.outFields = [ "Ymax", "Ymin", "Xmax", "Xmin" ];                     locatorParams.location = map.extent.center;                     locatorParams.distance = calculateExtentRadius();                          locator.addressToLocations(locatorParams, new AsyncResponder(locator_resultHandler, locator_faultHandler, lastSearchTimestamp));                 }                  if (isFindEnabled)                 {                     var searchLayer:SearchLayer;                     for (var i1:Number = 0; i1 < searchLayers.length; i1++)                     {                         searchLayer = searchLayers[i1];                         findTask.url = searchLayer.layerURL;                         var findParams:FindParameters = new FindParameters();                         findParams.contains = true;                         findParams.layerIds = searchLayer.layerIds;                         findParams.searchFields = searchLayer.searchFields;                         findParams.searchText = searchTerm;                         findParams.outSpatialReference = map.spatialReference;                         findParams.returnGeometry = true;                          findTask.execute(findParams, new AsyncResponder(findTask_resultHandler, findTask_faultHandler, lastSearchTimestamp));                     }                 }             }

TristanKnowlton

Here you go.

HeaderConrollerWidget.txt.zip

img.jpg

RobertScheitlin__GISP

Darryl,

Can you provide your HeaderControllerWidget.xml search portion, so that I can see exactly what you are trying to configure?

TristanKnowlton

I am. That would be much appreciated.

RobertScheitlin__GISP

Darryl,

Are you working with the source code? If so I can give you the fix for this issue.

TristanKnowlton

Well that's a good point Robert, lots of things do work right. I was really looking forward to that particular enhancement and I spent too much time trying to figure out what I was doing wrong. I was just a little sour:)

RobertScheitlin__GISP

Darryl,

Well there is LOTs of stuff that works right in the viewer. As far as when it will be fixed the best I can say is it will most likely be in the next release. As a developer myself I have great empathy for what they go through trying to figure out every possible angle and use people will attempt and then develop and test for that...

TristanKnowlton

Thanks for the reply Robert! Any idea how long it takes for bugs to be addressed for an upcoming release?

Do you know if there is a bug reported for <simplefillsymbol>? The use of fill symbols and outlines to highlight the search result doesnt work properly either. Once you right click and clear, it sometimes wont come back.

Never before have I jumped on a new release so early, now I know why that was a good idea. Why release it if nothing works right?

RobertScheitlin__GISP

Darryl,

This bug has already been reported to esri.

Nimm an der Unterhaltung teil

Angemeldete Mitglieder können Beiträge verfassen, Updates folgen und mehr. Neu hier? Registriere ein kostenloses Konto.

Schnellzugriffe

Community Help
Find useful guides, FAQs, and documents to help you navigate and make the most of Esri Community.