Drop-down widget

[rogue_recon]

Are the drop-down widgets in the images below stock in Experience Builder, or are these custom? Here is a link to the experience to see it yourself. 

https://experience.arcgis.com/experience/52ffb83c47844ef5ba14e7a0f063fcc7/page/All-Surveys/

I have a project where I would like to do something similar and show data by the year, week, and mgmt area/city, and I have been at it for hours trying to figure out those drop-downs. I will create layers that can be turned on and off, but I would like to do it this way for aesthetics and ease of use. Any suggestions/answers would be much appreciated!

[JenniferAcunto · Accepted solution]

That looks like an ArcGIS Dashboard embedded inside of an Experience Builder app. Those dropdowns are category selectors in the dashboard header. 

[rogue_recon]

Interesting! I will take a look at doing that. Is that pretty common to embed a dashboard in EB?

[AngelaSchirck]

EB is great for this functionality.  You can embed dashboards, Instant apps, web pages and much more.  It makes it much more useful then WebApp Builder.

[AngelaSchirck]

I have similar things on my dashboard which I embedded in a story map.  This looks like, as Jennifer said, they embedded a dashboard in an experience builder.  You can definitely create a dashboard with the drop-downs.

https://pbcgov.maps.arcgis.com/apps/dashboards/abfbca1e2637490d960909e2d22a5495

[AngelaSchirck]

I had to go look, it's called a category selector:

You can adjust the settings and what happens when a category is selected (e.g. filter, zoom, etc).

[AaronPDXPaul]

Is there an update to this question? Why doesn't Experience Builder have a drop down widget? Creating a Dashboard and embedding it in ExB has limitations, and creates additional content. Why can't this widget be in ExB?

[EvanManrow]

Bumping this. It's crazy that there is effectively no way to accomplish a filter by related-table in Experience Builder or Web AppBuilder, but the functionality was drag-and-drop in Dashboards a decade ago!

The result is that any data used in Experience Builder needs to be flattened to a single table, which is horrible. If you use joined views to accomplish that, it locks your schema.

It's like ESRI hates properly-refactored data. 🙄