Latest Contributions by HusseinNasser2

No worries, I confirmed this is fixed in Pro 3.1.     ... View more

@JohannesLindner  Can you try the filegdb case with Pro 3.1 Beta if you have access?  We have a known issue where Arcade might sometime fetch all the fields even a subset is provided.    ... View more

Your expectation is correct. Evaluate with changes - in version option should only evaluate features updated/inserted in the version.  We were able to reproduce locally and this seems to be a bug in Pro where if you close or minimize the error inspector the options won't persist while the UI continue to show you that it did.  We will try to address this in the next 2.9 patch.   As a workaround  1) Switch to your version 2) Remove the error layers  3) Close the error inspector 3) Save and close pro 4) Open the project back, Add error layer, then open the error inspector make sure the error inspector is on docked (not auto-hide)  5) Select the modify in version option and evaluate, should work.    ... View more

Hey Joel,  what was causing is  DeserializeEvaluateParams is a bug in Pro causing Evaluate to send a very large payload when def queries or subtype group layers are in the map.  This bug was fixed in Pro 3.1, ported back to 2.9.6 and will also be included in 3.0.4 for reference BUG-000153528 ... View more

It is not recommended to change the $feature attributes through edit dictionary, the AR loses context and you can get into cyclic triggers and infinite loops. No different than recursion in programming. Instead, set the field type to null and use the result dictionary object, this way we are able to update the attributes of the new feature in row buffer and flush it once to the database. After rewriting your attribute rule with this mind it works. I just changed asset_number to labeltext which is the field i had on my UN (see gif)          // MV Connector Line (Verbindingskabel) whithout Containment -> MV Substation if (($feature.labeltext == "associate")) { var update_class = 'ElectricDistributionLine' var update_class_asso = 'ElectricDistributionAssembly' var filterAssembly = "" var boundaries = FeatureSetByName($datastore, "StructureBoundary", ["globalid"], true); if (isempty(boundaries)) { return; //{"errorMessage": "Error 1"}; }; var intersectBoundaries = Intersects(boundaries, $feature); if (isempty(intersectBoundaries)) { return; //{"errorMessage": "Error 2"}; }; var structureBoundary = First(intersectBoundaries); if (isempty(structureBoundary)) { return; //{"errorMessage": "Error 3"}; } var AllAssemblys = FeatureSetByName($datastore, "ElectricDistributionAssembly", ["assetgroup", "globalid"], true); if (isempty(AllAssemblys)) { return; //{"errorMessage": "Error 4"}; } var XYassembly = Filter(AllAssemblys, filterAssembly) if (isempty(XYassembly)) { return; //{"errorMessage": "Error 5"}; }; var intersectAssembly = Intersects(XYassembly, structureBoundary); if (isempty(intersectBoundaries)) { return; //{"errorMessage": "Error 6"}; }; var assemblyGeo = First(intersectAssembly) if (isempty(assemblyGeo)) { return; //{"errorMessage": "Error 7"}; } return { "result": { "attributes": { "labeltext": "test" } }, "edit": [{ "className": update_class_asso, "updates": [{ "globalid": assemblyGeo.globalid, "associationType": "container" }] }] } }   ... View more

 You need to have an exit condition, Attribute rules in this case is no different than recursive function.    If you are updating object 3833, with value "Bem 3833", you might want to do a check first before doing the update. If the value is good exit the script else continue      var dangleDistance = 1000; var feature_ = $feature; //query objectid 3833 var fs1 = Filter($featureset, "objectid = 3833 AND BEMERKUNG = 'Bem 3833'"); var f = First(fs1); //if is null, means feature 3833 doesn't have the value Bem 3833.. contiue to update. //if is NOT null, it means the value already there, just exist if (f != null) return; //quit the script //else update the feature return { "result" : { "attributes": { "BEMERKUNG": "test 23" } }, "edit": [{ "className": "HydroEdgePro", "updates": [{ "objectID": 3833, "attributes": { "BEMERKUNG" : "Bem 3833" } }] },{ "className": "arcade_log", "adds": [{ "attributes": { "Value": "test" } }] }] } ... View more

It seems that the feature triggers a rule that updates itself that triggers, which then retriggers the same attribute rule leading to an infinite loop and thus this error.  If you want to update attributes in the same feature you can use the result keyword instead of updates.     return { "result": { "attributes": { "BEMERKUNG": "test 2" //this update goes to the $feature } }, "edit": [ { "className": "arcade_log", "adds": [{ "attributes": { "Value": "test" } }] }] }     ... View more

Edit: And @JohannesLindner  spotted it before I did, to consume the geometry of a feature that has been queried, the featureset should be created with return geometry set to true.    It is a good practice to always check for null when you call `first`, First can return null if the featureset is empty, which can cause subsequent code to fail. And just to be safe, because the error is pointing in line 18 the geometry of the line might be null here so add a check for that too.      var line = first(x) //check if line is null if (line == null) return; //do nothing var geom = Geometry(line) if (is_empty(geom )) return; //check if the geometry is null       Now to explain "well it worked in 2.9 why does it fail in 3.0". To validate an Arcade script , AR picks a row in the table and makes that row $feature to do the validation against. It could be the case the 2.9 gives a different row than 3.0 and resulting in a failure in your script.         ... View more

As long as your rule is NOT excluded from client evaluation (there is a checkbox on the rule, leave it unchecked) and you have auto apply turn off (which is the default) then the attribute editor should not rollback the changes and will give the user the ability to fix their mistake. This means that edits are not sent to the database and processed locally in the attribute editor pane.      your rule should also have return true; at the end otherwise it will always fail.   ... View more

The only way to run an attribute rule manually is to use batch calculation rule using Evaluate method.  For your use case however, I think you can still use immediate calculation rule and have a special field in the class (call it trigger (true or false)) when creating a feature have the trigger default to false and only when you flip the trigger field to true the rule can execute.    The rule will look something like this   if ($feature.trigger == 'true') return NextSequenceValue('seq'); return;   This is another way you can execute the rule manually.      ... View more

Yes that would be helpful thanks.  I want to know where the problem actually is and fiddler log will help (fields map might be sending incorrect request and I want to capture that),  try reproducing in Pro, do the same edit there and see if you see the behavior.    Try excluding from application eval too and test again in fields map ,  ... View more