Previous Topic: Aggregate Objects Listed As SameNext Topic: Maintain Aggregate Sets and Model Families


Aggregate Objects Listed As Different

Assume that the entity type CUSTOMER is updated in the source model.

When the change occurs, a new session is created and the entity type in the source model is now associated with that new session.

An example of aggregate objects existing in both models but in different versions is as follows:

Aggregate Objects Listed As Different

Report Results: The Compare Aggregate Objects Report indicates that entity type CUSTOMER in the source model is different from entity type CUSTOMER in the destination model. Objects with the same Original Object IDs are evaluated as different when their Session Change Date and Change Time are different.