Release Notes

The following new attributes have been added to clearMDM Reparenting Rules:

• Is Clone?
• Is Clone Prevent Delete?

Child Records can now be cloned (and parented to the Master Record) instead of updated. By default the original records are deleted, unless the “Is Clone Prevent Delete?” flag is set, in which case the original records are retained in addition to the new cloned records.

• Is Delete Failed Records?
• Delete Failed Records Keyphrase.

Where errors are encountered during Child Record update, the Reparenting Engine can now delete the failing Child Records. The primary use case here is where a unique constraint prevents the reparenting update and the retention of the original records causes record sharing issues. The keyphrase field can be used to specify a particular error condition to target for deletion.

The Remove Normalisation Rule Type can be used to remove all instances found of specified text tokens listed in a referenced Custom Setting. For example, the ” AND ” can be removed from Company Names to improve matching quality.

The clearMDM package now installs a Remove Values Custom Setting which can be populated and used as a reference for normalisation rules.

Scheduled data service processing can now be limited to specific data services. For example, Low priority data services can run daily and Medium priority data services hourly.

Note, real-time data service processing is unaffected by this enhancement.

The ISO Country Code list now provides a “Target Remove Start” attribute which can be populated with a list of prefixes to be removed from phone numbers before the international prefix is added.

For example with a Target Remove Start of 44 for UK.

44-0207990990, normalises to +44207990990 instead of +4444207990990.

The previously internal list of standard SObjectTypes supported for reparenting can now be managed via the MDM Home page (Manage Child SObject Types component).

The Master Record Update Platform Event is now published by Merge, Synchronisation and Reparenting Batch Jobs. Previously support was limited to real-time MDM processing.

This platform event supports myriad use cases including external system notifications and the invocation of on-platform process automations (i.e. Flow).

To enable event publishing, the “Is Platform Event Active?” checkbox should be ticked under Target Object Merge/Sync/Reparenting settings.

All package components have been upgraded to the Salesforce API version 57.0 and regression tested.

A new Target Object Merge Setting [Master Record 2nd Factor Priority] allows selection of Newest or Oldest recency/priority for the datetime field selected for Master Record 2nd Factor. Previously the 2nd factor implemented oldest logic by default.