Migrate Model from One Model to Another › Understanding Migration › Effect of Subsetting Protection on Migrations

Effect of Subsetting Protection on Migrations

The effects of subsetting protection on migration follow:

• A migration fail if the aggregate object or any of its components are checked out with Modify or Delete authority in the destination model.
• A migration fail if the aggregate object's companion or enabling objects are checked out with Delete authority in the destination model.
• If the migration would cause the deletion of any object from the destination model, that object may not be checked out for delete, modify or access. The migration can proceed if the object is checked out with Read Only protection.

Note: The effect of subsetting protection on migration suggests guidelines: (1) Try to avoid using full expansion of subsetting scoping objects, and (2) Restrict delete authority on common occurrences of entity types such as Customer.

One way to determine if your migration can succeed is to ask: Could I create a subset from my destination model with my aggregate object as my scoping object and not have any of my access requests downgraded when I expand the subset? If the answer is yes, the migration succeed.