Latest Contributions by HusseinNasser2

To add to this thread, when using Console with attribute rules we write a debug entry in both server manager logs and ArcGIS Pro Monitor diagnostics. This helps tremendously in debugging. Here is a simple example     This was first introduced in Pro 3.2/11.2 and the fix has been ported to the following patches - ArcGIS Pro 3.0.6 - ArcGIS Pro  3.1.3 - ArcGIS Pro 2.9.11 - ArcGIS Server 10.8.1 Utility Network and Data Management Patch 11 - ArcGIS Server 10.9.1 Utility Network and Data Management Patch 6 - ArcGIS Server 11.1 Utility Network and Data Management Patch 2 ... View more

Yes, you simply change the split model from update/insert to, delete insert insert     ... View more

This should not be possible , as NextSequenceValue simply queries the database for the next sequence (using .nextval) and databases often handle that really well.  It could be that the app is overwriting the value somehow via an update. Check the creation user/last updated for the duplicate unique id which one is newer is probably the duplicate, also to be safe make the field uneditable.  If you are using branch versioning or archiving you can use the history to investigate how the unique id happened to be.  Do you know what is the database?    ... View more

Edit: I went back to 2.9.11/ 3.1/3.2 and I'm getting the correct behavior (split only generates one sequence) Make sure when you test, create a new line feature, then do the split. this will generates a new sequence number for the line, but then the split will use the next value.  If you discard the edits the sequence is not returned (will be burned)   ... View more

posted a workaround ,can you try?  ... View more

Can we try the following?    When running python on a class with attribute rules you must specify all the fields required by the attribute rule in the python cursor.  Here is an example  I have a table with three fields a,b, and c. Field c has an attribute rule return $feature.b * 2. So the rule require fields b and c Because b and c are required by the attribute rules those fields must by passed to python as follows.         def update_standalone(fields): with arcpy.da.UpdateCursor(str(gdb / 'standalone'), fields) as cursor: for row in cursor: row[0] += 1 cursor.updateRow(row) print('Running') update_standalone(['a', 'b', 'c']) # Succeeds # passing only a will fail # update_standalone(['a']) # RuntimeError: Failed to evaluate Arcade expression. # passing only b will also fail # update_standalone(['b']) # SystemError: <method 'updateRow' of 'da.UpdateCursor' objects> returned NULL without setting an error # passing all fileds or the required fields for attribute rules will succeed # update_standalone(['a', 'b', 'c']) # Succeeds # update_standalone(['b', 'c']) # Succeeds print('Done')     ... View more

I think this might be a refresh issue in the table view, closing and reopening the table should refresh it (i'll make sure to log a bug to fix that) , but if you edit the map directly you can see the value changes instantly, I had this project with labeling and symbology on..  but here is a video along side the data.. works as expected   ... View more

This one is really interesting, just found another issue when you have more than 6 features to update, because we have a limit of the number of Arcade engines the script hit that limit pretty soon.     The only workaround to really fix this is to have an additional field, I added a field called isPush with a integer value. We want to essentially differentiate between a user update changing the pushvalue vs an automated attribute rule update.  You can hide the ispush field from users as it will only be used by the attribute rule.   if ($feature.ispush == 1) return {"result": {"attributes": {"ispush": 0}}};   Final script..    // calculed Field $feature.Helper // Triggers: Insert, Update // Exclude from application evaluation //add base condition if ($feature.ispush == 1) return {"result": {"attributes": {"ispush": 0}}}; if($originalFeature.pushvalue == $feature.pushvalue) return; var GID = $feature.GemeindeID var GLID = $feature.GlobalID // filter current featureset except the feature that is edited rn var SQL = "GemeindeID = @GID AND GlobalID <> @GLID" var sirenen = FeatureSetByName($datastore, "Sirenen", ["*"]) var filterSirene = filter($featureset, SQL) console(count(filterSirene)) var updates = [] for(var f in filterSirene) { if(f.GlobalID == $feature.GlobalID) continue; //don't update values that are the same to avoid recursion. if(f.pushvalue == $feature.pushvalue) continue; var u = { globalID: f.GlobalID, attributes: { Pushvalue: $feature.Pushvalue, ispush :1 } } Push(updates, u) } return { result: { attributes: { Pushvalue: $feature.Pushvalue} }, edit: [{ className: "Sirenen", updates: updates }] }     ... View more

Ok I forgot to deal with one more thing which is when the value is the same don't even attempt the update.   Tested this one locally and it worked.    // calculed Field $feature.Helper // Triggers: Insert, Update // Exclude from application evaluation //add base condition if($originalFeature.pushvalue == $feature.pushvalue) return; var GID = $feature.GemeindeID var GLID = $feature.GlobalID // filter current featureset except the feature that is edited rn var SQL = "GemeindeID = @GID AND GlobalID <> @GLID" var sirenen = FeatureSetByName($datastore, "Sirenen", ["*"]) var filterSirene = filter($featureset, SQL) console(count(filterSirene)) var updates = [] for(var f in filterSirene) { if(f.GlobalID == $feature.GlobalID) continue; //don't update values that are the same to avoid recursion. if(f.pushvalue == $feature.pushvalue) continue; var u = { globalID: f.GlobalID, attributes: { Pushvalue: $feature.Pushvalue } } Push(updates, u) } return { result: { attributes: { Pushvalue: $feature.Pushvalue} }, edit: [{ className: "Sirenen", updates: updates }] }     ... View more

Yeah your rule will trigger forever, just like in recursion you will need a base condition for your attribute rule.    And that is if pushvalue is the same, just no-op.   // calculed Field $feature.Helper // Triggers: Insert, Update // Exclude from application evaluation //add base condition if($originalFeature.pushvalue == $feature.pushvalue) return; var GID = $feature.GemeindeID var GLID = $feature.GlobalID // filter current featureset except the feature that is edited rn var SQL = "GemeindeID = @GID AND GlobalID <> @GLID" var sirenen = FeatureSetByName($datastore, "Sirenen", ["*"]) var filterSirene = filter($featureset, SQL) console(count(filterSirene)) var updates = [] for(var f in filterSirene) { if(f.GlobalID == $feature.GlobalID) { continue } var u = { globalID: f.GlobalID, attributes: { Pushvalue: $feature.Pushvalue } } Push(updates, u) } return { result: { attributes: { Pushvalue: $feature.Pushvalue} }, edit: [{ className: "Sirenen", updates: updates }] }     also for additional optimization (although you might have done on purpose for Editor tracking), add a filter to your sql to only push the different   var pushValue = $feature.pushvalue var SQL = "GemeindeID = @GID AND GlobalID <> @GLID AND pushvalue <> @pushValue"   ... View more

Thanks @Bud I used file just to support older Pro releases,  That being said, I just tried to upload a row mobilegdb but got an error (content type octet stream doesn't match file extension .geodatabase),   the change might take time to fully propagate   ... View more

There isn't an out of the box way to do it but you can script it with an options table as I show here https://community.esri.com/t5/attribute-rules-blog/how-to-toggle-constraint-and-calculation-attribute/ba-p/1387438  ... View more

There isn't an out of the box way to do it but you can script it with an options table as I show here https://community.esri.com/t5/attribute-rules-blog/how-to-toggle-constraint-and-calculation-attribute/ba-p/1387438  ... View more