Migrating data enhancement rules with input field changes
When you update a data enhancement rule that you already migrated to another organization, migrate the updated rule association first, and then migrate the updated data enhancement rule.
If you rename or delete fields, or change field data types in a process or a Data Quality rule specification, the data enhancement rules that use them don't automatically reflect those changes. You must manually remove the outdated field mappings from the associated rule associations and then save the data enhancement rule with the updated process or rule specification.
When you migrate the updated data enhancement rule and rule associations together to an organization where the same assets with the outdated mappings exist, the rule associations fail to load. This issue occurs because the rule associations still contain outdated field mappings. To avoid this issue, migrate the changes in two stages.
1Migrate the affected rule associations.
aIn the source organization, remove the outdated field mappings from each affected rule association.
bExport the rule associations and then import them into the target organization.
cVerify that the rule associations in both organizations are free of references to fields that no longer exist.
2Migrate the affected data enhancement rule.
aIn the source organization, refresh the data enhancement rule and save it with the updated process or rule specification.