If an adoption is not performed, you may not need to adopt. For example, if you reverse the adoptee and related models in the preceding example showing adoption that is not performed, Model 2 becomes the related model, Model 1 becomes the adoptee model, and Entity Type Client is adopted.
Important! Performing the adoption shown in the following illustration could cause you to lose common ancestry with objects in other models for the Entity Type Client. This approach is not recommended but is shown to illustrate another aspect of adoption.
In this case, duplicate Original Object IDs will not be created for Client, so the adoption succeeds. The link between Client in Model 1 and Customer in Model 2 is broken. Because of the name match, a new link would be established between the two Client Entity Types.
|
Copyright © 2013 CA Technologies.
All rights reserved.
|
|