Update, this is a bug: BUG-000167335 for ArcGIS Experience Builder (esri.com)
I'm using Map Viewer in ArcGIS Online to create a map with pop-ups which I'll place alongside a query widget in an Experience Builder app. The purpose of the query widget in my use case is to give the user a drop-down list of unique features so that they don't have to search the map. The query results would then display the pop-up configured in the map.
For whatever reason, the query results will not display an Arcade content block, while the map pop-ups do. I tried first with my own content, then with the Arcade examples map (as discussed in this Esri blog post), but no luck getting the Arcade content block to appear. I'm also making sure to check the "use web map settings" box in the query widget configuration panel.
The attached image shows the Arcade examples map mentioned above alongside a query widget that returns the pop-ups from the Peaks layer. The Arcade content block doesn't show, while the two text content blocks do show.
Thankfully, my use case allows me to just use a text content block with many Arcade expressions (see attached image), but because of the different (yet repeating) formatting I need for various pieces of my data, it's a LOT of expressions to maintain compared to what I'm able to do with just one Arcade content block.
I wasn't sure if this was a bug. It certainly doesn't seem like the intended behavior, but maybe it is? Weirdly, I couldn't find much of anything about this--pretty much just this post from a couple weeks ago in which someone had the same issue.
I really like the query widget as opposed to using something like a list widget combined with a feature info widget. I really don't want to dedicate space to both of those (I realize I can use a section with views, but the query widget is just so much more intuitive/seamless, especially on mobile; I feel like you need a good amount of vertical space to make the list widget worthwhile, and the drop-down in the query widget is just so much better).
Thanks for reading and apologies if this is actually just a bug.
@RohanC
