Latest Contributions by HusseinNasser2

Your attribute rule is correct, the problem is the order of operations and how the relationship record is created. This is something we are trying to address. Relationships are created after attribute rules.  When you add the related record, the related foreign key `.PARENTGUID`  is not populated, so when the insert attribute rule gets triggered, the foreign key .PARENTGUID is null, which of course will fail to find the parent and fail the edit.    Two workarounds,  you can add the relationship record directly to the table and during that insert fill in the parentGUID , this will cause the Insert trigger to have the parentGuid and the rule should work. Another workaround is to make the attribute rule on update and tell users to make a physical update to the related record (update a field etc.. ) to force trigger the update attribute rule.    I understand the workarounds might not be ideal, we are working on a solution not sure how long it will take though.    ... View more

Think of the dictionary you are authoring as creating an association from $feature to whatever feature you specified in the update_class. Specifying FROMTERMINAL means here you are trying to create an association from the $feature so that terminal should exist on that feature.    If the terminal you are connecting to is at the device then use ToTerminal. and you can safely use the string name  A blog detailing this can be found here.  https://www.esri.com/arcgis-blog/products/utility-network/electric-gas/advanced-attribute-rules-creating-utility-network-associations-with-attribute-rules/   As Mike said, you can also use  ^UN_Association if you want more control. (create associations between two assets other than $feature.    Hope that helps ... View more

Bug can be tracked here BUG-000151193 ... View more

It looks like a bug reading the shape_length st function in the client side. I assume you are consuming the SQL Server feature class through a feature service? I can't reproduce this when running direct connect.   We will look into it, meanwhile as a workaround, try Excluding the Attribute rule from application evaluation and restart the service, that should do it. That will skip the client side evaluation and only do server side which we know it works.     ... View more