Include the ability for the Near Me widget to inherit fields from the webmap

[LindsayKing1]

My organization is using an Experience Builder app with the Near Me widget to replace our existing Public Notification app that was built using Web AppBuilder and the Public Notification widget.  With WAB's Public Notification widget, the widget had the ability to simply inherit from the webmap's popup which fields to include in the CSV export.  We would like Experience Builder's Near Me widget to have the same ability.  Users should have the option to configure the Near Me widget's analysis to either include user-defined fields (as is currently the case) or simply use the webmap's settings.

The reason this option is important for our organization is because address information is not handled uniformly between all records in our dataset.  Instead, we use arcade in the webmap's popup to determine which fields should be used to construct each address.  We would like to be able to configure ExB's Near Me widget to inherit this webmap configuration.  The way it is now, with the user having to define the fields, the output CSV contains a mess of fields, only some of which are needed for any given record.  It is creating far more manual work for our end users downstream in the output CSV.

[Zach-Williams]

Have you tried creating the Public Notification Instant App, and then you can create a new page and embed the instant app url link in it, and then put a button somewhere in your app and link the button to that page?

I will be recreating our municipality's internal map where they used Public Notification, but because it was built in WAB, I'm going that route explained above because it has the same capability. I understand the want to have it in Experience Builder, but until they get a better build inside of EB, this is a great go around.

[LindsayKing1]

Hi @Zach-Williams - Yes, using the Public Notification Instant App is the first option we tried.  But it doesn't currently include a way for users to select and buffer non-contiguous parcels, which - by adding in other widgets - is possible in ExB, albeit a little clunky.  Since being able to buffer non-contiguous parcels in one go is a hard requirement from our users, we had to go the ExB route.  Also, our original WAB Public Notification app included additional widgets beyond the Public Notification widget, so it's difficult to get functional equivalency using the Public Notification Instant App.  

But I agree with you that if the Instant App is an option (especially for folks who are building a Public Notification app for the first time rather than migrating from WAB), I'd recommend it.  It's a straightforward design and very quick to stand up.  It just doesn't quite cover the functionality we need in our scenario.  Thanks for the recommendation, though.