Apply the package.

Apply the package

Bug Fix: Filtering with Select All

Previously, when applying a text filter in the Data Quality or Duplicate Data Steward views, the Select All action was incorrectly applied to all records instead of only the filtered results. This issue has been resolved in this release.

Step 1: Check

Step 2: Apply the upgrade

Apply the package

New Score Meter: Review & Fix Everything in One Place

The Score Meter has been redesigned to simplify your workflow and make issue resolution faster and more intuitive:

• Before: You had to switch between the Score Meter and the Bot to review and apply corrections.

• Now: Everything happens directly in the Score Meter — review, select, and apply corrections all in one place.

• New interface: Cleaner, clearer, and optimized for batch actions. You can now apply changes to 1 / some / or all suggestions with just a few clicks.

No more back and forth. Just smarter data review in a single streamlined experience.

Try it out now and speed up your remediation process!

No migration step when upgrading from 3.58x.

Apply the package

Fix some display issued on Cross Merge Field Rules.

• Add missing permission set for duplicate merge editor.

This build introduces some enhancement in the display of the Duplicate Data Steward pairs. Loading time is divided by 2.

Apply the package

From all versions below 3.50.6

• Reconnect your Org to Delpha: App Delpha Setup / Section: Delpha Integration / Click the Connect button

• Update conversations: App Delpha Setup / Section: Import Conversation

  • Remove Data: Select All conversation package and click on 'Remove Data

  • Import Data: Based on the use cases you are implementing, select your packages : DuplicateAccountsWD, Duplicate ContactWD, DuplicateLeadWD, DuplicatePersonAccount, LeadVsContact, LinkedInEnrichment, LinkedInEnrichmentAdvanced.

• pairs following these steps

  • delete current scheduled tasks involving the Apex class: DDQ_DuplicateRecordAutoMerge

  • from the app Delpha Setup > Duplicate > Initialization, section Auto Merge Scheduler, select the hours to run the auto merge.

• Apply a migration script.

This script updates the existing Duplicate Expressions and Filtering rules and ensure their proper display with the .

Open the developer console and apply the following script.

Manage Duplicate from the Score Meter

The Score Meter now includes the Duplicate information for Accounts and Contacts. By clicking on the link you start the Duplicate Merge process.

Duplicate Settings - Migration to the new JSON based format

From this version, the Duplicate Settings have been moved from SObejcts into a unique JSON.

This reduces the complexity of Duplicate settings spanned over many objects (mainly DDQ Duplicate Objects, DDQ Duplicate fields...). This change requires a migration step that is made simpler by using a dedicated migration package provided by Delpha.

• After the main Delpha package is installed, add the DelphaUpgrade258 package (unmanaged) to your org. It will facilitate the migration process.

  • Package Id: 04tRl000001EAVBIA4

  • Package URL : /packaging/installPackage.apexp?p0=04tRl000001EAVBIA4

Once the upgrade package is installed, open a developer console and run the script below.

Check What's New section

• Delpha Setup

Single stop for Duplicate setup

All the settings are now available in one single place, in the Duplicates section of the Delpha Setup app.

Visual Rule Builder for Duplicate Management

Upgrade Steps from any version previous 3.58.0

• Apply the package

• After the main Delpha package is installed, add the DelphaUpgrade258

Apply the package

UI - UX

Sections on Duplicate Setup (App Delpha Setup > Duplicates > Detection Settings) have been reorganized.

More Logical Sidebar Organization

in the App Delpha Setup, the left-hand menu is now grouped by functional categories (e.g., Data Quality, Duplicates, Conversations), making navigation more intuitive and setup tasks easier to locate.

Suggested Discard Value

Form now on, Delpha performs an analysis on your targeted duplicate population and proposes you to discard in one click all values that may trigger too much pairs. Thsi information is displayed in the app Delpha Setup > Duplicate > Object Settings, in the Properties section of each object.

You can

• Score Meter

  • Fix tooltips not displaying for bullets

  • Yellow bullet for Status = Unknown is now a triangle

You can assess selected records directly from the Data quality Steward view.

If you click on the Assess button, all selected records will be Data Quality assessed. This feature is compatible with the Select All, allowing mass reassessment from the Data Quality Steward View.

Fix some limitations related to the Auto Number fields when used in Expression or Filtering rules.

Check What's New section

• Duplicate

Negative view for tiles

Add "Last Modified Date" column to the steward

Implement filtering for data steward views (Data Quality and Duplicate)

Legal Id types

2 new Legal Ids types are supported by Delpha : Australia and New Zealand

LinkedIn enrichment cleanup

If you remove the D LinkedIn URL from your record (Account or Contact), all related information is deleted from Delpha fields, now including the logo / picture profile.

Validation Rules

Validation rules can act as a blocker for Data Quality.

When a record is updated by Delpha in the Data Quality process (assessment or recommendation phases) it must follow the validation rules or the update will be blocked.

• When it happens in a mass assessment process (Automation, Campaign, Data Steward mass update...) the record is detected and blacklisted in the Delpha Setup > Tab: Locked Records until a Delpha Admin deletes the entry (and takes proper actions to avoid the validation breach again).

• When it happens in a single enrichment phase, using the Score Meter, a warning message is displayed to the user so he knows that his record cannot be updated and why.

This version provides a fix on the mass process from the Duplicate Data Steward view: some duplicate records pairs could be deleted before or after being processed

Build 3.70.0

First draft of the new create account / create contact use cases

Bug Fix: incomplete Legal ID

Legal address was missing the street part. This is fixed.

Direct access to filters

Based on the users feedback, we improved the Data Steward view by having the most common filters back on the main data steward screen area.

Data Quality

You can directly select the Object and the field from the main screen. To access the extra filtering capabilities, click on the filter logo.

Duplicate

You can select the Object and the processing state (True or False). To access the extra filtering capabilities, click on the filter logo.

[Ultimate]

• App Delpha Setup > Data Quality > Account

Once the Ultimate toggle is activated, you can manually trigger a reassessment of the Ultimate analysis.

LinkedIn

Account - Main Entity Address

When enriching an Account, you retrieve the Main Entity address in the tab Delpha > Address. You can reuse this information in a regular address (billing, shipping...).

Note that this address can be different from the Legal Address.

The "What's New" section is organized by key feature areas, making it easy to browse recent updates and improvements. Each item links to a dedicated page summarizing the latest changes and enhancements for that component:

• Delpha Setup – .

• Duplicate – .

• Data Quality

New Data Steward View – Improved Usability & Customization

We’ve redesigned the and the interface to align with Salesforce’s native List View experience:

• Familiar Navigation: Use the standard cog and filter icons to create, filter, and manage your views—just like any Salesforce list.

Process Duplicates from the Score Meter & Merge process New UI

For Accounts and Contacts, processing of Duplicates at record level is now part of the Score Meter. It is no longer done in a conversation but in a dedicated layout.

Upgrade Steps from any version previous 3.63.0

• Apply the package

• After the main Delpha package is installed, add the DelphaUpgrade363 package (unmanaged) to your org. It will facilitate the migration process.

Multiple settings for each handled object

Duplicate Settings now support multiple configurations. You can define a dedicated scope for each configuration using advanced rules in the Record Filter section.

Each configuration runs its own full duplicate assessment, and the results appear separately in the Duplicate Data Steward View.

To create a new Duplicate Setting, click Add New, choose the target object, and decide whether to start from the Delpha default template for detection and merge settings. You can also duplicate an existing configuration using the Clone option.

Detection Settings

General Settings

Record Filter

The goal of the Record Filter is to limit the scope of the duplicate scan, ensuring the system only checks records that meet specific criteria you define.

1. Filter Logic

• Filter Logic: This area allows you to combine multiple individual conditions using boolean operators (AND, OR, NOT) to create complex filtering rules.

• e.g., 1 AND (2 OR 3): This example illustrates how the logic works. It means:

  • Condition 1 must be true, AND

2. Adding Conditions

• Search Input Field: You use this to find and select a field name from your database (e.g., Status, Creation Date, Region).

• Add Condition Button: Once you select a field, you click this button to add a new condition row.

• Condition Rows (implied below the image): Each row will typically let you:

Example Use Case:

You might set up a filter to only check records where:

1. Status Equals Customer

2. AND Last Modified Date Is Greater Than 90 days ago

This filter ensures the duplicate detection process only runs on active customer records that have been modified recently, saving processing time.

Filtering Rules

The purpose is to apply specific rules before potential duplicates are reviewed and merged.

The rules are divided into different Rule Types that trigger specific actions:

Matching Fields

The Matching Fields configuration, is the core mechanism used by the application to calculate the numerical Duplicate Score for any pair of records. This section defines what fields matter and how much they matter when determining if two records are duplicates.

Advanced Settings

This screen shows the Advanced Settings for duplicate detection. This section provides granular control over how the system initially screens for duplicates, cleans data for scoring, and manages duplicate creation in real-time.

1. Screening Fields

Purpose is to quickly filter the large pool of records down to a smaller, more relevant subset before the full, weighted matching score calculation (from the "Matching Fields" section) is performed. This significantly improves performance. The system performs a fast initial match (relying on Name). If the name match is inconclusive, it uses these Screening Fields (e.g., ZIP Code, First Letter of Company Name) to narrow down which records should proceed to the full scoring calculation.

2. Discard Placeholder Values

Purpose is to prevent "dummy" or default values in your records from artificially inflating or skewing the duplicate match score.

You can enter common placeholders that should be ignored into the input field or directly select them from the proposed values.

3. Duplicates at Creation

Define the system's immediate response when a user attempts to create a new record that matches an existing record. This is a crucial real-time defense against data decay.

You choose an option from the dropdown menu to determine what action the system takes: