Case Merge Premium Release Notes 5.73 - 5.841

  • Nov 26, 2025
  • Knowledge

Permalink
https://kb.vicasso.com/?kb=000005435
What's New
Improvements
  • The app has been optimized for SLDS2 design updates. (5.77)
  • Due to a Salesforce limitation, cloning Messaging Session records on cases is not possible. That option will now be grayed out in the "Child Object" tab of the setup wizard. (5.79)

  • Due to Salesforce limitations and to avoid "Field caseid is not editable" errors when merging cases, Salesforce Historical and Big Objects are not eligible for selection in the Child Objects tab of the setup wizard. (5.82)
  • The search bar is now collapsed by default on cases with previously merged cases showing in the Merge History section. (5.83)

  • To avoid issues when the "Rich Text for Case Comments" setting is enabled in the organization through Salesforce's Support Settings, the custom setting to enable/disable rich text in the app has been deprecated. The CommentBodyRichtext will always be populated whenever a case comment is inserted. (5.83)
  • Following Salesforce's security enhancements, Connected Apps can and should be migrated to External Client Apps, which are now supported. (5.84)
  • Improved error handling for the External/Connected App Client setting. (5.84.1)

 

Bugs Fixed
  • Fixed an issue related to the error "Insert failed. First exception on row 0; first error: DUPLICATE_VALUE, Document with ID: 069Su000006aTCx is already linked with the entity with ID: 500Su00000LF9Gf: [LinkedEntityId]" when attempting to transfer files from a merged case to its parent. (5.73)
  • The "Cannot read properties of undefined (reading 'Owner.Name')" error no longer happens when duplicate cases are detected. (5.74)
  • Errors such as "null input to JSON parser" and "[this.errorDetails.forEach is not a function]" should no longer pop up when working in Salesforce. (5.74)
  • Existing customers from prior to 2025 will no longer see unlicensed user messages for the Duplicate Detector component. (5.75)

  • Fixed the issue where cases owned by unlicensed users and blurred on the component could still be dismissed from the list of duplicate cases. (5.76)
  • Configuring the Connected App should no longer result in the "Invalid Credentials" error. (5.77)
  • Users should no longer see the "Body: data value is too large" error when sending comments out after merging cases that contain comments that exceed the 4000-character limit in Salesforce when the "Clone" option for Case Comments is enabled in the setup wizard. (5.79)
  • Errors similar to " t.hostElement.appendChild is not a function" and "Uncaught Error during LWC component connect phase: [illegal invocation]" should no longer show up when loading cases if Lightning Web Security is disabled in the org. (5.79)
  • Clicking the information icon in the component no longer results in the "[this.refs.dialog.showModal is not a function]" error, and the duplicate criteria are displayed correctly. (5.80)
  • A new custom setting called "Use Rich Text Case Comments" was added and disabled by default to prevent issues related to the character limit of the CaseComment.CommentBodyRichText imposed by Salesforce. When enabled, rich text comments are added instead of plain text. (5.80)
  • Fixed Salesforce internal errors such as: "UNKNOWN_EXCEPTION: An unexpected error occurred. Please include this Errorid if you contact support: 1146936932-47752 (1498942470)" by ensuring that email messages in a draft status are ignored during the merge process. (5.80)
  • The dependency on Enhanced Email has been removed from the package, and organizations with it disabled can now install without issues. (5.81)
  • Fixed the wrong spelling of "No Duplicate Cases" in the mobile version of the component. (5.83)
  • Fixed an issue in Winter '26 where the settings' descriptions in the setup wizard were all bolded in SLDS2. (5.83)
  • The error "Access to EVENT 'force:registerHover' with access 'INTERNAL' is not allowed from namespace 'csmrgp' in 'csmrgp:CriteriaManagerAppContainer'(APPLICATION)" should no longer occur in Winter '26, allowing the Case Merge Premium tab of the app to load the Search by Criteria section as expected. (5.83)
  • We updated our API version throughout the app to version 62.0 to prevent errors such as “Errors occurred during the case update process. Check validation rules that may prevent updates from succeeding. Error list: Field Case.MilestoneTimer is inaccessible in this context" when mergning cases, and “Field Case.MilestoneTimer is inaccessible in this context” when loading the setup wizard if the MilestoneTimer field is being used in the org. (5.83)
  • Fixed an issue where clicking the "X merged cases" link in the Merge History section of the component would not properly expand the section on the first click. (5.83)
  • The toast notification that appears when a case is being automerged (when configured to trigger from selected statuses) now correctly links to the parent case when clicking "here". (5.84)
  • When working in a console app in Salesforce, cases that were automerged will no longer appear in both the Duplicates Detected and Merge History sections of the component; instead, they will only appear in the Merge History section, as the merge has already occurred. (5.84)
  • Updated the code to prevent errors such as "Apex Type unsupported in JSON: System.SelectOption" from happening when configuring the "Configure External Client App or Connected App" setting in the wizard. (5.84.1)

 

Title
Case Merge Premium Release Notes 5.73 - 5.841
URL Name
Case-Merge-Premium-Release-Notes-5-73-5-841