Plauti Deduplicate release notes

New

• Merge Rule Sets - Create multiple merge rule sets per object, so you can apply different merge logic depending on the records you merge. For example, use one merge rule set for leads with Lead Source "Web" and another for leads with Lead Source "Phone", or define separate sets per Record Type.
  Merge rule sets are available for Premium and PDM licenses.

To determine which Merge Rule Set should be applied, add a priority and a condition, written as a Salesforce formula. When records are merged, Plauti Deduplicate evaluates the active merge rule sets in order of priority, and applies the first set whose condition is met by all records in the merge group. When no other sets match, the Default Merge Rules set is used.

Your existing merge rules are automatically converted to the Default Merge Rules set when you update. This set is always active and cannot be renamed, deleted, or given a condition. It can be cloned to create other merge rule sets.

Improved

• Merge Rules - The Master Record Rule, field merge rules, and field groups have been redesigned and offer more options:

  Use the new Value based and Field based rule types. With Value based rules, the record where a field matches a specific value is selected, for example "City equals Arnhem". Field based rules can reference a different field than the field being configured.

  Add up to five merge rules per rule: a primary rule, up to three additional rules, and a date-based rule that acts as the tiebreaker. For each additional rule, choose whether it applies to the records selected by the previous rule or to all records. If the primary rule is date-based, no additional rules are needed.

• Salesforce Winter '27 - Plauti Deduplicate has been updated for compatibility with the Salesforce Winter '27 release.

Classes Added

If you are not using the Plauti Deduplicate permission sets, add the following classes to the applicable Admin/User permission sets:
dc3ControllerMergeRuleSet
dc3MergeRuleSetMigrator
dc3MergeRuleSetResolverBatch
dc3MergeRuleSetSelector
dc3MergeRuleSetValidator
dc3MergeRuleSet

Other Items Added

If you are not using the Plauti Deduplicate permission sets, add the following field to the applicable Admin/User permission sets:
dcGroup__c.AppliedMergeRuleSetId__c

Improved

• Duplicate Prevention - The setting Duplicate Prevention in Native Entry Page Lightning has been renamed to Duplicate Prevention in Entry Page, since it also applies to the Deduplicate Entry override page, and Classic is no longer supported.
  Enabling this setting will block the creation of duplicate records both in Salesforce and Plauti Deduplicate Entry pages. Read more in Deduplicate Entry.
• Lead Conversion - When "Contacts to Multiple Accounts" is enabled in Salesforce, you can now convert a Lead into any existing Contact and Account combination; upon conversion an indirect account-contact relationship is created.
• Matching Methods - The Date Distance in Months matching method now supports a range of up to 12 months.
• Setup - Improvements were made to the performance of the Deduplicate Setup page.
• Setup - The Setup Check now detects duplicate Deduplicate settings and duplicate Record Type scenario/match configurations, with a one-click Fix for each, grouped under a new "Org-wide checks" section. Furthermore, the Setup menu shows the number of detected setup issues, surfacing problems even before the page is opened.
• Small Trigger Footprint - The setting for enabling the Small Trigger Footprint now lets you choose between “Enable for all field updates”, and “Enable for scenario field updates”. This gives you more control over which records are queued for indexing.

Fixed

• AI Scenario Builder - Creating a scenario with the help of the AI Scenario Builder no longer fails when a field label contains special characters, such as parentheses or brackets.
• Deduplicate Entry - Lookup searches now work correctly for custom objects.
• Deduplicate Entry - Salesforce validation rules now work correctly in Deduplicate Entry when using State/Country Picklists.
• Overall Job Results (OJR) - When using an embedded OJR overview, with the Source Record Owner filter set to "Logged-in User”, the overview now displays duplicates where the logged-in user owns at least one of the records.
• Scheduled Jobs - You can now change where existing scheduled jobs will run, e.g. from within Salesforce to on Plauti Cloud.

New

• Scenario Tester - Test a Deduplicate Scenario directly from the Scenarios setup page without running a full duplicate search. Enter two records or field values to compare, and verify that the Scenario produces the expected results. Read more here.

Improved

• API - All of Plauti Deduplicate’s triggers and Apex Classes have been updated to API version 66.0.
• Deduplicate Setup - Quickly switch between Setup pages of all of Plauti’s Apps, and find out more about the ones you aren't using yet.
• Flows - Specify which Scenarios to use in the ‘Search by ID’ and ‘Search by Field Values’ Flow Actions. When left empty, all Scenarios that are applied to Flow will be used as usual.

Classes added

If you are not using the PD permission set, add the following classes to the applicable profiles or permission sets:

• dc3ControllerSetupScenarioTester

Fixed

• Deduplicate Convert - When converting Leads, any messages alerting the user to correctly fill out the form are now fully displayed again.
• Deduplicate Entry - When opening Deduplicate Entry by URL Addressable, using the RecordType parameter, the default record type page layout was used instead of the specified record type.
• Predefined Filters - Using a Date/Time parameter in a Predefined Filter would result in an error.

Bugfixes

• Deduplicate Entry - When creating a new record from a parent record's related list, custom lookup fields now correctly pre-fill with the parent record.
• Deduplicate Setup - Exporting a Plauti Deduplicate configuration with a large number of objects (more than ten) no longer fails due to SOQL query limits.
• Deduplicate Setup - In Salesforce orgs with Tableau Next enabled, the Deduplicate Setup page now loads correctly. Previously, access errors related to the PersonalOrgInfo object could occur.
• Predefined Filters - Filters on reference fields (such as CreatedById) and Record Type fields now save and work as expected.

New

• AI Merge Recommendation - Use AI-powered field selection for Auto Merge and Direct Processing, in combination with the merge rules for non-AI fields.
• Plauti Apps – Deduplicate your records even before importing them into your org with the Import Records data flow in Plauti Desktop, Server and Cloud (previously DC Local). Duplicates will not be imported, keeping your Salesforce org clean.
• Scenarios – Not sure how to set up an efficient scenario for finding duplicates? Use the new AI Scenario Builder to come up with scenarios that suit your needs. Based on the object fields you are using, this AI Assistant will ask targeted questions to understand how you want to compare records. It generates a scenario proposal that you can refine through follow‑up questions. Once you’re satisfied, save and deploy the new scenario. Read more here.

Improved

• Audit Logs - When fields are merged based on AI Merge Recommendation, the Audit Logs record that field value selection was based on AI Recommendation, as well as the AI’s reasoning for its decision.
• Deduplicate Setup – The layout of the Deduplicate Setup pages has been improved with an intuitive user interface. To prevent accidental edits to settings, all changes to the setup now need to be confirmed by clicking 'Save'.
  Non-System Administrators now need the Salesforce system permission ‘Customize Application’ to edit all settings in Deduplicate Setup, instead of just the General Settings.
• PD REST API – Specify which deduplicate scenarios to use during REST API deduplicate search operations. Read more in the Plauti SDK library.
• Plauti Desktop/Server: A number of improvements were made. Jobs will now continue running when your machine enters sleep mode, you can disable SSL certificate checks or enable TLS, and more. Read more in the Plauti Apps release notes.
• DC Entry Tab – From Plauti Deduplicate release 2026 R1 onward, the DC Entry tab that can be added to the Salesforce Navigation Bar will no longer be supported. Note that this is not the same as the Deduplicate Entry (DC Entry) replacement page, which will continue to exist. Read more here.

Classes added

If you are not using the PD permission set, add the following classes to the applicable profiles or permission sets:

• dc3ConverseWithAiJarvis
• dc3ConverseWithAiTypes
• dc3HierarchyBatch
• dc3IConverseWithAi
• dc3ObjectConfigMigrator
• dc3ObjectConfigRepository
• dc3ScenarioBuilder

Bugfixes

• NPSP Insert Prevention - In NPSP Orgs, in some cases, duplicate prevention in native entry pages (Lightning) did not work.
• Manual Merge - Time fields can be edited again in the ‘Preview’ column, thus overriding the field preselection.
• PD Merge – In some cases, Plauti Restore would interfere with Plauti Deduplicate Manual Merge activities.

New

• Plauti Apps – Deduplicate your records even before importing them into your org with the Import Records data flow in Plauti Desktop, Server and Cloud (previously DC Local). Duplicates will not be imported, keeping your Salesforce org clean.
• Scenarios – Not sure how to set up an efficient scenario for finding duplicates? Use the new AI Scenario Builder to come up with scenarios that suit your needs. Based on the object fields you are using, this AI Assistant will ask targeted questions to understand how you want to compare records. It generates a scenario proposal that you can refine through follow‑up questions. Once you’re satisfied, save and deploy the new scenario. Read more here.

Improved

• Deduplicate Setup – The layout of the Deduplicate Setup pages has been improved with an intuitive user interface. To prevent accidental edits to settings, all changes to the setup now need to be confirmed by clicking 'Save'.
• PD REST API – Specify which deduplicate scenarios to use during REST API deduplicate search operations. Read more in the Plauti SDK library.
• Plauti Desktop/Server: A number of improvements were made. Jobs will now continue running when your machine enters sleep mode, you can disable SSL certificate checks or enable TLS, and more. Read more in the Plauti Apps release notes.
• DC Entry Tab – From Plauti Deduplicate release 2026 R1 onward, the DC Entry tab that can be added to the Salesforce Navigation Bar will no longer be supported. Note that this is not the same as the Deduplicate Entry (DC Entry) replacement page, which will continue to exist. Read more here.

Classes added

If you are not using the PD permission set, add the following classes to the applicable profiles or permission sets:

• dc3ConverseWithAiJarvis
• dc3ConverseWithAiTypes
• dc3HierarchyBatch
• dc3IConverseWithAi
• dc3ObjectConfigMigrator
• dc3ObjectConfigRepository
• dc3ScenarioBuilder

Bugfixes

• PD Merge – In some cases, Plauti Restore would interfere with Plauti Deduplicate Manual Merge activities.

Version 2026 R1 not on Production We have decided to postpone our 2026 R1 release, which was originally scheduled for January 26. All changes planned for R1 will now be included in the R2 release, following the 2026 release schedule as listed on Plauti Deduplicate General release information‍. Production environments will not receive any updates before that time, and the R1 features that are currently available in Sandbox will only be promoted to Production in the 2026 R2 release. We have encountered issues during the sandbox period that we need to address before this version is production ready. We understand that this postponement may impact your planning, and we sincerely apologize for any inconvenience. If you have any questions, please don't hesitate to contact Plauti Support, via support@plauti.com.

Release Winter '26 Features, December 1, 2025

New

• Deduplicate Job - Use AI Match Recommendation to get AI-generated matching analysis included in Deduplicate Job results, that indicates whether records are likely to be duplicate or not. Then use that advice to decide whether to merge records or not; manually or with an auto merge job based on the AI advice.
  Strict matching rules can miss fuzzy matches that might be legitimate duplicates, but relaxing match rules leads to more potential duplicates that require a lot of manual reviewing. AI Match Recommendation can compare records holistically, thus catching duplicates that straightforward match rules could miss, and at the same time relieving you from a large portion of the manual reviewing work. Read more here.

Improved

• General - As part of Plauti’s rebranding process, the Duplicate Check app is not available anymore in the App Launcher from now on. Find DC in Salesforce’s App Launcher as ‘Plauti Deduplicate’. Don’t forget to add it to your favorites!
  Read more about the new naming in this blog, and find a list of all new names in DC and Plauti Deduplicate old and new names‍.
• Overall Job Results - Display the pair relationships within a duplicates group in OJR as a node-edge graph with the Show Graph View option. Display all matching percentages between record pairs in a graph, and select nodes to compare their details.
• Plauti Desktop/Server - Apply custom CA certificates and configure proxy server settings for Plauti Desktop and Plauti Server. Read more here.
• REST API - The Plauti Deduplicate REST API has been improved with two new options:
• Filter on scenarios in the Search endpoint
• Retrieve scenario configurations for Objects with a new GET endpointUse this for example to let your integration search for duplicates with specific scenarios, or to let a monitoring tool verify certain scenario configurations.

Classes added

If you are not using the PD permission set, add the following classes to the applicable profiles or permission sets:

• dc3AbstractDupRecommendationAdapter
• dc3AzureDupRecommendationAdapter
• dc3DuplicateRecommendationBatch

Bugfixes

• Account Hierarchy - Excluding accounts that are connected via Account Hierarchy as potential duplicates could trigger an error in cases where an account had a large number of child accounts.
• Deduplicate Entry - Date and date/time fields are now formatted according to the user’s language setting.
• Deduplicate Job - On finished Jobs, the Info modal now displays the correct Empty Fields scenario configuration again.
• Record Types - After deleting a record type that still has scenarios configured in Deduplicate Setup, you are now notified that you should run a Setup Check.

New

• Plauti Restore - Undo Merges and other field and record changes with the new Plauti Restore solution. Keep track of changes: merges, inserts, updates and deletions, on Objects and Fields you define. Restore changes including related data to revert accidental modifications. Restore from the main Changes overview, or from a custom record tab. Read more here, or watch the video.
• Manual Merge - Use AI Merge Recommendation to get AI-generated, contextual field merge proposals in the Manual Merge modal.
  The Manual Merge page suggests a master record and field values to keep based on the Merge Rules, such as “shortest value” or “Most recently updated”. However, these values are not always the values you want to keep. Plauti AI Merge Recommendation considers the full context of the records to merge, resulting in more useful merge suggestions.
  AI suggestions are always visible for review, and require your confirmation before any changes are applied. No automatic merges will occur. Read more about AI Merge Recommendation here.

Improved

• Overall Job Results - The configuration fields for embedding the Overall Job Results page in a Salesforce page have been renamed, to better reflect their intended use. All ‘Cross’ fields can only be used for Cross Object job results. Read more here.

Other

• Flow Actions - From Salesforce’s Winter ‘26 release onwards, flow apex actions in record-triggered flows cannot be used anymore in an immediate path (synchronous path or non-scheduled path). To prevent your flows with Plauti apex actions from failing, change the Transaction Control settings of your existing record-triggered flows to 'Always continue in current transaction’.
  Note that screen flows and auto-launched flows are not affected.
  Read more about updating your flows here.

Classes Added

If you are not using the DC permission set, add the following classes to the applicable profiles or permission sets:

• dc3SecureRedirectController,
• dc3AzureMergeRecommendationAdapter,
• dc3MergeRecommendationHelper

New

• DC Local - To improve user experience, maintenance, and feature consistency, DC Local and DC Local Server have been replaced by two new apps: Plauti Desktop and Plauti Server. Not only will these apps be more intuitive to use, they will also contain new features.
  For example, you can queue jobs from multiple Salesforce Orgs and MS Dynamics Environments without the need to switch between orgs. And, in addition to quickly running Deduplicate and Export jobs on your local machine as you are already used to, you will be able to import and export data to and from your Salesforce org.
  More features will be added in the future. Find out more here.
• Export Data - A new Data Flow is available: Data Export. Next to importing data into your Salesforce Org, you can now export data from any Object as well. Export a CSV file with data from the entire object or a subset of records, from selected fields including parent fields. Run the Export Data Flow in Plauti Cloud, or in the new Plauti Desktop or Plauti Server apps that will replace DC Local and DC Local Server. Read more here.

Improved

• Overall Job Results - The filter option “All records in a pair must match filters”, which is already present when filtering a single-object Overall Job Results (OJR) overview, can now be predefined when setting up embedding the OJR overview on another page.

Fixed

• Deduplicate Entry - Rich Text Area fields now offer their rich text formatting options again.

Improved

• Deduplicate Job (DC Job) - Filter a job on Date Literal in combination with Earlier Than, Equals, or Later Than.
• General - Labels have been updated to reflect the new naming. Find the settings in Deduplicate Setup, run a job via Deduplicate Job, etc. Read more about the new naming in this blog, and find a list of all new names in DC and Plauti Deduplicate old and new names‍.
• Index Search - In order to improve upon the performance of the duplicate search process it was necessary to remove the option to search with a wildcard.

Classes added

If you are not using the DC permission set, add the following classes to the applicable profiles or permission sets:

• dc3GenericStorageRepository
• dc3SettingsMutex
• dc3InAppNotification
• dc3InAppNotificationController
• dc3InAppNotificationRepository
• dc3InAppNotificationScheduler
• dc3InAppNotificationService

Other items added

If you are not using the DC permission set, add the following object to the applicable profiles or permission sets:

• Plauti Deduplicate Generic Storage (dupcheck__dc3GenericStorage__c)

Fixed

• Auto Convert - After a scheduled Deduplicate job that is run on DC Local Server, the subsequent Auto Convert job will now start automatically again.
• Deduplicate Discard (DC Discard) - Groups containing a large number of records could not be discarded from the job results.
• Deduplicate Entry (DC Entry) - Formula fields now correctly display formatted content such as images (IMAGE) or hyperlinks (HYPERLINK).
• Deduplicate Entry (DC Entry) - Multi-select picklists now display the number of lines as set in their Visible Lines setting again.
• Deduplicate Entry (DC Entry) - The State/Province field of custom addresses is now properly displayed again in Deduplicate Entry.
• Deduplicate Entry (DC Entry) - Users with read-only rights for a lookup field can now save the record again when the field is empty.
• OJR - With the Overall Job Results‍ overview (OJR) for a single object embedded on a page, the option “All records in a pair must match filters” was missing from the filter options.

New

• Plauti is rebranding! Duplicate Check has been renamed to Plauti Deduplicate, and can be found under that name in the Salesforce App Launcher.
  For now both apps can still be used, but later this year only the new Plauti Deduplicate app will be available. So add it to your favorites! Read More.

Improved

• DC Entry - The Record Type field now displays the record type name instead of its ID.
• Overall Job Results - Decide to display or hide the ‘Delete Record’ buttons in duplicate groups in an embedded Overall Job Results list.

Items added

• Add the new Plauti Deduplicate app to your list of favorite Salesforce apps to use instead of the Duplicate Check app.
• If you are not using the DC permission set, assign the following app to the applicable profiles or permission sets:
  Plauti Deduplicate (dupcheck__plauti_deduplicate)
  if you currently have the Duplicate Check (dupcheck__dc3App_Lightning) app assigned there.

Fixed

• DC Entry - The setting ‘Prefill parent record if DC Entry is opened from a record page', when used from a record details page, now also works for multi-object lookups.
• DC Entry - When a controlling picklist field was set to ‘read-only’, the dependent picklist field also became read-only for non-system admins on a DC Entry page.
• DC Entry - When copypasting a number in a number field, the last digit was omitted.
• DC Entry - When creating a related record with a DC Entry URL Addressable button, the master-detail relationship field was filled in, but it was not visible until saving.
• DC Entry - When using DC Entry to edit records, some changes were not visible straight away.
• DC Merge - With Country/State Picklist enabled, the country or state could not be edited in the merge preview.

New

Plauti is rebranding! Duplicate Check has been renamed to Plauti Deduplicate, and can be found under that name in the Salesforce App Launcher. For now both apps can still be used, but later this year only the new Plauti Deduplicate app will be available.
So add it to your favorites! Read More.

Items added

• Add the new Plauti Deduplicate app to your list of favorite Salesforce apps to use instead of the Duplicate Check app.
• If you are not using the DC permission set, assign the following app to the applicable profiles or permission sets:
  Plauti Deduplicate (dupcheck__plauti_deduplicate)
  if you currently have the Duplicate Check (dupcheck__dc3App_Lightning) app assigned there.

Classes added

If you are not using the DC permission set, add the following class to the applicable profiles:

• dc3JobInfoQueueable

Fixed

• DC Entry - In the new DC Entry, lookup fields weren’t always displayed correctly.
• DC Entry - With the option 'Prefill parent record if DC Entry is opened from a record page' enabled, lookup fields in DC entry were also prefilled when a new record was created from somewhere else, like the navigation bar.

Improved

• DC Entry - To make sure DC Entry is ready for new features in the future, its technology has been modernized. Please select the new DC Entry Lightning component for the New and Edit pages in Salesforce Setup. Read more here.
  If you are using a URL with prepopulated values to open the DC Entry page, this needs to be adjusted as well. See DC Entry - URL Addressable‍ for the new base path.
  Furthermore, duplicate block override now works based on permissions instead of the Disable Duplicate Check checkbox. Read more here.

Classes added

If you are not using the DC permission set, add the following classes to the applicable profiles:

• plautiWebRequest
• dc3WebEntryController
• dc3WebLookupController

Fixed

• DC & RV - In some cases, when converting a Lead with Duplicate Check, the RV validation and metadata were not copied along.
• NPSP Merge - When merging Contacts that are part of different Households, and that are the only Contacts for their Household, the Household Accounts now merge correctly as well, following the Account merge rules.

Improved

• General - A number of minor bugfixes and performance improvements were carried out.
• General - Discover Data Flows, Plauti’s new import feature for Salesforce and Microsoft Dynamics. In Plauti Cloud, in the Data Importer menu, create Data Flows to process data in bulk. Import CSV or Excel files of any size into a Salesforce or Dynamics environment, with support for any Object or Entity type, and handy features like previous mapping memory. Perfect for data migration projects. Read more here.
  For now you can only insert data as new records into a Dynamics or Salesforce environment, but in the future updating, exporting and other data processing options will be available.

Fixed

• DC Job - For Cross Object jobs, and single object jobs with a filter applied, only the source record count was displayed in the info modal, not the match record count.
• DC Job - The results of a Cross Object job were not updated when Auto Merge was applied to records in the results via DC Local.

New

• General - Easily link Sandboxes to your Production license via the new Sandbox Linking page. Read more here.

Improved

• DC Job - Next to filtering out jobs to delete, you can now select jobs for deletion straight from the job overview, or select an entire page at once.
• DC Merge - When using Set for Merge you can now see whether a duplicate group was already been set to Set for Merge, and by whom.
• Frequent Words - Include a comma as part of a frequent word by escaping it with a backslash. Read more here.
• Overall Job Results - When opening a results group in Group View, the name of the job where the group originates from is displayed.

Fixed

• DC Entry - With Geocode location fields present on the page layout, new records could not be saved via the DC Entry page.
• DC Job - A job’s info modal will now display the correct number of records analyzed in the (single object) job.
• DC Job - Job results shared with a group by email were not always received by all group members.
• DC Merge - In Financial Service Cloud, when merging Accounts or Contacts with record type “Individual", merging sometimes did not work.
• DC Merge - Users without delete permission can edit values inline in the Merge Preview again.
• DC Setup - With user language set to French, apostrophes were not displayed correctly in some Predefined Filter settings.
• DC Unique Import - Large import jobs sometimes displayed ‘N/A’ as result in the overview, when there were results present (the View Results button did indicate the number of results correctly).

Fixed

• DC Job - When filtering a job on Record Type, record types of unrelated objects were available for filtering as well.
• DC Settings - In the DC Setup setting “Default display of field values if text exceeds column width in DC Job Result”, you can now set either "Clip text” or "Wrap text”.

New

• Synonym Matching - Create lists of synonyms that will be matched as duplicates of each other. Apply the synonym lists to specific scenario fields.
  For example, match First Name values ‘Bobby’, ‘Bob’ and ‘Robert’, or State values ‘New York’, ‘NY’ and ‘NYC’ as duplicate values. Read more here.

Improved

• Scheduled Jobs - On the Scheduled Job Overview page, the info modal of a job now shows more information. It lists whether the job will be processed in Salesforce, DC Local or Plauti Cloud; and whether Auto Merge / Auto Convert will be applied or not.

Classes added

If you are not using the DC permission set, add the following class from the applicable profiles/permission sets:

• dc3ControllerSynonymMatching
• dc3HelperSynonym
• dc3MergeCustomMerge
• dc3MergeDeleteAccConRelation
• dc3MergeFeedMerge
• dc3MergeIPipelineStep
• dc3MergeNPSPMerge
• dc3MergeOpportunityMerge
• dc3MergePipeline
• dc3MergePipelineFactory
• dc3MergePipelinePayload
• dc3MergeProductMerge
• dc3MergeRegularMerge
• dc3MergeReparentAccConRelation
• dc3MergeReparentHierarchy
• dc3SynonymMatchingRepository
• dc3SynonymMatchingService

Fixed

• DC Entry - When you have custom address fields in use on an object, the DC Entry page did not show the individual address field labels.
• DC Merge - Field rule ‘Group that has the most fields populated’ was missing a fallback rule when applied to Address compound fields.
• DC Merge - Merging Custom Object records could result in an error in Salesforce Spring '24.
• DC for NPSP - Direct Processing did not work properly when merging more than two duplicate records.
• DC Setup - Predefined Filters were not visible with language set to French.

Improved

• DC Job - The new DC Job Overview, with an updated interface and improved functionality, is now fully in use. The last missing features have been added, such as a number of filter fields, and scheduling a custom Cron job. The old DC Job Overview has been discontinued, to align with Salesforce’s updated security protocols.
• DC Job Auto Merge - When preparing a DC Job, next to the auto merge threshold, set an Object Filter and/or Duplicate Group Filter to determine in which cases Auto Merge should take place.
• General - Next to English, Dutch, French, German and Spanish, DAP is now available in Chinese (Simplified) as well. Translations for the other languages have been improved. However, if you still encounter any translation mistakes, do let us know!
• Predefined Filters - At each time of running, scheduled jobs that use a predefined filter now apply the current state of the predefined filter. Previously, the predefined filter in its state as it was at the time of creating the scheduled job was used for all future runs. Please keep this in mind when editing predefined filter settings.
  This also applies to restarting a single job from the Job Overview.

Classes added

If you are not using the DC permission set, add the following class from the applicable profiles/permission sets:

• dc3FilterMapper

Fixed

• DC Job - Fixed a small problem with editing date/time filters in a DC Job.
• NPSP - The merge log did not log the auto-merge of NPSP contacts.

New

• DC Job - The new DC Job Overview, with an updated interface and improved functionality, is set as the default. For now you can still toggle between the new and old version, but from release 2024R1 (Sandbox January 29, Production release February 12) the old DC Job Overview will be discontinued to align with Salesforce’s updated security protocols.

Classes removed

If you are not using the DC permission set, remove the following class from the applicable profiles/permission sets:

• dc3ComponentWelcomeTest

Items added

If you are not using the DC permission set, add the following Visualforce page and tab to the applicable profiles:

• Visualforce page: dc3OnboardingPage
• Tab: dc3Onboarding
  This is a repeat message, as this page and tab were already available in a patch for the previous version.

Fixed

• DC Export - When exporting DC Job results, the number of exported duplicates was not shown on the new DC Job page, even though the export itself succeeded.
• DC Live - In some situations, a record page that includes the DC Live component could not be saved after editing.
• DC Merge - For some field merge rules, with Field Level Security active for the user, the DC Merge Preview page did not load. Now, a user with restricted field access will be shown a warning message.
• DC Merge - In NPSP orgs using the one-to-one account model, and with the ‘Contacts to Multiple Accounts’ setting enabled, an error could occur when merging contacts.

Improved

• DC Job Overview - In the new DC Job Overview (Beta), add an Object filter to run an Auto Merge or Auto Convert on a subset of job results.
• DC Merge - If a merge rule points to an empty field, the rule is re-applied to decide which field value will be used in the master record from the remaining records.
• General - Optimized the deletion of DC system records so they will not be kept unnecessarily in the recycle bin

Classes added

If you are not using the DC permission set, add the following classes to the applicable profiles:

• dc3OnboardingService
• dc3WebOnboardingController
• dc3WebTelemetryController

Classes removed

If you are not using the DC permission set, remove the following class from the applicable profiles/permission sets:

• dc3ComponentWelcomeTest

Other items added

If you are not using the DC permission set, add the following Visualforce page and tab to the applicable profiles:

• Visualforce page: dc3OnboardingPage
• Tab: dc3Onboarding

Fixed

• DC Apex API - For end users with read-only access to a field, the output from the ‘GetMergeMaster' API method did not show the value of that field. Use an additional method to show such read-only fields. Read more here.
• DC Discard - Groups containing a large number of Person Account records could not be discarded from the job results.
• Merge Preview - Picklist field values are now shown in the correct language if they are translated.
• General - When adding a filter containing an empty Value field, e.g. in a DC Job, the filter was not always added right away.