Migrating to the Data Model Based on the Party Table
Migrating to the Data Model Based on the Party Table
Customer 360
versions 10.2 HotFix 2 and later use the data model based on the Party table. If you upgraded to 10.2 HotFix 2 or use
Customer 360
version 10.2 HotFix 1 or 10.2, then
Customer 360
uses the data model based on the Party Role table. You can now migrate from the data model based on the Party Role table to the data model based on the Party table.
If you do not want to migrate to the data model based on the Party table, you can continue to use the data model based on the Party Role table.
Promote the
update_foreign_keys.change.xml
change list.
Validate the
Customer 360
Operational Reference Store.
Update foreign keys and recalculate the best version of truth for the records.
Validate the
Customer 360
Operational Reference Store.
Promote the
party_updates.change.xml
change list.
Validate the
Customer 360
Operational Reference Store.
If you extended the data model, import the data model extensions.
Reindex the data.
Deploy the updated
Customer 360
components.
Reconfigure the values for the Full Name row in the Hierarchy Manager.
Remove the post-merge user exit.
Delete the shards and the ZooKeeper data directory.