Latest Contributions by HusseinNasser2

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

My guess is you might need to account for empty geometries , line 26 points to this  "paths": json["rings"],   which essentially means it couldn't find the "rings" property in the geometry object you sent to the function. So either you are sending something else (which your code doesn't look like it) or one of your features have an empty geometry that was recently added that broke your script..    try updating this function with this  function polygonToPolyline(p) { var json = Dictionary(Text(p)); if (!haskey(json, "rings")) return; if (!haskey(json, "spatialReference")) return; var polylineJSON = { "paths": json["rings"], "spatialReference": json["spatialReference"] }; return Polyline(polylineJSON) }   Now this script may cause other downstream failures so you might want to handle the empty geometry across the rest of the script.  ... View more

Can you try installing fiddler and capture the applyEdits call? What does the response looks like?  Pro should refresh the map with updated features on the backend, the applyEdits returns a payload called "ServiceEdits" which tells the client the updates that have been made to the server (this includes attribute rules ) Capture what the request parameters (there should be returnEdits or returnServiceEdits parameter) and in the response there should be the edited features payload  ... View more

I know this is an answered post but just adding this for additional info.  I wrote up a post to explain why. Why FeatureSetByName doesn't work with variables https://community.esri.com/t5/attribute-rules-blog/why-featuresetbyname-doesn-t-work-with-variables/ba-p/1541572  ... View more