Latest Contributions by HusseinNasser2

‎07-07-2022

This session focuses on best practices deploying Attribute Rules on enterprise systems. This includes details of how to identify and fix slow running rules in the entire stack, run-away recursive attribute rules, attribute rule execution during branch versioning reconcile, client side execution of attribute rules, and more. https://mediaspace.esri.com/media/t/1_gr7hrdjy

‎04-05-2022

Hey @Zoggo would you mind sharing the following info? The version of ArcGIS server? How many total number of features in the class? The registration type of the class (unversioned/branch etc.) Can you monitor the ArcSOC as you execute the evaluate call and see how much it reaches before the SOC crashes?

‎03-24-2022

Hey @ASHAFFER would you mind sharing the attribute rule script along side the error you get during execution? thanks

‎02-07-2022

That should be possible, you need to add an attribute rule to the related table. One thing to watch for is cyclic execution and infinite loops. (Parent updates child, child turns out updates parent, which turns out and update child and that goes on.) We detect and protect against such cases but you will need to write the rules such that it has a base condition to quit.

‎01-20-2022

Which Pro version? Does the class have batch calculation or validation rules (check the datasource to see if GDB_Validationxxxx classes exist) Which data source is this ? (filegdb/mobilegdb/enterprise feature service?) Note that the add error layers only work through mobilegdb/filegdb and in feature services after consuming the feature service which has a validation capability enabled. this video might help https://www.youtube.com/watch?v=HFHJFCn2E1M

‎12-13-2021

This is happening because the AR tried to use a field that was not fetched by python. Two solutions, you can wrap the python call with arcpy.da.Editor(str(workspacepath)) which will give the editor context. or you can include all the fields that the AR require in the UpdateCursor call (cptraceability) in this case.

‎10-25-2021

When you share a webmap with named trace configuration, the GUIDs of the trace configuration is persisted in the webmap definition along side the utility network layer. The full definition of the trace configuration can be retrieved through the UtilityNetworkServer by passing the GUID to /trace. This is so that you can alter the trace configuration without republishing the webmap and also to keep the definition of the webmap compact.

‎10-22-2021

I just pushed a fix for few bugs that I found, can you try again? https://github.com/hussein-nasser/un-js-api-demo/blob/master/un-js-api-demo.html

‎10-08-2021

Can you try your rule on a FileGDB? see if you experience the behavior. If you don't, then we know this bug was fixed in 2.8 and Enterprise 10.9 will have the fix.

‎10-08-2021

Hey Billy, Do you know which ArcGIS Pro/Enterprise you are running? We had a bug with Null persistence in Arcade that we fixed in Pro 2.8 (Enterprise 10.9).

‎10-04-2021

Hey Anthony This is a known bug, the error layer of validation server should be included and packaged in the project package. They are currently not packaged (you get an error when you try) and you will have to add them manually every time. Edit: Bug number BUG-000151105 -Hussein

‎10-01-2021

AmirBar-Maor from the parcel fabrics team wrote a cool attribute rule that allows you to auto-snap to the feature near by after creating or updating a feature. In 2.7, we added the ability to assign an attribute rule to the shape field, which will allow the Arcade expression to return a geometry to update the $feature geometry. This opens up all sorts of workflows, including the one Amir built, which is the snapping. I thought it the attribute rules community will enjoy this https://community.esri.com/t5/arcgis-parcel-fabric-blog/using-attribute-rules-to-update-the-line-geometry/bc-p/1103951

‎09-07-2021

The utilitynetwork layer id will be different for each feature service. You can find the utility network layer id dynamically for any feature service (if it exists) by querying the feature service definition.

‎09-07-2021

You can call `queryDataElement` rest call on the feature service and provide the utility network layer id. https://server.esri.com/server/rest/services/service_name/FeatureServer/queryDataElements [13] is the utility network layer id You can find the utility network layer id querying the feature service definition and looking up utilityNetworkdatasetId "controllerDatasetLayers": { "utilityNetworkLayerId": 13 },

‎09-02-2021

Hey Billy I suggest reading the blog I authored on this topic. It has basic examples of creating associations of all types using attribute rules. The rule you have is so large to debug without the data. I suggest starting with a simpler rule to narrow down whats wrong. It might help to work with a file geodatabase so altering and testing the rule is easier. Then deploy it to enterprise. https://www.esri.com/arcgis-blog/products/utility-network/electric-gas/advanced-attribute-rules-creating-utility-network-associations-with-attribute-rules/

Online Status	Offline
Date Last Visited	‎06-02-2026 09:20 AM

My Ideas

Latest Contributions by HusseinNasser2

Attribute Rules - A Deep Dive (Dev Summit 2022)

Re: Validation Service with Attribute Rule kills ArcGIS Server

Re: Help Needed - Calculating Geometry in Current Environment

Re: Attribute rule to actively transfer data from a related table to it’s parent feature class and vice versa

Re: I Cannot activate "Add Error Layers"

Re: Attribute rule error on python updatecursor

Re: Share named trace configuration in webmap - missing JSON parameter

Re: Share named trace configuration in webmap - missing JSON parameter

Re: Update Field with Date Type to Null Value

Re: Update Field with Date Type to Null Value

Re: Error Layers - Branch versioned datasets

Auto Snapping with Attribute rules during Editing

Re: How do I find a list of networksourceid?

Re: How do I find a list of networksourceid?

Re: Utility Network Junction-Junction Connectivity Association

Re: Edit operation failed. Message: Cannot acquire...

Re: Attribute Rule [Constraint]: Combining GetUser...

Re: Attribute Rule [Constraint]: Combining GetUser...

Re: applyEdits in squence - FeatureService vs. Lay...

Split with Attribute Rules