It is important to realize that objects in different models that share the same name and object type can not be logically the same. If you have any doubt that objects with the same names should be made equivalent, take the necessary precautions to verify whether the objects are intended to be independent or intended to be equivalent. You can use Public Interface views or download the models and examine the objects in question. If you discover any objects with the same name that should remain independent and retain their separate ancestry, avoid using the Adopt All option with the models that contain these objects.
There are two scenarios where such false candidates can be detected from a Compare Aggregate Object Report. Proceeding with adoption in one case has no ill effect; Adoption ignores the request to adopt and reports IGNORED on the Trial Adoption or Adoption report. Proceeding with adoption in the other case will result in removing the common ancestry the target object had with an object in the source model with a different name; Adoption honors the request to adopt and reports ADOPTED on the report. This section describes each of these scenarios, both with Compare Report entries to be on the alert for, and an illustration that depicts the technical perspective.
|
Copyright © 2013 CA.
All rights reserved.
|
|