Use selected features as input in analysis tools in Experience builder

[LarsElmkær_Chwastek]

I have an idea about using selected features in an analysis tool in Experience Builder

If I use the select tool to select let's say 10 houses from a building layer, I want to be able to take that building layer and use as an input to for instance the buffer tool.. 

But at the moment it doesn't honor the selection.. it just takes all the features in the layer..

So it would be great if the selected features in the layer would be possible to use as the input.

This should of course also be possible with a GP/Web tool that you publish your self.

[jer0geo]

Our organization is currently using this functionality in WAB with multiple custom GP tools. It is critical to our work-flows and processes. We really need this available in the Experience Builder Analysis Widget if we are expected to migrate our apps from WAB!  

[DougBrowning]

We need this bad also.  A tool will always need a selection so it just has to be there.

[DougBrowning]

Started a new thread to get this fixed finally.  The current workaround it past our users.  Mostly that they have to select then follow Set as .. and then nothing happens on screen.  It does not open the Analysis widget or go to it.  So the user thinks nothing happened.  We are getting endless calls on this.  It should work like Pro does in the end.  In WAB the tool would at least see the selection and ask if they want to use it (it often ignored it but still). thanks

https://community.esri.com/t5/arcgis-experience-builder-questions/select-widget-cannot-connect-to-an...

@LarsElmkær_Chwastek did you ever get anywhere on this?

[andrewdc_tt]

I agree the Analysis widget needs this badly, and it doesn't feel like it should be this difficult!

At the moment I'm looking to build a workflow using Experience Builder and this is a showstopper. It really should be as simple as any selected map (or table) features get passed through to the widget, just like ArcGIS Pro.

I've tried the 'Set as Analysis input' option with the select widget and this is way too clunky as a viable workaround for the average user.