Migration Rules › Usage and Applicability › Aggregate Object Expansions › Special Case Examples: Data Views and View Matching When USING Action Block is migrated

Special Case Examples: Data Views and View Matching When USING Action Block is migrated

In the following situations, Action Block A is an action block that is directly or indirectly selected to be migrated and Action Block B is another action block.

• View Match Copied

  Action Block A uses Action Block B in the source model.

  A View Match exists in the source model between a view in Action Block A and a view in Action Block B.

  Action Block B exists in the destination model.

  The View in Action Block B exists in the destination model.

  The View Match does not exist in the destination model.

  Result: The View Match is copied to the destination model.

• View Match Replaced

  Action Block A uses Action Block B in the source model.

  A View Match exists in the source model between a view in Action Block A and a view in Action Block B.

  Action Block B exists in the destination model.

  The View in Action Block B exists in the destination model.

  The View Match exists in the destination model.

  Result: The View Match is replaced in the destination model.

• View Match Not Copied

  Action Block A uses Action Block B in the source model.

  A View Match exists in the source model between a view in Action Block A and a view in Action Block B.

  The Action Block B exists in the destination model.

  The View in the Action Block B does not exist in the destination model.

  Result: The View Match is not copied to the destination model.

• View Match Deleted

  Action Block A uses Action Block B in the source model.

  A View Match exists in the destination model between a view in Action Block A and a view in Action Block B.

  The View in Action Block A does not exist in the source model

  OR the View Match does not exist in the source model.

  Result: The View Match is deleted from the destination model.