Latest Contributions by HusseinNasser2

‎10-30-2025

I'm not sure if the user workflow allows it but I would suggest using the option to keep the original features and let the attribute rules do the delete instead of the merge tool. This gives you more control as it turns the operation from a delete , update. To an update only and you will write the rule to trigger on update on geometry (use the triggering fields to set the rule to trigger only on the shape change) on the update you will have the control to query the original features (since they won't be deleted) and copy any attribute you want off of it. And then later you can insert the logic to actually delete the original feature. My guess as to why you are losing your update is as you suspected the order of the operations causes your update to be lost/ not persisted.

‎10-23-2025

Hey Mike, if you use the Evaluate Rule gp tool and select the features you want to evaluate , the tool will only evaluate selected features. This isn't currently available when evaluating through error inspector

‎10-14-2025

Make sure to pass in the correct layerid to queryDataElements that belongs to the Utility network layer, if you don't know it you can pass in empty string and that will pull all definitions of all layers which includes the utility network layer. sourceId should be there, if its not, the UN likely wasn't published. Go to to the feature service root json definition and look for utilityNetworkLayerId to see if its published.

‎09-08-2025

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.

‎09-03-2025

My colleague Koya has just published a blog detailing how you can performing snapping with Attribute rules. Wherever you are, web, mobile, Pro, edits you make can be made more accurate, and it is configurable. Amazing the stuff you can do with attribute rules. Give it a read! https://www.esri.com/arcgis-blog/products/utility-network/arcade/snapping-with-attribute-rules

‎08-27-2025

I can't tell what is going on but let us verify few things 1) Change the server logs to debug and see if you have entries for attribute rules being evaluated. 2) Does full extent work? 3) create new features and then evaluate them do they get picked up? if that doesn't work Finally try the following. Delete the validation rules, delete the error tables, then add the validation rule again, this will generate the error tables. Makes sure you are using a branch version workspace when you do that. Then delete the feature service and create new map, add your layer and the error tables and publish with the validation server, create a new feature service and test that new feature service..

‎08-12-2025

I would recommend not writing to the association table directly as it can be error prune. Instead use the provided attribute rules dictionary APIs I authored a blog about it https://www.esri.com/arcgis-blog/products/utility-network/electric-gas/advanced-attribute-rules-creating-utility-network-associations-with-attribute-rules for more advanced cases use this keyword Read more here about "^UN_Association" https://pro.arcgis.com/en/pro-app/latest/help/data/geodatabases/overview/attribute-rule-dictionary-keywords.htm

‎08-11-2025

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.

‎08-08-2025

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

‎08-05-2025

If you are looking for junction Edge associations you should use featureSetByAssociation($feature, 'junctionEdge') "Connected" is only for JJ associations

‎07-25-2025

Alot of customers came to me after the demo I did on the UC 2025 asking for the recording (Which we don't do), so I promised a blog post with code and data instead. Hereit is https://www.esri.com/arcgis-blog/products/arcgis-pro/data-management/batch-work-order-generation-with-attribute-rules-uc-2025-demo

‎07-24-2025

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

‎06-30-2025

Reposting this article I authored back in 2021 for visibility as it is not easily searchable. In it I discuss the best practices of authoring and configuring attribute rules. Hopefully you found it useful. https://community.esri.com/t5/attribute-rules-blog/attribute-rule-authoring-and-configuration-tips/ba-p/1023745

‎05-16-2025

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.

‎02-07-2025

What version of Pro are you using? We should have yelled with a message that the sequence doesn't exist

Online Status	Offline
Date Last Visited	‎03-19-2026 06:14 AM

My Ideas

Latest Contributions by HusseinNasser2

Re: Attribute rule to merge road centerline address ranges

Re: Issues with Using Attribute rules to assign parcel number in the Parcel Fabric Service

Re: How do I find a list of networksourceid?

Re: Error inspector

Snapping with Attribute Rules

Re: Validation Rules on Feature Layer (branch versioned) can be triggered but no results

Re: Deleting and creating a containment association within calculate attribute rule

Re: Error Inspector: Make the 'Modified in this version' option the default parameter when evaluating rules - Status changed to: Already Offered

Re: Attribute Rule [Constraint]: Combining GetUser + third action. Action not recognised

Re: Issue with Fetching Connectivity Association using Arcade

UC 2025 Demo - Work order generation with Attribute Rules

Re: When a feature is edited, update a different feature in the same FC - Status changed to: Already Offered

Attribute Rule Authoring and Configuration Tips and Best Practices

Re: enable utility network topology errors

Re: General Evaluation Error

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

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

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

Split with Attribute Rules

Temporarily Disable Attribute Rules