Latest Contributions by mpboyle

The Search widget actions work as expected, the location is shown on the map, and the location is set in the NearMe widget. Below are the NearMe widget actions. The Data | Filter actions are what aren't working, same as what's shown above. I don't have a table action. This is the only widget set to filter data. Workflow: Enter Address in Search widget ---> location from Search widget is passed to NearMe widget ---> below are the NearMe widget actions

Nope, the NearMe widget is hidden, and the user does not interact with it.

The bug mentioned does sound similar, and I have contacted Esri support to raise a case. My workflow is a bit different than that mentioned in the bug report. I have the NearMe widget hidden behind a banner, so the user never sees or interacts with it. The selected feature from the NearMe analysis is displayed within a Feature Info widget. This part works as expected on the first and subsequent runs. What isn't working on subsequent runs are the filter actions set on the NearMe widget, shown below circled in red. These are two layers within the map that have a common field with the analysis layer. These filters only seem to work on the first run. The filter action in green is set to the analysis layer, it's auto-bound, and works as expected.

Below is my workflow with ArcGIS Online Experience Builder: 1. Users enter an address using a Search widget 2. Search widget location is passed to the NearMe widget 3. NearMe widget executes a Closest Feature analysis 4. NearMe widget has actions to: filter the map layer being used in the analysis (auto-bound), filter two other map layers using a common attribute. Step 4 only works on the first execution. On any subsequent executions, the two map layers being filtered don't seem to return anything. The polygon being used in the NearMe analysis continues to be filtered as expected. Below are examples: First execution works as expected. The polygon (orange) is filtered and the animated layer shown as an orange halo (green arrow) is filtered and displayed. Subsequent executions do NOT work as expected. The polygon (orange) is filtered correctly as this the analysis layer in the NearMe widget. However, the point feature shown with a green arrow should have an animated symbol as it is the feature with same common attribute as the polygon, but nothing is shown. I have tried multiple different settings in the NearMe widget. Tried using "Data" as the target rather than the map, same result. Is this a known limitation of the NearMe widget? ... am I missing some setting somewhere? ... is this a bug?

@DeirdreSmyth Nope, it's super frustrating. We have multiple hosted tile layers containing imagery projects that we'd like to be able to easily track usage on, but these item types (Map Service) don't return any usage data even though the Usage tab on the item page does. Hosted vector tile layers are another item type that doesn't return any usage data through the Python API. Again, super frustrating as we use hosted vector tiles for our organizational base maps and we'd like to be able to track usage on those items too. Below are some examples. We're a County government, our items are open to the public. Item identifiers provided for testing. Hosted Tile Layer example Hosted Vector Tile Layer example Perhaps someone associated with Esri can provide some insight why these particular item types don't return any data through the Python API...? @ShareUser @KellyGerrow @JakeSkinner

‎04-02-2026

@BernSzukalski Whether it's a feature service published from ArcGIS Server or a hosted feature layer on AGO, the fields list popup defaults to showing attributes in alphabetical order, rather than respecting the order of the service. Below are examples. The second example is for a commercial building hosted feature layer. All the fields at the beginning (top) of the service order have to do with the associated parcel (parcel identifier, address, owner, class, etc...). Those fields are scattered throughout the default fields list popup and I have to manually re-order the attributes to get them back in the desired order. ArcGIS Server (feature layer service) --- service field order on left, default fields list popup on right. ArcGIS Online (hosted feature layer) --- service field order on left, default fields list popup on right.

‎04-01-2026

@BernSzukalski I'm all for creating popups that are enjoyable to lookup by using custom text, but that's not going to be used in all cases, maybe not even the majority. There are several times where I want a simple list of attributes that flow in a logical order, which has already been done at the feature layer or service level. Having to scroll up and down the fields list to re-order attributes back to that logical order is a waste of time, not to mention frustrating when I've already taken the time to do it and then have that order ignored.

‎04-01-2026

I completely agree with @Heather_Hegi ... the desktop environment is where the schema considerations are done. Do once, apply many times. At the minimum, provide an option/checkbox for displaying the field list in the default schema order.

‎04-01-2026

4 years later...please, for the love of God, remove alphabetical ordering by default

‎03-13-2026

Maybe this is because it's the draft version...? If I view the published version, it seems to work as expected.

‎03-13-2026

I have an experience where I'm hoping to use multiple buttons to open the same anchored window on different pages, kind of like a dropdown list that will launch other pages. This seems to work sometimes, but other times when I click the button, the anchored list is displayed as expected, but then a second window is opened off to the side. Is this a bug? Is this functionality not supported? Do I have to create a separate window for every page?

‎03-06-2026

In case anyone else comes across this issue, what we found was that NULL values in the vector tile style JSON seemed to be causing the issue. Once the NULL values were removed, we were able to successfully print from the map viewer or ExB. Below is an example of what seemed to be causing our issue:

‎03-02-2026

We just noticed a similar issue. After the February 2026 update, printing in the Map Viewer or ExB using the default print service does NOT work if the map contains one of our own hosted vector tile layers. If I turn off the vector tile layer or switch to an Esri provided base map, printing works. If I replace our existing hosted vector tile layer, printing still doesn't work. If I add a vector tile package, publish, and add the resulting hosted vector tile layer, printing works. This seems less than ideal. We use AGO hosted vector tiles for many of our basemaps. It seems to get them working again, we may need to re-create all our styles, and then update all the web maps used as our base maps?!? That is assuming newly created styles work with printing. Esri support has been able to duplicate our issue on their end.

‎03-02-2026

Did some quick testing... If I follow our existing workflow of: adding a new vector tile package, publishing it, and then replacing our existing vector tile layer used for our base maps, I still get an error. If I publish the same updated vector tile package, and add the resulting hosted vector tile layer to a web map, printing works. This is less than ideal. It seems to get printing working we may need to re-create all our styles, and then update the web maps used as our base maps?!? This is assuming creating a new style works when printing.

‎03-02-2026

After the February 2026 ArcGIS Online update, we're getting print errors within the Map Viewer if using any of our own hosted vector tile layers or styles. We also receive errors when using the Print widget in Experience Builder when using our own hosted vector tile basemaps. All our vector tile layers and styles are hosted in ArcGIS Online. If I switch to an Esri provided vector tile base map, printing works as expected. If I turn off our vector tile layer, it works as expected. Are there any known issues with this update? Do I simply need to re-publish/overwrite our vector tile layers? Esri support has confirmed the behavior on their end with one of our hosted vector tile layer styles.

Online Status	Offline
Date Last Visited	Monday

My Ideas

Latest Contributions by mpboyle

Re: NearMe Filter Action Not Working

Re: NearMe Filter Action Not Working

Re: NearMe Filter Action Not Working

NearMe Filter Action Not Working

Re: Usage Values Not Being Returned

Re: Show Pop-ups in Attribute order rather than Alphabetical by Default

Re: Show Pop-ups in Attribute order rather than Alphabetical by Default

Re: Show Pop-ups in Attribute order rather than Alphabetical by Default

Re: Show Pop-ups in Attribute order rather than Alphabetical by Default

Re: Multiple Buttons to Single Window

Multiple Buttons to Single Window

Re: Print Error After February 2026 Update

Re: Printing from EB broken after February update - or is it just me?

Re: Print Error After February 2026 Update

Print Error After February 2026 Update

Usage Values Not Being Returned

Re: Use Button to filter list

Print Error After February 2026 Update

Overwrite Experiences to Maintain IDs

Provide Icons in Image Elements