Better Attribute Rules Error Descriptions in Field Maps
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.
