Latest Contributions by HusseinNasser2

Yes this is definitely possible, Assuming two tables T1, T2 , T1 is related to T2 via field KEY you will add an attribute rule on T1  and you can have it trigger on update so that it makes an edit to T2 and update the related feature on T1 (find the parent feature by querying T1.KEY = $feature.KEY ..   Here is a blog detailing this  Advanced Attribute Rules – Editing features on another class with attribute rules  You can restrict the attribute rule to execute only if a certain field has been updated by using $originalFeature  ... View more

Glad it helps Vish!  Junctions and Devices with no terminals are identical, The difference between junctions and devices are as follows 1) Junctions cannot have terminals while devices can  2) Junctions cannot participate as subnetwork controllers while Devices can I do see your point though with regards to modeling, if you have don't need terminals should you go with a junction or a device. I personally don't see a difference you can choose any. however if you modeled it as a device, you can add terminals later by changing the definition of the device (AG/AT) and magically all your devices now have terminals. You do however need to do some clean up on the data to assign lines/associations to the correct terminals after doing that. If you model it as a junction and then decided to add terminals later you will have to delete all your junctions and physically insert devices in their place and also do the cleanup part to assign terminals correctly.  Hope that helps Hussein ... View more