Managing Dependent Objects

Many ISA objects depend upon other objects. This means that you access dependent objects through the properties of their parent object. Keep the following considerations in mind as you manage these dependent objects in your code:

• When adding an object that contains a reference to another object or when modifying the name of the referenced object, ISA attempts to verify the existence of the referenced object. If the referenced object cannot be verified, the operation fails.
• For example, the following code

  MySiteAndContentRule.SetDestination fpcSpecifiedDestinationSet, "Sports Destinations", fpcArrayScope
  

  adds a new destination set to a site and content rule. This code fails if the FPCDestinationSet collection named "Sports Destinations" has not been previously created. See Restricting Site Access for a fuller example of adding a destination set to a site and content rule.

• When removing an object that is referenced by another object, ISA checks all instantiated objects to learn whether there are other references to the deleted object. If such references exist, the operation fails.

For example, if the FPCDestinationSet object named "Sports Destinations" is referenced by more than one FPCSiteAndContentRule object, code that removes the destination set will fail. If no other object references the destination set, "Sports Destinations" will be removed successfully.