I have an Experience Builder application in Enterprise 11.2 that leverages two separate layers in the map. My map is only showing Layer A, but uses the data of Layer A and Layer B in two separate Feature Info Widgets. I have the following trigger on my map widget:
Record Selection Changes > Framework > Select Data Records
Trigger: Layer A
Action: Layer B
Connection: unique identifier
The issue that I'm facing is that when I select the point of Layer A on my map, it is not filtering the Feature Info Widget of Layer B; it will however filter the Feature Info Widget of Layer A. I have tried turning Layer B on in the application and making the selection, but still no luck.
Does Layer B need to be on by default in order for this action to work? It's simply a "hidden layer" only to be leveraged for it's pop-up.
I was able to determine the issue with ESRI Support. I had a second layer that had similar functionality that was set first in the data action list. This overwrote the second action that I was trying to set, and the application only noticed the first action. When I removed the first action, the second was the recognized.