Migration can delete objects in the destination model-whether you intend to delete them or not. For example, if Entity Type A exists in the source and destination models and its Attribute C is deleted from the source model, migration deletes Attribute C from the destination model.
If Attribute C is not referenced in the destination model-has no usages-the deletion of Attribute C causes no problem, and the migration can proceed. However, if Attribute C is referenced in the destination model (for example, in an attribute view), the migration terminates and all object actions are rolled back.
See details on the migration error message in the Object Cannot Be/Must Be Deleted section.
You want to generate a Trial Migrate to avoid unintended results although Trial Migrate requires more time to process.
If a deletion by migration creates a problem, try migrating the parent object of the deleted object. (Usually you migrate only the directly changed aggregate objects and not their parents.)
If migration of the parent object does not solve the problem, checkout an appropriate subset from the destination model and delete the object, or use the Host Encyclopedia's Delete Object function.
|
Copyright © 2013 CA Technologies.
All rights reserved.
|
|