When the destination model contains an object with the same name as an object being migrated but which does not share common ancestry with the like-named object, migration renames the object being migrated before adding it to the destination model. The destination model then contains the renamed object that shares common ancestry with the object in the source model plus the unrelated object that only happens to have the same name as the source model object.
The convention for renaming the object being migrated when a duplicate name is encountered is to add a dash and the object's Object ID (for example, Customer-12345). The name of the object already in the destination model is unchanged. For example:
|
Model Version |
Before Migration |
After Migration |
|---|---|---|
|
Source Model |
Customer Object ID: 12345 Original Object ID: 12345 |
Customer Object ID: 12345 Original Object ID: 12345 |
|
Destination Model |
Customer Object ID: 67890 Original Object ID: 67890 |
Customer Object ID: 67890 Original Object ID: 67890 and Customer-12345 Object ID: 94034 Original Object ID: 12345 |
When aggregate objects in the source model and destination model have different names and common ancestry, migration replaces the name in the destination model with the name in the source model. For example:
|
Model Version |
Before Migration |
After Migration |
|---|---|---|
|
Source Model |
Client Object ID: 12345 Original Object ID: 12345 |
Client Object ID: 12345 Original Object ID: 12345 |
|
Destination Model |
Customer Object ID: 56789 Original Object ID: 12345 |
Client Object ID: 56789 Original Object ID: 12345 |
Difference in the name but common ancestry can occur if an aggregate object has been previously migrated and then renamed in either the source or destination model. The subsequent migrations for such objects overlay the name of the object in the destination model.
|
Copyright © 2013 CA Technologies.
All rights reserved.
|
|