Experience Builder Tips and Tricks

About a month ago, I was tasked with a project to find points in a polygon area. I could never quite crack it, in part, because by polygon layer wasn't actually a layer, it was a table, but I kept getting close. Ultimately, we converted the table to an actual polygon layer and used the Zone Lookup Instant App. It did everything we needed and was super easy to set up. Then, the new ArcGIS Online update came out and the update to Feature Info didn't quite work the way anyone expected and I wondered if could use the Near Me tricks I was working on to make a popup replacement. Again, I couldn't quite get there. I felt I was so close to something useful, but I every iteration lead to some weird response. I wound up with some versions that would work on mouse click and others that would work with a Search Widget, but never both at the same time. In some versions, clicking a polygon would select a neighboring polygon. I was getting a bit obsessive and going slightly crazy.

I think I finally cracked it. I found the idea that is mostly useful. I built a Zone Lookup App using only OOTB Experience Builder widgets. Did you know one Near Me Widget can trigger another? This is a build based on double-hidden Near Me Widgets. This is a build that can find points in a polygon using either a Locator Source or a Layer Source, or by clicking on the map. Downsides: If you want to use both a Locator and Layer Source, you will need to separate Search Widgets and clicking directly on the point layer will not trigger the Near Me functions.

For my demo, I have a map with a polygon layer of counties and a point layer of Bigfoot sightings. Let's find some big feet! (Maybe don't Google that.)

Step One: Big Feet Near Me (Really Don't Google That.)

Let's add a Map Widget and connect it to our Bigfoot map. I'm going to turn off popups. I think it will be better that way. Then, I throw in a Near Me Widget and rename it Bigfeet Near Me. In my Near Me settings, I will set the Search Distance to 0. I go to Add Analysis and select my Bigfoot layer and set the Analysis Type to Proximity.  (To all the confused people who just typed the first four letters of analysis and big feet into their search engines, this isn't the site you are looking for.) Now, go back to the Map Widget Settings Action Tab. Add a Record Selection Changes>Framework>Select Data Records Action and set both the Trigger and Action Data to the Counties layer. Then, Add Action and Bigfeet Near Me>Set Location. This should find all of the Bigfeet in a county by mouse click.

Step Two (Optional): Search By Layer Source

Add a Search Widget. Add New Search Source and select the Counties layer. It would be good design to change the Hint to something that clarifies that the user should enter a county name. Turn off Enable Filtering For Layer Source Search. I've also renamed my Search Widget to County Search. In the Action Tab, add a Record Selection Changes>Map>Zoom To Action and then a Bigfeet Near Me>Set Location Action. Zoom To should be before Near Me, apparently this order matters. Now, searching for counties should find Bigfeet.

Step Three: Search By Locator Source

This is where it gets a little weird. We are going to double up Near Me. (Google people, go away, this still isn't what you want. (Seinfeld voice: Not that there's anything wrong with that.))  Add a second Near Me Widget. We'll call this one Counties Near Me. As before, set the Search Distance to 0. This time set the Analysis Type to Closest Feature. You will also want to turn off Highlight Results On Map. In the Action Tab, add a Record Selection Changes>Bigfeet Near Me>Set Location Action.

Now add a second Search Widget, set your search to a Locator Source. In the Action Tab, make Record Selection Changes>Map>Zoom To and Counties Near Me>Set Location Actions. Now using the Locator Search will find a location, send it to the Counties Near Me Widget, find the correct county and pass the county on to the Bigfeet Near Me Widget.

Step Four: Build An Output

Depending on how your user searches and in what order, the Counties Near Me Widget may fall out of sync with the currently searched for Bigfeet. So you will definitely want to hide it. And I still ain't a fan of how Near Me looks so I'll hide both of them. To make my output, I will use the newly updated capabilities of the Feature Info Widget. To get my Bigfeet, I will go to the Outputs Tab>Bigfeet Near Me>BigFoot (Proximity) Output View. 

For the Counties, I will add the Counties layer from my map in the Added Data Tab. Then, I will click back on the Counties layer in the Settings Panel to get more options and use the dropdown menu to pick Selected Features.

Go find big feet near you from the safety of Experience Builder. 

All of the following does sort of assume that there's not a major bug introduced by the update. There seems to be a big problem.

The issue has reportedly been fixed.

It's everyone's favorite holiday that means more work instead of less work, ArcGIS Online Update Day!!!!!!!!!!! I've been looking over the What's New page and trying a few things out to see what you can do in Experience Builder today that you couldn't do yesterday and it's a lot. This is a big update. I don't see any huge new features, at least for my applications, but many of the small updates to existing widgets are absolute gamechangers. I'm going to go over what I think are the most important new options and some first thoughts of what you might be able to do with them.

New Actions:

• Open Sidebar
• Open Widget
• Plan Route
• Related Data
• Set As Analysis Input

All of these actions look super useful. I'll circle back to a few of them later.

New Data Sources:

• Building Scene Layers
• Imagery Layers
• Oriented Imagery Layers

I don't really use these types of layers, but if you do, this is lifechanging.

Privacy Settings: You're a businessy business person and you care about businessy business stuff like SEO and analytics. Now, you can use Google Analytics to track your performance. It also comes with the option for the user to turn it off so you don't get arrested in the EU or the ever growing list of jurisdictions where a turn off cookies button is legally required.

Icons: This was honestly the first thing on this update list that made me excited and it is such a tiny change. There are way more default choices in the icon picker. That's all, but wow is it a big quality of life improvement.

Related Data: I don't know how to use this yet, but it sounds very intriguing.

Additionally, you can use the layer's relationship to configure a message action where a trigger involving one data source can trigger an action with the related data.

New Widgets:

• Building Explorer: Doesn't really apply for me, but if your working on an indoor space, this looks like the widget for you. 
• Feature Report: Turn Survey123 stuff into PDFs. Looks super useful if you have Survey123 stuff.
• Measurement: (Did I do this? I might have done this. My first week in Experience Builder I put in a call to ESRI support asking for the Basemap Gallery, Select and Measure Map Tools to all be built out as separate widgets and now it's all been done. Tell ESRI what you want. They really do listen.) The gamechanger here is the ability to control where the Measure Widget actually goes. You can also set your default units to something other than your organization's defaults. A make-your-own-units and appearance options would be good next steps, ESRI.
• My Location: Do you want to stalk people? Now you can get their exact location, speed and altitude. There's some sort of neat walking survey application that could be made based on this widget. A field worker opens your app on their phone. It starts tracking their movements. As they go, they make notes with the Survey123 Widget. In the end, you have the Survey123 responses and the walking path that triggered them.

Widget Updates:

• Add Data: When I mentioned earlier that some small updates are gamechangers, this is the kind of stuff I was talking about... You can now sort your search results in the Add Data Widget.
• Analysis: For the first time, in one limited capacity, it is now possible to write custom code and run it in ArcGIS Online Experience Builder as the Analysis Widget supports custom geoprocessing tools. The ability to select stuff with one widget and make the Analysis Widget do stuff with the Set As Analysis Input Action has limitless potential.
• Basemap Gallery: 3D support. If you have 3D stuff, you probably want a 3D basemap. Now, it's an option.
• Bookmark: Your user has turned off the the visibility on three map layers, then they click on a bookmark to zoom to their area of interest. They are confused and angered as all the layers they turned off suddenly come back on plus two more that are normally off by default. Don't let this happen to your users. Turn on the Ignore Layer Visibility option so that map layers don't change with bookmarks. This should never be turned off unless you are deliberately making some sort of extremely guided Storymap-type experience. But, ESRI, could we please have the opposite as well? A bookmark that changes layers but not location would also be very useful.
• Directions: Your user has searched with Near Me to find their closest park, now they probably want to know how to get there. The Plan Route Action is here to save the day! 
• Edit: Add data with the Add Data Widget and edit it.
• Feature Info: Popups are great and all, but they also block your view of the map. That's why @RobertScheitlin__GISP made his Feature Panel and I made Identify. If you're not on Developer Edition your best popup replacement is Feature Info, but it can only handle one layer...until now. Sometime in the next few weeks, expect this sentence to turn into a link about combining the Open Sidebar Action and the Feature Info Widget into a full popup replacement, like Robert's auto-opening Feature Panel Sidebar trick. Edit: Tried and tested. It doesn't really work. Only one layer of features registers as selected at any given time, so it's not a popup replacement yet.
• Legend: The legend can be configured to only show stuff that currently on the map. Another small improvement that makes a big difference in user experience.
• Map:
  • Overview Map: It was technically possible to make an overview map from the very first version of Experience Builder, but now it's easy enough, as in one click, to actually be worth doing.
  • Dock Your Popups: Put your popups in a more convenient spot than covering up your data.
  • Zoom To Selection URL Parameter: Go to a specific feature on the map as soon as the page loads. Build links from other applications.
  • One Map = Select By Default: What a nice little quality of life addition.
• Near Me: More export options.
• Print: Report templates.
• Sidebar: A few updates ago, we got the Toggle Sidebar Action which was pretty good, but what if the Sidebar was already open and you don't want to close it. Enter the Open Sidebar Action. But ESRI, if you're going to give us an Open Sidebar Action, we should also get a Close Sidebar Action.
• Table: 
  • Control column widths: Yes, please.
  • Throw your whole map in and get tables for everything: That's faster than doing it one by one.
  • Delete Stuff: You can edit from a table, of course, you should be able to delete from a table, too.
• Views Navigation: Supports the Views Change and Button Click Action Triggers. This along with the Open Sidebar and Open Widget Actions makes all sorts of crazy user clicks one thing and everything changes stuff possible.

Those are my Experience Builder Update highlights, and no, I did not actually mention everything in this update. Is there something I missed on the update list you are excited about? Should I do this for every update?

Today, I would like to walk you through three things I built in Experience Builder, why I chose to use Experience Builder and (on a philosophical level) how they were made.

Telecom Editor

Why: To Make A Focused Application

We have a group of people in the city who are tasked with building out the telecom infrastructure used in city operations. They also must track the telecom infrastructure built by private companies within the city. These people are not GIS people. They don't need access to all the data in the city. They need access to telecom data and they need to be able to edit it. That's it. Anything more than that would be more confusing than helpful. Could they use the Webmap Viewer? Sure, but it just wouldn't be as dedicated to doing one thing. ArcGIS Pro? Way more confusing.

How: ESRI Widgets

This application is pretty basic. Fundamentally, it is just a Map Widget, an Edit Widget and an edit enabled Table Widget. It does have a few custom widgets, but none of them are essential to the application.

At this point, I would like to explain that my job is specifically to build stuff that is more complicated than can be done with OOTB tools. The next two projects are significantly more complex. The best way to keep a project within the OOTB capabilities of Experience Builder is to keep it focused on a small number of closely related tasks. Trying to build an everything app in Experience Builder is a really bad idea...

Virtual Map

Why: It's An Everything App

We want every city employee to have access to all the city's authoritative data. People in different departments need access to different things and to do different things, but sometimes they also need access to other sources of data. In many ways, this is a simplified version of ArcGIS Pro dedicated explicitly to city data. As above, most of the users are not GIS people, many of them are not even computer people, so the Webmap Viewer and ArcGIS Pro are not realistic options. With the retirement of WebAppBuilder, the only viable options for building such an application is Experience Builder or the JavaScript API. And as I see it, Experience Builder is the JavaScript API with some helpful UI components built-in. In retrospect, a series of department focused applications may have been faster, easier and better, but an all-in-one application is still possible.

Why: It Saves Us Money

Shhhhhhh! Let's keep this one quiet. Don't put this anywhere ESRI can hear about it.

An ArcGIS Enterprise subscription comes with unlimited Viewer licenses which is all that is necessary for our users to log into Virtual Map. At standard list prices, an ArcGIS Pro subscription for all of our Virtual Map users would cost the city approximately two million dollars a year. And that's not counting training or hiring additional tech support personnel.

For all the GIS Administrators and Managers out there, how many people in your organization really need a Pro license? How many of them could instead be using the Webmap Viewer or one of the various web apps to do their jobs? It might be more than you think. 

How: Time and Communication

Virtual Map was in development for over a year before it was officially released and it's still not entirely finished. It may never be truly finished. Why did it take so long? There were some external delays and I was also working on other projects, so several months of unproductive time were being counted in there. But one of the biggest reasons it took so long is we were trying to get it right. Throughout the entire process, we were communicating with the users to try and make what they needed. Versions of the application were available for testing six months before the official launch. You'll see the other big reason it took so long a little later.

Pet Finder

This application needs a little explanation. You're an animal control officer and you just caught a dog. How can you figure out who owns it? Luckly, our city has records of many of the dogs in the city. Too many records. Tens of thousands of records without pictures. Then, there is the problem of identifying breeds and colors and if the person who made the record agrees with your identification. How can you narrow down this list of thousands to a few prime candidates so you can actually call some people and ask if they are missing a dog? Pet Finder was built to help.

How: Cheating

Developer Edition is cheating. I have previously pointed out using Developer Edition is a pretty sweet trick even if you can't code. As much as Experience Builder is sold as a no-code environment, it is so much more useful and powerful as a developer's framework. This application is built around two custom widgets, one that takes user input, finds what animals meet the search criteria, filters through the possibilities and controls the map display and the other displays the candidate animals in a list. Other than connecting me to the webmap, Experience Builder is not doing much functionally in this application.

Virtual Map contains 19 functional widgets. Eight were developed by ESRI and another was made by ESRI and modified by me. Another widget was made by a third-party and three more are my modifications of a third-party widget. And the last six are entirely my creations for a final score of 8 OOTB widgets to 11 custom ones. Learning to code is probably the greatest Experience Builder trick of them all.

Why: Experience Builder As A Framework

I knew before I started that what Pet Finder had to do was too complex for the OOTB widgets, so Experience Builder was useless on this project? No, it was vital. Before I started, I thought about the ingredients I would need to make this work. I was working with a map and feature layers, so obviously I would need the ArcGIS JavaScript API. I had a good idea for a slick user interface that would respond quickly and update itself based on user inputs. You know something that would react. React! React was literally built for this! Ok, so I want to use React, but I don't want to be limited to strict one-directional data flow, so I'll need a state manager like Redux. And I don't want to spend too much time messing around with the user interface, so having a UI component library and a CSS library like Bootstrap would be very nice. A drag and drop builder would be even nicer. Ok, let's add this all up.

ArcGIS JavaScript API + React + Redux + UI Component Library + Bootstrap + Drag and Drop Builder = Experience Builder

By the time I was through with Pet Finder, I had used every single piece of that formula and I got it all set up for me by just clicking a single button. Experience Builder was still very helpful even though it was useless.

In Experience Builder, there are two ways to get map layer controls and a legend in your map. The first option is to flip on the Layers Tool in the Map Widget. This will give you an icon on your map that when clicked contains a list of map layers and a legend in a tabbed view. It's super easy, looks ok, and has zero customization options. You can't even decide where to put it. It'll just dance around the map however Experience Builder feels like putting it. The other option is to use the separate Map Layers and Legend Widgets. This takes only slightly more work, but it gives so much more customization controls and looks better. The main problem is that two always open widget take up way more screen real estate than a single icon. Why can't we have the power of the Map Layers/Legend Widgets, but the compactness of the Layers Tool in the Map Widget? Take a look at the title. We are making this happen.

Today's recipe calls for a Widget Controller, a Fixed Panel or Card Widget, a Section Widget, a Map Layers Widget, a Legend Widget and a Views Navigation Widget.

1. Add a Widget Controller to your Experience. This will compact your final product down to a single button.
2. As I am working in ArcGIS Online, I will place a Fixed Panel Widget inside my Widget Controller. Enterprise users will need to wait for 11.3 to do this, but an empty Card Widget will work just as well.
3. Inside my Fixed Panel Widget, I will add a Section Widget leaving some space up top for the Views Navigation Widget. Section Widgets are super useful tools in Experience Builder that allow different stuff to occupy the same space on a page at different times. Think of them as mini-pages within your main page.
4. In the Section Settings Panel, I will add a New View. Then I will rename my first view Map Layers and the second one Legend. Look for the three dot menu on the right to find the rename option.
5. Now, I will add the Map Layers and Legend Widgets into the appropriate views and connect them to my Map Widget.
6. Next, add a View Navigation Widget in that space we left earlier above the Section Widget and connect it to the section. If you would like some more control on the appearance, you could use Button Widgets instead.
7. Finally, you will want to change the icon and title of the Fixed Panel Widget. Instructions on how to do that here. The map layers icon is for some reason not one of the standard icons pre-loaded in the icon chooser, so I would need to find an icon I could download and then upload back into Experience Builder, and this is the step that caused me the most hassle.  First, I tried going to the Calcite icon library, where ESRI keeps all their icons. But the Figma links are broken, so there is currently no way to download an icon. Then I tried some developer tricks, looking through the assets in Developer Edition and using the Dev Tools in the browser to inspect the icon, but these assets are in .svg, a format the icon uploader won't accept. So I turned to Google, specifically Google's Material UI Icon Library, where you will find all of the icons Google has made, free-to-use for any purpose without attribution. This includes the icons in Google Maps and I was able to download their map layer icon in .png.
8. Optionally, bake your computer at 350°F for 15 minutes. (I didn't say it was a good option.)

Here's my final product, a combined Map Layers and Legend Widget that collapses to a single button when not in use.

Edit: Alternatively, you could use a Grid Widget. Placing multiple widgets in the center of a Grid Widget will cause them to automatically stack into tabs. It's easier and faster than the Section Widget method described above and more similar in appearance to the map layer tool built into the map. However, you will get some more optionality with the Section based method.

I've done many tips for the people making stuff in Experience Builder, but what about the people using that stuff. Here's one for you.

A number of widgets in Experience Builder, at least Query, List and Table, have a Show on Map option. 

I've done a query and hit this Show on Map button and my map is covered in a yellow indicating I should drink more water. This highlighting should probably be automatic when I run the query, but isn't.

I've finished with the stuff I need to do with this query and I want to move on to the next one, so I hit the Clear Results trashcan in the Query Widget, but the highlights are still there. I go to the bottom of the Query Widget and hit the Reset Button. That clears my search radius graphic, but the highlights are still there.

How do I get rid of this dehydration yellow? Look carefully at your map. Do you see something that wasn't there before? Keep looking... It's there. Down in the lower-right of your map... Where did that trashcan come from?

This is the button to clear the map highlights. No, it won't delete anything. It just makes the yellow go away.

Is any of this good design? Nope. Sorry ESRI, I can't defend every choice you've made and you've made a bunch of bad choices with this one. Here are some suggestions:

• Query results should automatically highlight when run.
• Designers should have an option for what highlighting color to use.*
• Clearing the results or hitting the Reset button on the Query Widget should also clear any highlighting or Drawn Graphics from the Query Widget.
• The Clear Highlighting button should be located within the widget that creates the highlights.
• The Clear Highlighting button should not be a trashcan or, even better, there should be icon options.

I'm sure there are Ideas for each of these suggestions already (I know I've posted one that covers two of them before.), so I'm not going to post this on the Ideas Board again. I know there are ESRI people reading this, so please make these changes, your application will be better for it.

Reminder: suggestions for product improvements, go on the Ideas Board, not here. Finding this button is a common user problem and there is just no way to talk about without it turning into an Idea post. Sorry for breaking my own rules.

*Edit: I owe Experience Builder a bit of an apology for this one. This option to change the highlight color does exist, at least in the most recent versions. In the Settings Panel Action Tab, go the Data Action Tab then expand the Show On Map option. Now select Use Custom Symbols and click the type of feature you would like to change.

Since I just had to track down one of my old answers to make sure I'm doing it right, I'm throwing a link to it here.

Upgrading to a new version of Experience Builder Developer Edition.

Developer 1.14, here I come.

Once upon a time, this blog had a YouTube video by @MichaelGaigg describing how to hack a Sidebar Widget into a dropdown menu. Sadly, that video has been lost to the sands of time. Here is my attempt to recreate the method (and create a new variant) having seen the video once about six months ago.

1. Add a Sidebar Widget. In the Style Tab, switch to px and set the width and height, as you'll get better results if the Sidebar stays a consistent size. You'll want the width to be about equal to the length of text. You want to set the height as low as you can. (This is a design decision. Do you need to display all your options at once or not? How much interactive space can you give up to this menu?) Then add about 20px to your number.
2. In the Content Tab, set the Dock Side to open down (third choice from left), Size to the number you picked above, Overlay and Resizable to off, and Default State to Collapsed.

    

3. In the collapsible side of the Sidebar (should be labeled First, if you have set the Dock Position as shown above), add a List Widget and connect it to the data you want in your menu. (Depending on what you are doing, you might also use a Text Widget containing a set of links or a set of Button Widgets*. You may also need to use a Column Widget to help with the styling.) If you are using a List widget, you will want to go to the Action Tab > Data Action and disable data actions.
4. Go back to the Sidebar Settings Panel under the Content Tab and style the collapse button. This part is pretty subjective, so play around with the options till it looks right. I think setting the Style to the more rectangular option looks better for this application. I set the Width to the entire width of my Sidebar and the Position to Center. Using a Width about 1/5th the width of the Sidebar and Position Right is also a good choice. 
5. Finally, add a Text Widget to the always open side of the Sidebar with some text to describe why the user should press that arrow. Here's my result.

Closed     Open

Note: I've given my Text Widget a blue background, not because I think it looks good but as a reminder that you should be aware of The Sidebar Problem. All that area is not interactive.

Alternate Method

Here is another way to do this that is slightly easier to pull off. Currently, it is not possible to do in any version of ArcGIS Enterprise, but it is coming soon in Enterprise 11.3.

1. Follow steps 1-3 as above.
2. In the Sidebar Settings Panel under the Content Tab, turn the Collapse Button off.
3. In the always open side of the Sidebar, drop in a Button Widget and give it some explanation text. Also give it an arrow icon with Position Right.
4. In the Action Tab, select Add A Trigger > Button Click > Your Sidebar > Toggle Sidebar.

Here's how this looks.  

Closed    Open

If you wanted to get real fancy with it. Maybe you could put your button in a Section Widget and have your button change itself to a different button with different text and an up arrow.

*Oh and if you are going to make a set of Buttons inside your dropdown menu, maybe make them also close the Sidebar.

Confused about how to use the ArcGIS Experience Builder "builder"?  In this blog, we'll examine the builder user interface to guide you in how best to create and navigate your first experience!

This article will walk you through creating a widget in Experience Builder describing the different map tools, similar to what you could create using the About widget in WAB.

As I'm sure readers of this article are already aware, WebAppBuilder is on the way out and many of you are currently working on re-building your old applications in Experience Builder. One very useful bit of documentation, for those of you making the transition, is the WebAppBuilder to Experience Builder Functionality Matrix. On this page, you can see what widget in Experience Builder is equivalent to a WebAppBuilder widget and what version you need to get it. 

The Public Notification Widget from WebAppBuilder is a very popular tool for finding residents in an area that might be impacted by some sort of event or regulatory change. Let's look it up in the table and see what we should use in Experience Builder...

Oh, no. Some of the widgets in WebAppBuilder aren't making the transition and Public Notification is one of them. But don't give up, unless you are on a truly ancient version of Enterprise, everyone with Experience Builder has a way to build a Public Notification tool in Experience Builder, right now. There are three potential methods...

Use the Public Notification Instant App

If you look at the Migration Path for Unplanned Widgets link in the functionality matrix, the official ESRI recommendation is to use the Public Notification Instant App, so let's do that.

1. Configure a Public Notification Instant App.
2. In Experience Builder, use an Embed Widget to drop in the application.
3. Ask your boss for a raise because you just put a robust public notification tool in Experience Builder in like 20 minutes.

Ok, it's a bit silly to make an Experience Builder project that just embeds another application and the embedded application won't really be able to interact with the rest of the project, but as part of a multi-page project, this could be an excellent option. But, this instant app is only currently available in ArcGIS Online and Enterprise 11.2 and is there a native Experience Builder method?

Use The Near Me Widget

The Near Me Widget is the best choice for a native Experience Builder Public Notification Widget. Here's how to set it up.

1. Add a Near Me Widget to your Experience and connect it to your Map Widget.
2. In the Analysis settings, you will want to choose Specify A Location and under Inputs you probably want to turn on Distance Settings and the Sketch Tools.
3. Now click Add Analysis to open the Edit Analysis menu. Use Select Layer to select your parcel layer and set the Analysis Type to Proximity.
4. In the Action Tab, go to the Data Action Tab and Enable Data Action, so that we can export our results.
5. In the Data Panel on the left side of the screen, find your parcel layer and make sure Allow Export is turned on.

    

6. Add a Search Widget and set your search source to be your parcel layer. You could also use a locator source, but be aware that if you do, your search radius will be based on a single point and not the geometry of the parcel.
7. In the Action Tab, hit Add A Trigger and select Record Selection Changes > Near Me > Set Location. If you don't want to use a Search Widget, you can alternatively set this action in the Map Widget to trigger Near Me from a mouse click. Or do both, you could do both.

Following these instructions, your end-user should be able to either search for a parcel with the search bar or clicking or drawing on the map and find the parcels within a given area then export the results to a csv.

Sometimes I forget how new Near Me is, this widget will make its first appearance in Enterprise 11.3, so for right now you will need ArcGIS Online or Developer Edition to do this method. Can we do Public Notification in Enterprise?

Use The Query Widget

There is one last method that will cover us all the way back to Enterprise 10.9.1. Honestly, I don't fully understand why Near Me was created as a separate independent widget when its functionality is almost all reproducible in the Query Widget. I suspect the product team made some choice early on that made it difficult to use the Query Widget as an output data source, thus necessitating the development of the Near Me Widget. (But that's just a theory, a he's retired now, we can retire the meme theory.)  

1. Add a Query Widget and select your parcels as the Data source.
2. Turn off the Attribute Filters.
3. Click Selected Features From Data Source and choose your parcel layer again as the Data source. (If you are on anything but Enterprise 10.9.1, you can also use the output from the Search Widget as above.)
4. Select which Spatial Relationship Rules you want for your end-user. You'll almost certainly want Intersect, all the rest are up to you.
5. Then turn on Enable buffer and set a default distance and unit.
6. Follow steps 4 and 5 from the Near Me method above to make sure your results are downloadable.

To see these steps in action and a few other refinements to this method, watch this video.

Ok, but what if you are on Enterprise 10.8.1, the very first version of Enterprise with Experience Builder, what can you do? Upgrade, it's really time to upgrade.