Smart Editor Widget: Attribute Actions > Intersection failing to fire

481
4
11-05-2021 10:17 AM
Labels (1)
ahargreaves_FW
Occasional Contributor III

Hello @AlixVezina 

I'm using WAB Dev Edition V2.22 and am struggling to get the Smart Editor Widget Intersection action to fire upon creation of a new feature. It is configured as below. My wish is that a newly created point should pickup the FACILITY ID of the nearest Hydrant, Valve or Meter and add that value into the NOTES field of the Redline: Point layer.

ahargreaves_FW_0-1636132157349.png

I have the Action Settings set as below:

ahargreaves_FW_1-1636132286255.png

However, the NOTES field never populates. If I try the Preset or Coordinates Actions they all work fine. Can you advise me on if I have this misconfigured somehow?

0 Kudos
4 Replies
AlixVezina
Esri Regular Contributor

Hi @ahargreaves_FW ,

At first glance, please try checking the box for "Ignore layer ranking and find closet feature across all defined layers" under "Group Name"?

If that still doesn't work, please let me know.

0 Kudos
ahargreaves_FW
Occasional Contributor III

@AlixVezina  I checked the box for "Ignore layer ranking and find closet feature across all defined layers" under "Group Name" but it still failed.

I noticed that if I try the Address Intersection Action it too fails. This happens whether I use the default GeoCoder service setting of AGOL or our own hosted Geocoder Service.

This is interesting as both our own hosted Geocoder Service and the hydrant/valve/meter data I'm trying to intersect with are physically on a different server. Does the widget simply use features in the current map or is it attempting to traverse back to the underlying server where that data is stored and is possibly failing to authenticate?

0 Kudos
ahargreaves_FW
Occasional Contributor III

Possibly related to what I ask above is the fact that if I try to save anything using this widget I get the below:

ahargreaves_FW_0-1636133836242.png

 

0 Kudos
AlixVezina
Esri Regular Contributor

@ahargreaves_FW , the widget reads the data from the service, so it is possible this is an error coming from your server. Given your current setup I would recommend reaching out to Esri Support as they will be able to jump on a call and help you find the source of the issue for your use case.