WxC-DI Phased Migration BASL Feature
Overview
New feature in version 2.6.14 introduces a way to bulk change dependency objects to Customer level whilst object type still remains allocated to site. This page describes how to use this feature within the migration
BASL Types
To facilitate this we have introduced a new mapping table called BASL (Before Any Sites Loaded) Types, where we add dependency objects that are moved to customer (BASL) level during a phased migration.
The BASL Types reside under Mappings->Mapping Tables
By default, BASL Types contains a number of Object Types as per screen shot below. These may be added to or removed as required.
Using BASL Types in migration
During a phased migration, after as per normal, described in Migration User Guide wrangler_ WxC-DI Migration User Guide, going through the steps of
Creating Sites from Site Suggestions
Solving Validation Issues
Performing Target Mappings
Selecting Sites to Migrate
then revalidate or reallocate as requested by wrangler_
On completion of validation, there will be a rule triggered advising of detected objects that should be moved to Customer and before any sites loaded level. These objects may be viewed by selecting Review Objects, and if satisfied that all looks correct, select Update Objects bulk change button which will move all these objects to Customer and BASL
Review Objects to move to BASL
If OK with Review - select Update Objects
Post bulk change, you can check individual objects where you will notice a new field, Prepare & Load With and in Override Value column, you can here see that Change At has moved to BASL and Prepare & Load With now states CUSTOMER
Continue to solve all validation rules as required, then perform revalidation. Continue to Prepare step, select Start Prepare twice
Display Dependency issues by selecting the Source objects with issues link
Resolve these issues and restart execution, moving on to pre load stage.
You will need to perform another validation. Notice that you will again require an update of objects Bulk Change for dependency objects. in addition to other validation rules. Without solving any other validation issues, select Update Objects
Now Re-Validate Migration again
On completion of the validation, a number of sequential issues would have disappeared, now resolve any remaining pre load issues as per normal, Re-Validate Migration migration and proceed to load