Validation Rules on Feature Layer (branch versioned) can be triggered but no results

[StijnSchouten]

Dear ArcGIS Pro experts,

I'm currently struggling to transfer some validation rules I've developed locally on an FGDB to our Enterprise environment. I've followed these guidelines in this other community post

State so far:

1. The validation tables are created in the EGDB
   
2. I've manually added them to the feature layer and overwritten the published one. The checkbox 'Validation' has been enabled during this process
   

    "supportedExtensions": "FeatureServer, NetworkDiagramServer, UtilityNetworkServer, ValidationServer, VersionManagementServer",

3. Then in a fresh map I've added my UtilityNetwork with associated layers. After adding these layers I can right-click on DHCDevice and select 'Add Error Layers'. The error layers are added to the map.
   
4. I create a very simple validation rule (on DHCDevice), one that should always fail. Just for testing purposes
   
5. I restart the service and verify if I can view the validation rule in the service (yay it shows up). 
6. However when starting the validation. Just by zooming into one DHCDevice and pressing the validate button. Not much happens. The screen 'Validating' pops up but after that nothing. I expect: the validation status of the object to change and a record to be created in the Point Error table
   

   'Execute asynchronously' turned off or on doesn't matter seemingly. 
   > No calculation required, validation required, no error (does not change)

An error would be easier to fix but as nothing happens it is kinda difficult. Would greatly appreciate some advice or help on this topic 🙂 

[HusseinNasser2 · Accepted solution]

I can't tell what is going on but let us verify few things

1) Change the server logs to debug and see if you have entries for attribute rules being evaluated. 

2) Does full extent work? 

3) create new features and then evaluate them do they get picked up? 

if that doesn't work Finally try the following.  Delete the validation rules, delete the error tables, then add the validation rule again, this will generate the error tables. Makes sure you are using a branch version workspace when you do that.

Then delete  the feature service and create new map, add your layer and the error tables and publish with the validation server, create a new feature service and test that new feature service.. 

[StijnSchouten]

Hi Hussein,

Thank you for your reply! The triggered attribute rules show up in the logs and after zooming out more I could see why. 

The extent window is offset by some x,y. Is it possible to reproject the error tables from 4326 to a local CRS? That will probably fix this issue

[StijnSchouten]

I've used the tool 'Project' to change the projection. Republished the layer and now everything works great