nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Experience Builder Search Widget and Zoom not working

ChristopherEarley

My organisation has recently adopted Experience Builder. While we find it quite useful, we're encountering an issue with the 'Zoom to' functionality in the Search Widget.

Here's the problem: When I configure the search widget, I use the 'Data filtering changes' trigger to search for features based on a unique ID. It works perfectly when only one layer is involved. However, upon adding an additional layer, the zoom seems to pan to an unrelated location.

I believe the data isn't the issue here. I say this because when I tried replicating the process with Web App Builder, both the search widget and zoom functioned as expected.

I'd appreciate any insights or solutions. Thanks!

Vind meer berichten getagd met

ArcGIS Enterprise

Accepted answers

All comments

ShengdiZhang

Hi @CynthiaSkelhorn , thanks for your feedback.

used ArcGIS World Geocoding as a default search source, but I don't see that in Experience Builder.

This enhancement is included in Enterprise 11.5. In 11.5, you can use map search sources directly, and if you choose to connect to a map widget, some message actions will be automatically added to your search widget.

CynthiaSkelhorn

Hi @ShengdiZhang, I do not think this is a bug. I posted the steps that we followed to configure the search widget because, in our case, I did not initially know the steps for configuration. In Experience Builder, it seems a little more difficult to configure than in WebApp Builder. I'm not certain, but I think the search widget in Web App Builder used ArcGIS World Geocoding as a default search source, but I don't see that in Experience Builder.

ShengdiZhang

Hi @CynthiaSkelhorn , I have tested on both AGOL and Enterprise 11.4 and cannot reproduce this problem. Are you unable to zoom to the locator result, the layer result, or both? A sample app would be very helpful to reproduce this bug. If you cannot share your app, could you contact our Support team to help reproduce this bug?

Thanks

Shengdi

CynthiaSkelhorn

I was also experiencing this issue. The steps I followed to enable the Record Selection Changes were:

1. Under Content, Add Search Sources (layers in the map that we wished to search, or locators). In our case, I added one locator for Address Points and one layer for volunteer areas.

2. Under Action, I selected Add a Trigger - Record Selection Changes

3. Under Record Selection Changes, I selected Add Action - Map - Zoom To and then selected either the layer or the locator that I had added in Step 1 for Search Sources.

You can then select multiple search sources for the same trigger.

Save, test with Live View and then publish if working as expected.

JasminePrater

I was unable to get it to zoom using when Record Selection Changes, but did get it to work with your suggestion of using when Record Created. I think they need to tweak this to function better and/or be more clear.

CAPortesdeFranceThionvilleServ

Hello,
I managed to make the "zoom to" work with the "search" widget using the trigger "Created records" instead of "Modified records". See below.

(sorry it's in french)

KevinDeneault

Hi,

I am also experiencing the same problem using Experience Builder in AGOL. The web app template that I am using is Jewelry Box. I have tested it several times by typing in an address and nothing happens. Is ESRI looking into this problem?

Thank you,

Kevin

Laura

I am also facing zoom, pan to & flash issues in AGOL. Simply not doing anything when clicking on a result.

I had a similar issue in Portal and when I called about that they just logged a bug.

andreoudi

Hi!

I have exactly the same problem as mentioned above. I am using experience builder on ArcGIS Online (version 1.13.0).

ShengdiZhang

Hi @ChristopherEarley ,

Could you tell me which version of Experience Builder you are using? This bug should be fixed in an ArcGIS Online release earlier this year.

Regards,

Shengdi

JeffreyThompson2

The unique ID filtering on the second layer presumably fails because that id is not present on the second layer. Experience Builder gets confused and takes you somewhere 'random' (probably your datum). Here are some options which may work for you:

Add the unique ID to the second layer, so the filtering does not fail.
Remove the data filtering trigger.
Add a second search bar to handle the different search function.
Build a custom search widget.

Doe mee aan het gesprek

Aangemelde leden kunnen berichten plaatsen, updates volgen en meer. Nieuw hier? Registreer een gratis account.

Snelle Links

Community Help
Find useful guides, FAQs, and documents to help you navigate and make the most of Esri Community.