topic Action "Record selection changes" with Trigger "Select data records" stopped working in ArcGIS Experience Builder Questions

Action "Record selection changes" with Trigger "Select data records" stopped working

kabukow — Thu, 29 Feb 2024 11:22:23 GMT

Hi, we had multiple Experience Apps set up with a map actions and trigger "Select data records" where one layer while selected caused selection of another layer by common ID. These actions stopped working today. We tested that on different apps, using different datasets both of which function properly and are not corrupted in any way except for the above. Is this a bug that ESRI is working on or can it be fixed differently?

Thank you

Re: Action "Record selection changes" with Trigger "Select data records" stopped working

NBC — Thu, 29 Feb 2024 11:33:56 GMT

Hi, we are having the exact same problem with the map widget, but also I suspect other widgets where the select data records trigger has just stopped working. Have tried removing widgets, re-adding and recreating the actions/triggers but still not working.

Please can someone at ESRI provide some information on what can be done to resolve this as this seems to coincide with the quarterly updates earlier today.

Thanks

Re: Action "Record selection changes" with Trigger "Select data records" stopped working

DavidHofmannAY — Thu, 29 Feb 2024 15:12:30 GMT

I'm having the same issue, It appears that the AGO update created this bug.

Re: Action "Record selection changes" with Trigger "Select data records" stopped working

Jianxia — Thu, 29 Feb 2024 16:32:49 GMT

Thank all for letting us know. The team is investigating it.

Re: Action "Record selection changes" with Trigger "Select data records" stopped working

beachcamp — Thu, 29 Feb 2024 18:55:30 GMT

Having the same issue in a couple of production experiences. I'll stop troubleshooting and watch for an update!

Re: Action "Record selection changes" with Trigger "Select data records" stopped working

BlairMcclenathan — Fri, 01 Mar 2024 01:52:02 GMT

We are having the same issue with several production experiences as well.

Re: Action "Record selection changes" with Trigger "Select data records" stopped working

NBC — Fri, 01 Mar 2024 04:36:57 GMT

Thanks @Jianxia , do you have a bug/case number to follow at this stage? We have a few production applications where this is affecting staff so want to be able to communicate to them appropriate action is being taken.

Re: Action "Record selection changes" with Trigger "Select data records" stopped working

Jianxia — Fri, 01 Mar 2024 05:49:12 GMT

@kabukow @NBC @BlairMcclenathan @beachcamp @DavidHofmannAY This issue has been addressed. Could you please help confirm? Thanks!

Re: Action "Record selection changes" with Trigger "Select data records" stopped working

NBC — Fri, 01 Mar 2024 06:06:50 GMT

@Jianxia - Thank you. I've checked to see what's working now. I can see Map widget select record triggers to other Map widgets are working now.

However it appears select record triggers from search widgets to map widgets and from list widgets to survey widgets are still an issue.

Re: Action "Record selection changes" with Trigger "Select data records" stopped working

Jianxia — Fri, 01 Mar 2024 06:41:06 GMT

@NBC , noted. Thanks for getting back to us quickly. We are looking into it.

Re: Action "Record selection changes" with Trigger "Select data records" stopped working

Jianxia — Fri, 01 Mar 2024 06:42:43 GMT

@NBC , could you please provide a repro sample? We are not able to reproduce it.

Re: Action "Record selection changes" with Trigger "Select data records" stopped working

NBC — Fri, 01 Mar 2024 07:10:55 GMT

@Jianxia no problems its an internal application and we cannot share unfortunately so will attempt to explain.

We have a search widget which is using as its data source a point layer in a map. The point layer is hidden and represents a 1:1 relationship to another layer in the same map containing land parcel polygons.

When the user searches the address field from the address points layer in the search widget they should be zoomed to the location in the map to show the extent of the parcel, which has the same common identifier as the address point and selects the parcel in the map to show the user.

The zoom to trigger when record selection changes from search to map works, its just that the select data records does not work. The common field used to join point to polygon are both text strings and previously this worked well.

I tried just removing the widget, re-adding and setting up the trigger again but its still not working.

Thanks for your help!

Re: Action "Record selection changes" with Trigger "Select data records" stopped working

TianWen — Fri, 01 Mar 2024 07:17:18 GMT

We're unable to reproduce the issue. Would you be able to provide a sample app for further investigation?

Re: Action "Record selection changes" with Trigger "Select data records" stopped working

NBC — Sun, 03 Mar 2024 18:02:29 GMT

@Jianxia . The Search widget to Map widget select data records trigger looks to be working now - thank you.

The other issue, which is in a separate internal production app so again will attempt an explanation.

We have a list widget and a survey widget - both using the same point layer datasource.

The survey widget is in 'edit an existing record' mode.

The list widget is in 'single' select mode.

The Framework Select data records trigger from List to Survey is set to Auto bound. It was working well previously, populating the survey with the existing data, now get the 'Editing is not possible because of the globalid parameter was not provided' message across the top of the survey widget.

Our workaround it to select the point in the map, as the trigger from Map widget to Survey widget still works, however our users are getting confused by this change in workflow.

Thanks again for any help you can provide.

Re: Action "Record selection changes" with Trigger "Select data records" stopped working

Jianxia — Mon, 04 Mar 2024 00:38:59 GMT

@NBC , I was able to reproduce the issue with the List and Survey widgets. We are looking into it. Thanks for the detail information.

Re: Action "Record selection changes" with Trigger "Select data records" stopped working

Jianxia — Mon, 04 Mar 2024 17:03:46 GMT

@NBC , Select record trigger from List to Survey has been addressed.

Re: Action "Record selection changes" with Trigger "Select data records" stopped working

Jianxia — Mon, 04 Mar 2024 20:25:14 GMT

@NBC , record selection trigger from the Search widget to the Map widget is now working for me. Could you please help confirm them?

Re: Action "Record selection changes" with Trigger "Select data records" stopped working

JustinCurtis2 — Tue, 05 Mar 2024 23:45:29 GMT

Our organization is experiencing an issue where you have to click the search result a couple more times to achieve the record selection.

1. Using search widget to search for an address

2. Using address output as a trigger to select the record in a polygon parcel layer (using Framework)

Before the last update, you just clicked on your search result and the parcel would be selected, and the pop-up would also appear, all with one click. Now you have to click twice more on the search result from the widget to get the same result.

Re: Action "Record selection changes" with Trigger "Select data records" stopped working

Jianxia — Tue, 05 Mar 2024 23:59:39 GMT

@JustinCurtis2 could you please provide a reproducible sample or contact Esri Support?

Re: Action "Record selection changes" with Trigger "Select data records" stopped working

stariq22 — Thu, 07 Mar 2024 01:23:12 GMT

https://experience.arcgis.com/experience/4d2e8ef6b21343ddb243894f58df94f3

When you conduct a search using any specific address, such as 950 S Magnolia ave., you need to double-click on the search result for the pop-up to appear and the parcel to be highlighted. This is under the functionality of our search widget, which has the 'Auto select the first result' option enabled. Prior to the February update, this feature would automatically highlight the parcel and present the pop-up without requiring a second click. Our address search is using a custom locator and below is the screenshot of the action: