Latest Contributions by HusseinNasser2

I appreciate the work MVPs are doing here in the community, especially in the attribute rules section which is getting lots of traction thank you !  ... View more

This bug will be addressed in 3.1.2  Please use BUG-000157390 for tracking.  ... View more

Good catch @JohannesLindner updated post thanks!      ... View more

Hey  James   FeatureSetByName you are only asking for the ZIP5 to be returned, but then you are attempting to access. the zipcode field.   To fix this add the zipcode field. See if that helps. That is something we fixed in 3.1 where in some cases prior releases we were fetching all fields regardless of what you asked it to, which is why you script worked before but no longer does.    var zip = FeatureSetByName($datastore, 'ZipCodes', ['ZIP5', 'zipcode'], true); var intersectLayer = Intersects(zip, Geometry($feature)); if (Count(intersectLayer) > 0) { var layer = First(intersectLayer); return layer['zipcode']; } else { return null; }   ... View more

Hello, let me add context to why you are getting this object not found error at least in this particular case. Simplifying the script you have to the following there is a condition that when met, you define a variable inside the if block and set it to a value.  Later outside the scope of the if block you do another if and use that variable. This is variable scoping, the variable isLeft will only be defined if the first condition is met   Now if the first condition was not met, the variable isLeft will never be defined and the second if will fail with isLeft object is error. This is because Arcade has inherited its behavior from Javascript.        Why did this work in 3.0 and not in 3.1? Well I could argue that the script may also fail in 3.0 or any release as well if $feature happened to not satisfy the first condition which leads to the variables to not getting defined. I think you can reproduce this in 3.0 by creating a feature outside Test_Jurisdictions.  So the real solution for more predictable script is to define the scripts outside the scope. that is move isLeft and IsRight so they are at global scope if you are planning to use them across the script.      If there are any other cases where the script fail but the syntax looks correct please post it in the this thread and we will take a look.  Hope that clarifies it. Thank you and apologies for the late reply.   ... View more

If you use FeatureSetByname with $datastore and exclude the rule from application evaluation, the rule should work on the server as long as the container (assembly I assume?) is in the workspace which it should be in case of the UN.   if those are related with containment associations you can use FeatureSetByAssociation  https://www.esri.com/arcgis-blog/products/utility-network/data-management/featuresetbyassocaitions-new-utility-network-arcade-api-to-work-with-associations-2-5-10-8/   ... View more

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