Loading

Vlocity Party Records Can Be Safely Deleted When Not in Use

Udgivelsesdato: Jun 26, 2026
Beskrivelse

Issue

Salesforce orgs with the Vlocity CMT (vlocity_cmt) managed package may accumulate vlocity_cmt__Party__c records over time. When the Party functionality is not actively used, administrators may want to remove these records to reduce data volume and simplify the org.

Symptoms

  • A large number of vlocity_cmt__Party__c records exist in the org.
  • The Party feature of the Vlocity managed package is not being used by the business.
  • After manually deleting Party records, they reappear because a trigger recreates them.

Root Cause

The vlocity_cmt__Party__c records are created automatically by a managed-package trigger. This trigger fires on record operations and generates corresponding Party records. Even after manual deletion, the trigger recreates the Party records on subsequent DML events unless it is explicitly disabled.

This behavior is by design within the Vlocity managed package — the trigger ensures Party records exist to support the package's Party-Bound Relationship Graphs functionality. When this functionality is not in use, the trigger still runs, which causes the records to persist.

Løsning
Prerequisites
  • Verify that the Vlocity Party functionality is not in use in your org. Check whether any processes, flows, reports, or integrations reference the vlocity_cmt__Party__c object.
  • Perform all steps in a sandbox or lower environment first before making changes in Production.
  • Confirm you have the appropriate administrative permissions to manage triggers and delete records.
Steps to Disable the Trigger and Delete Party Records
  1. Disable the Party Model Trigger
    • From Setup, in the Quick Find box, enter Custom Settings.
    • Click Custom Settings.
    • Next to Trigger Setup, click Manage.
    • On the Trigger Setup page, next to Party.EnablePartyModel, click Edit.
    • Uncheck the Trigger On checkbox, and click Save.

  2. Delete the existing vlocity_cmt__Party__c records.

    • Use Data Loader or Workbench to query and delete the Party records.
    • For large volumes, consider using Bulk API to process deletes efficiently.

  3. Verify that associated Contact records are unaffected.

    • Confirm that deleting Party records does not delete the associated Contact or Account records. The Party record is a separate entity; removing it does not cascade-delete related standard objects.

  4. Monitor the org for record recreation.

    • After deletion, create or update a Contact or Account record and verify that new Party records are not generated. This confirms the trigger is successfully disabled.

  5. Promote to Production.

    • Once validated in the sandbox, repeat the same steps in Production during a low-activity maintenance window.
If the Issue Persists
  • If Party records continue to reappear after disabling the trigger, check for additional automation (Process Builder, Flows, or other Apex triggers) that may also create Party records.
  • If you cannot identify the source of recreation, open a case with Salesforce Support for further investigation.
Vidensartikelnummer

005387792

 
Indlæser
Salesforce Help | Article