Better Attribute Rules Error Descriptions in Field Maps

[JCGuarneri]

The error messages for Attribute Rules are very vague in Field Maps. This causes trouble in two areas.

First, in developing and testing Attribute Rules, if there is one that isn't playing nicely with Field Maps, the error "Arcade expression is invalid." displays. This doesn't tell me which attribute rule is invalid. If there's no obvious candidate, the only way to suss it out is by stopping the feature service, turning off one attribute rule, restarting the service, and republishing. If there are more than two attribute rules, this gets very tedious very quickly. Even more frustratingly, this error does not show up in the logs or anywhere else. Listing the attribute rule name or even the code would drastically speed up troubleshooting.

 The second place this causes trouble is with editors in the field. If a constraint rule is violated, the end user doesn't get any feedback about what they need to correct to successfully submit their edit. In this case, the popup should return the custom error message that was set up with the attribute rule.

 

[AH2]

Yes!  This is such a problem for the field users having to search all the fields in their form to figure out what field is causing the error.  And the ability to have these constraints work easily in the offline package/offline areas maps.  I have so many issues with constraints working in pro and not the map

[VincentMcClarty]

This also is a problem for the Map Viewer (in AGOL and ArcGIS Enterprise 11.4) where the attribute rule during an edit operation that is invalidated does not get presented back to the user:

The only way to see the actual error is to look through the browser network traffic:

[ShayneODonnell]

Agreed. Came to post a similar Idea and searched to see if one already existed. The issue occurs in Experience Builder as well. When using the edit widget to create or update a record, if a constraint rule is violated, essentially nothing happens, not even a generic error message or anything. This is obviously confusing for users. If you use browser developer tools you can see the attribute rule error message being returned by the server, also the error messaging works when editing the service via Pro. Why would applications not also have this capability? This is going to be more important as we move more users to service based editing through experience builder and field maps solutions.