Experience Builder Button Widget

[ChristianSandoval2828]

 I can’t get the Query widget to talk to my Button or a Section. When I go to the Action tab on the Query widget and try to add a "Record selection changes" trigger, my Section/Button doesn't even show up in the "Select a target" list. I've tried connecting them to the same data (Query Output), but they still won't see each other. Is this possible for this widgets to work together? 

[NicoleJohnson]

@ChristianSandoval2828, it's possible for the Query widget to work with a Section widget (I'm not seeing that it's possible for a Button though).

Here's what I have. I have a Query widget connected to a layer of "peaks," and a Section with a couple views. The first view shows some instructions, and the second view houses a Feature Info widget with attributes about the peak. As a whole, this doesn't make sense (why not just put these attributes directly in the Query widget results), it's just a quick experiment because I was initially convinced what you're trying to do isn't possible, but if I were going to say that, I would at least need to try it first... so, thanks for that. When you select a peak result in the Query widget, the view with the Feature Info widget opens:

This all seems to be working, even though it's nonsensical. 

However, I'm not sure why you wouldn't be seeing the Section you created. Could you post some screenshots of your table of contents and Query widget configuration? I have to wonder if it's something weird...

If you're willing to change your direction a bit, maybe a List widget would be better suited to whatever you're trying to do?

Edit: I just realized you didn't specify whether you're on ArcGIS Enterprise or ArcGIS Online. This functionality doesn't seem to be available in 11.5 (the Enterprise version I have access to) at least.

[ChristianSandoval2828]

Hi Nicole,

I used a Section widget as a "functional menu" where each View acts as a dedicated workspace for a specific task. Instead of one giant widget I had to do 16 separate widgets, with their own section, add buttons to go back to the menu, and another button to take the user to our website with a code implemented to the link that fills out and search's for the data in our system. Experience builder is truly annoying.