AnsweredAssumed Answered

Creating composite relationship class that removes the condition of Deleting origin deletes Destination feature/record.

Question asked by bsanders69 on Feb 23, 2018

I love all of the other concepts behind the Composite relationship such as move and rotate destination feature with origin, but the delete in every case should have the option to be disabled.  This may work for related table records where the information is no longer needed, but there are spatial reasons to keep the destination feature.  The other options are excellent...rotation and move, but there are cases where you don't want them deleted as they are re-used.  For example...Poles have Streetlights or Poles have Signs.  Someone may drive into a pole causing for the pole to be replaced, but the attachments (signs or streetlights in many cases are undamaged and will just be re-attached to the new pole). 


Thanks in advance for you comments,