Latest Contributions by HusseinNasser2

I'm not sure if the user workflow allows it but I would suggest using the option to keep the original features  and let the attribute rules do the delete instead of the merge tool. This gives you more control as it turns the operation from a delete , update. To an update only and you will write the rule to trigger on update on geometry (use the triggering fields to set the rule to trigger only on the shape change) on the update you will have the control to query the original features (since they won't be deleted) and copy any attribute you want off of it. And then later you can insert the logic to actually delete the original feature.     My guess as to why you are losing your update is as you suspected the order of the operations causes your update to be lost/ not persisted.      ... View more

Hey Mike, if you use the Evaluate Rule gp tool and select the features you want to evaluate , the tool will only evaluate selected features.  This isn't currently available when evaluating through error inspector  ... View more

Make sure to pass in the correct layerid to queryDataElements that belongs to the Utility network layer, if you don't know it you can pass in empty string and that will pull all definitions of all layers which includes the utility network layer.   sourceId should be there, if its not, the UN likely wasn't published. Go to to the feature service root json definition and look for utilityNetworkLayerId to see if its published.    ... View more

Hey Garry, I'm going to assume you are trying to evaluate attribute rules. So first make sure you have batch calculation or validation rules on the class you want to evaluate. then add that class to a new map, and then right click on the layer on the map, you should see a new context menu AddErrorLayers, if you don't or it is disabled this means you don't have batch rules.  ... View more

This is now available in ArcGIS Pro 3.5. The user can use Attribute rules backstage options to change the default settings and it will persist when restarting Pro. ... View more

This bug has been addressed under BUG-000154445 in 11.1 , and ported to 10.9.1 patch 5,  11.3 should have this fix. If you have a repro case on 11.3 it could be a different bug, I suggest submitting a case. msg me the case number so I can follow up ... View more

Yes it is possible to update the same class with attribute rules and prevent infinite loops, I authored a post detailing this with an example.  Prevent Infinite loops in Attribute Rules https://www.esri.com/arcgis-blog/products/arcgis-pro/data-management/prevent-infinite-loops-in-attribute-rules   ... View more

The error "The requested operation is unsupported by instance db" often indicates that the geodatabase the UN is loaded on is not upgraded where some stored procedures maybe required by the application and they are not there. That explains why you are getting it on both enable and applyEdits.   Can you try running upgrade geodatabase from your current Pro?    Before you do that, take a screenshot of the current geodatabase version, I want to know what geodatabase version you are on because it is been years since I saw this error. You can find out by logging in as sde user and go to the properties. Expand Geodatabase version, upgrade status.   Then run upgrade geodatabase gp tool when you are ready.   If it works after that, will do some work to improve the doc.  ... View more

What version of Pro are you using? We should have yelled with a message that the sequence doesn't exist     ... View more