Release Notes

clearMDM Summer 25 (v9.41) Release Notes.

Use this URL to install the package into any organization:

https://login.salesforce.com/packaging/installPackage.apexp?p0=04tKk000000sykA

Note: If you are installing into a sandbox organization you must replace the initial portion of the URL with http://test.salesforce.com

Use of clearMDM is subject to our terms and conditions.

The ability to be able to create multiple MDM configurations for a Salesforce Object and choose which to apply for Jobs or realtime has been added in the Summer 25 release.

Within the MDM Settings, you can ‘Save as’ Target Objects and Data Sources allowing the creation of multiple configurations for the same Target Object. This is particularly useful when there are multiple Record types per Object. More information can be found here.

You can now rename a Target Object, which was previously not possible. This will update the Data Source, Attribute Groups, Data Services and Custom Rollups associated with that Target Object.

Use this URL to install the package into any organization:

https://login.salesforce.com/packaging/installPackage.apexp?p0=04t4w000000p6Vd

Note: If you are installing into a sandbox organization you must replace the initial portion of the URL with http://test.salesforce.com

Use of clearMDM is subject to our terms and conditions.

When scheduling a Matching or Synchronisation Job, a Blocking Key can be selected (when more than one exists) to use in the MDM Operation. There is also the option to select ‘All’, which will validate against all 3 Blocking Keys, and continue to do so until all 3 have been checked.

The following blog post provides further detailed information.

When creating a Blocking Key Process Request, there is the option to select ‘Is Multiple Blocking Keys?’ and the ‘Blocking Key Sequence’, e.g. 1, 2 or 3. If This field is selected and the Blocking Key Sequence of 2 is entered, the Blocking Key Process Request will start looking for Matches on Blocking Key 2, then 3 then 1.

The following blog post provides further detailed information.

clearMDM Spring 25 (v9.27) Release Notes.

Use this URL to install the package into any organization:

https://login.salesforce.com/packaging/installPackage.apexp?p0=04t4w000000p6V9

Note: If you are installing into a sandbox organization you must replace the initial portion of the URL with http://test.salesforce.com

Use of clearMDM is subject to our terms and conditions.

The Find Matches UI now displays a ‘Blocking Key for Matching field’ that allows the filtering of the Blocking Key for Matching when the Find button is selected. There is also the option to select ‘All’ which will look for Matches on all Blocking Keys.

Only Matches above the specified Match threshold are displayed, although you can select the ‘Return Non Matches?’ checkbox to display those below the threshold.

Potential Matches only displays records that have Matched according to the Match threshold, not those below this threshold.

The Account Merge UI now displays the Parent Account ID as a Name link and the Contact and Supplier Merge UI displays Account ID as a name link. Previously these were record ID links.

A new setting within Data Source settings has been added to address non reparentable Child Objects. The setting ‘Is Clone Reparenting?’ defaults to ticked where the Child Object does not have a master relationship.

clearMDM Winter 25 (v9.14) Release Notes.

Use this URL to install the package into any organization:

https://login.salesforce.com/packaging/installPackage.apexp?p0=04t4w000000p6BJAAY

Note: If you are installing into a sandbox organization you must replace the initial portion of the URL with http://test.salesforce.com

Use of clearMDM is subject to our terms and conditions.

New Matching functionality for Winter ’25, described via the blog post linked below.

Multiple Blocking Keys

Use this URL to install the package into any organization:

https://login.salesforce.com/packaging/installPackage.apexp?p0=04t4w000000p630

Note: If you are installing into a sandbox organization you must replace the initial portion of the URL with http://test.salesforce.com

Use of clearMDM is subject to our terms and conditions.

The new manual Merge UI supports attribute groups and both the master record selection and field selection defaults driven by the configured rules. As such the default display is exactly how the automated processes would merge the data, however the Merge UI allows selections to be changed or overrides added.

The MDM Reparenting operation now supports a Deep Clone mode where the child object relationships for losing records can be traversed recursively to establish a complete hierarchy of records at the master record level irrespective of whether the relationship type is master detail (non-reparentable) or otherwise.

The Merge Now function available in the data stewardship UI now supports child record reparenting and the Deep Clone functionality noted above.