How to inspect attribute rule definitions on Enterprise Service?

[AndrewRudin1]

I am trying to troubleshoot an issue with editing data in an enterprise geodatabase through a feature service in ArcGIS Enterprise 11.3

Does anyone know if information about attribute rules on feature classes is put into a feature service when you publish a reference service to Enterprise?  And if so, where can I inspect that attribute rule definition in the service's JSON?

I'm asking because I've run into an issue where if I edit the feature class with a calculation attribute rule applied, it will work if I edit the feature class directly from Pro.  But if I make the same edit through the service referencing the feature class, the attribute rule doesn't fire.  This made me think that somehow the service is not aware of the attribute rule, so I wanted to verify.

[RPGIS]

Hi @AndrewRudin1,

I have ran into this issue several times even though we are on 10.9.1 but I would recommend checking each of the following:

1. Check the compatibility version of your enterprise with the rule version. The rules will show you the lowest compatible version of enterprise it will work with, and if the rule is set for a higher version than your enterprise then that might be the issue.
2. Another issue is there could be a potential bug where the syntax checks out and the edits can be applied in pro, but once it is turned into a service, then the issues arise. Check the server logs in the server manager to see what the error is. If you get the message "script error at line 0" then that is a possible sign that there is a bug.
3. Check if "Exclude from application evaluation" is checked if it is accessing $originalfeature or some other feature or table.

[MikeMillerGIS]

Attribute Rules always get called in the database, regardless of client.  I would start by inspecting the Service Logs on Debug Mode.

Also, how are you verifying the rule was not fired?  Did you refresh or requery the row?

When a service edit is made and that edit affects other fields or other rows, it returns a ReturnEdit payload.  ArcGIS Pro knows about this payload and makes the appropriate updates to the affected features.  Some webapps may not honor this ReturnEdit payload, so if you AR edits other fields or other features, they are not refreshed and will be out of sync with the edits from the AR, so a manual refresh is required.