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; } } }

Search Widget w/ a lot of layer sources.

jjgarrett0

I am implementing the Search Widget in an application and I am trying to figure out a better way to configure the sources for the widget.

I have a feature service that contains 60+ layers in it and the requirements are to be able to search all of the layers with the Search Widget. Do I really have to manually define every single layer as a LayerSearchSource or is there a better way that I can just give it the feature service url and it can pull all of the layers in as a search source utilizing default values?

Find more posts tagged with

Accepted answers

Noah Sager

Hi @jjgarrett0, thank you for posting your question here. As far as I know, yes, layers have to be configured individually as a LayerSearchSource. Typically, a looping function should suffice. However, can you share a bit more about your use case, and why you want to have 60+ layers as sources in a Search widget?

All comments

jjgarrett0

Ah yea, that could be another route. I'll look into it. Thanks!

jjgarrett0

Thanks @Noah-Sager, I had planned on a looping function but just wanted to make sure I wasn't missing something elsewhere in the API. As far as the use case is concerned, my end user(s) have a lot of layers that are loaded into the map (with visibility defaulted to false) and they want to be able to search for any feature in any of those layers.

JeffreyWilkerson

I think that's what you'd have to do if you utilized the Search Widget, and I don't know about the performance of 60+ layers but it'd probably work at least. If you have only one (or a small number of ) field to search in each layer maybe you could mimic the Search Widget by using the where clause directly on the REST web service, then you could compile the possible features selected in whatever way you wanted from the resulting JSON, as in this REST call:

https://services2.arcgis.com/2t1927381mhTgWNC/arcgis/rest/services/BusStopsWAmenities/FeatureServer/0/query?where=stopID+%3D+5655&objectIds=&time=&geometry=&geometryType=esriGeometryEnvelope&inSR=&spatialRel=esriSpatialRelIntersects&resultType=none&distance=0.0&units=esriSRUnit_Meter&relationParam=&returnGeodetic=false&outFields=*&returnGeometry=true&featureEncoding=esriDefault&multipatchOption=xyFootprint&maxAllowableOffset=&geometryPrecision=&outSR=&defaultSR=&datumTransformation=&applyVCSProjection=false&returnIdsOnly=false&returnUniqueIdsOnly=false&returnCountOnly=false&returnExtentOnly=false&returnQueryGeometry=false&returnDistinctValues=false&cacheHint=false&orderByFields=&groupByFieldsForStatistics=&outStatistics=&having=&resultOffset=&resultRecordCount=&returnZ=false&returnM=false&returnExceededLimitFeatures=true&quantizationParameters=&sqlFormat=none&f=html&token=

Noah Sager

Join the Conversation

Signed in members can post, follow updates, and more. New here? Register a free account.

Quick Links

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