507
Like
Share
ReportSignificance of Configurable cascading behavior:
Basically configurable cascading is a type of relationship behavior which is not used primarily and it is used whenever the business required.
Scenario:
Below are the brief explanation of the scenario which is used during the migration of data from between MSCRM to MSCRM to assign the ownership correctly.
Generally Data migration is a bottle neck is to migrate all the transactional records and activities which is getting created on a daily basis to follow up with the customer.
During Data migration an extra care should be taken to migrate the activities from one environment to another environment without changing the owner of the activity records.
OOB [Out of box], all the activities are having a parental relationship with their parent entities and in this scenario we will consider Parental Relationship between Opportunity and all the activities.
Major activities are [Phone call, Fax, task, Email or any custom created activities].
Due to the Parental relationship between Opportunity and the activities, whenever the owner of the opportunity changes the child related activities owners will be changing automatically.
This will be fine when it is in single place and when we started doing the data migration from one version of MSCRM to another version, it will creates a problem. Whenever the activities are creating in another environment it will create with the owner of the parent record in the target even though the child record has different owner in the source.
Suppose Opportunity owner is A and A has created lots of activities and A would be the owner and for some reason A left the organization and B has become the Owner of the A related opportunity and when B started creating activities B will be owner of the creating activities and not for existing activities which are created by A.
But When we started proceeding for the migration the B owned opportunity will create and its related activities will go in the name of B not A since partial records owner was A. Here the data mismatch will come and to correct this data is huge and it will create a mess within the target system. Because business will generate reports out of this data.
Suppose if it is storing in the EDW[Enterprise Data Warehouse] for analysis purpose, it will not help much to do the analysis.
To avoid this mess during the data migration we need to change the Parental behavior to configurable cascading and make the CASCADE ALL to NONE for ASSIGN and then start doing the migration then the data will move to the target as it is without any change.
Once the data migration is completed and before the system goes for LIVE revert back the changes.
In our project we had tried this and it worked well.
*This post is locked for comments