There is a trap that will catch every new Experience Builder developer at some point, usually the first time they add a sidebar.  Here I have a Legend in a Sidebar that covers up about half my map area. I open up the Preview mode and I start clicking my map. The popups work fine in the west, but as I move east. They suddenly stop working. Why is this happening? Well, even though the sidebar is closed the Sidebar widget is still on top of the map and it is effectively blocking you from interacting with your map. The fix is to rearrange your layout, so that the map is now in the always open side of the sidebar. Starting with my arrangement with the sidebar directly on top of the map: I grab and shrink my map down so I have some room to work. I drag my sidebar so it is outside my map. I drag my map into the sidebar. If your sidebar, now shows First and Second on the Page panel, you are doing this right. Which side is labeled First and Second is dependent on how your Sidebar widget opens. Resize your sidebar and map as necessary. Pay attention to this Overlay option. Turn it on if you want to have the sidebar cover the map. Leave it off if you want the map to resize without covering any content as the sidebar opens. Note: This problem of one widget blocking interaction with another widget can happen between any two widgets. Put a big empty text box over your map and your map will stop working as well. So, it is good practice to make your widgets as small as you can and trim any unnecessary whitespace. But, what if I have two sidebars? Well, you can do this trick again. Take the whole Sidebar widget and stuff it just under the First or Second label (whichever is the always open side) of Sidebar 2 and you should have two sidebars that don't mess with your map. I've never gone beyond two, but I don't see any reason you can't have three or four sidebars, maybe even more... ... View more

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.   ... View more

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. Configure a Public Notification Instant App. In Experience Builder, use an Embed Widget to drop in the application. 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. Add a Near Me Widget to your Experience and connect it to your Map Widget. 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. 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. In the Action Tab, go to the Data Action Tab and Enable Data Action, so that we can export our results. In the Data Panel on the left side of the screen, find your parcel layer and make sure Allow Export is turned on.   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. 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.)   Add a Query Widget and select your parcels as the Data source. Turn off the Attribute Filters. 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.) Select which Spatial Relationship Rules you want for your end-user. You'll almost certainly want Intersect, all the rest are up to you. Then turn on Enable buffer and set a default distance and unit. 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. ... View more

Here are some helpful resources that will help you create interactive and immersive web apps using ArcGIS Experience Builder. ... View more

The February 2024 ArcGIS Online update just dropped and I'm excited. It's got some big changes to Experience Builder. Select Widget! URL Parameters! Big improvements to Map Layers and Near Me! And perhaps most exciting of all, Group Filters! (And if you are on a 10.X version of Enterprise with SSO authentication, you will actually be able to use Developer Edition 1.14, unlike the cursed version 1.13.) Let's go through the steps to make a Group Filter. During my testing, I discovered a neat (new?) option that also filters the filters, but there was a trick to setting it up, so we will go over that, too. For this demonstration, I will be using a map with two copies of the same data, a polygon layer of the parks of Arlington, TX. We will make filters for Zip Codes and Golf Courses. Four of these parks are golf courses and the city of Arlington has 12 zip codes, so not every zip code has a golf course. First, we'll do zip codes. I will start by dragging a Filter Widget into my project. And hit this carot to make a Group Filter. Press the Select Data button, then highlight all the data sources you want to filter, Orange Stripe and Blue Stripe for me. You'll need to press the X up top when you're done. Now click the Group SQL Expression Button and select Zip Code in the Main field. Next, I will need to select Zip Code in my other layer. Under Operator & Values, I will use the Select Source Type Button to switch to Unique values. And hit the Ask for Values option. This Choose Input Style Button lets you choose between a dropdown menu or a set of buttons. I generally favor buttons as they are better for user experience and accessibility. I'll set the label to Zip Code to clarify to the user what these buttons are. Then, I'll go to the List Values Based On dropdown. This is how I'll filter my filter. There are three options here All Unique Values of this Field will always show all of the zip codes in the layer. I have not found a functional difference between the other two options, but they will reduce the number of possible zip codes when other filters are used. Here is the trick to making the filtered filters work: the other filters must be on a seperate Filter Widget. So I drag in a new Filter Widget and set it up to filter Golf Courses. As my application opens, I see 87 parks in two data layers and twelve zip codes. I turn on my golf filter and both data layers filter down to four parks and my zip code filters also reduce to the four zip codes with golf courses. Annoyingly, 12 zip codes, 4 golf courses and 2 data layers are all the right number of syllables to fit into the Twelve Days of Christmas, so now that's stuck in my head and in yours now, too. ... View more