Plauti Deduplicate Audit

The dupcheck__dcAudit__c object is part of the Plauti Deduplicate system and stores a historical log of actions taken during the deduplication process. It provides traceability and visibility into what actions were performed, by whom, and when.

Purpose

Plauti Deduplicate Audit is used to record audit trail entries for deduplication jobs and user actions, such as merges, conversion, skips, or delta queue entries.

Fields & Metadata

Field Label	API Name	Type	Description
Audit Date	dupcheck__AuditDate__c	Date/Time	Timestamp of when the audit event occurred
Created By	CreatedById	Lookup(User)	System audit field
Data	dupcheck__Data__c	Long Text Area	Contains structured JSON detailing the full context of a deduplication event, including user, object, method, and merged records. See more below.
Plauti Deduplicate Audit	dupcheck__dcAudit__c	Lookup(dcAudit)	Self-lookup, used for linking grouped audit entries
Plauti Deduplicate Audit Name	Name	Auto Number	Unique identifier for the audit entry
Plauti Deduplicate Job	dupcheck__dcJob__c	Lookup(dcJob)	Reference to the job that triggered the audit (can be null)
Last Modified By	LastModifiedById	Lookup(User)	System audit field
Method	dupcheck__Method__c	Text(50)	Technical source of the action (e.g., flow, component, API)
Object Id	dupcheck__ObjectId__c	Text(18) (External ID)	ID of the object related to the audit
Object Label	dupcheck__ObjectName__c	Text(255)	Display label of the object type
Object Prefix	dupcheck__Prefix__c	Text(4)	Key prefix of the object type
Order	dupcheck__Order__c	Number(18, 0)	Sequence of execution or grouping
Owner	OwnerId	Lookup(User, Group)	Ownership field
Record Id	dupcheck__RecordId__c	Text(18)	Specific record ID affected by the action
Related Records Ids	dupcheck__RelatedIds__c	Text(255)	Record IDs of loser records after a successful merge event
Type	dupcheck__Type__c	Picklist	Type of audit event (e.g., Merge, Convert, Delta)
Type String	dupcheck__TypeString__c	Text(50) (External ID)	Text representation of type
User	dupcheck__User__c	Lookup(User)	User who performed or triggered the action

Understanding the dupcheck__Data__c Field

The dupcheck__Data__c field stores detailed JSON data that describes what happened during a deduplication event such as a merge or queue entry.

For merge events this field includes:

• User information: Who triggered the event, including their user ID and name.
• Timestamp: Exact time the event occurred.
• Event type: Indicated by the auditType (e.g., "Merge", "Delta").
• Merge method: Whether the merge was manual, automatic, or API-driven.
• Master object: The record that was retained after the merge, including field values like address and description.
• Loser objects: Full snapshots of the records that were merged into the master, including both standard and custom fields.
• Context: Optional internal flags or merge rule versions used at the time of execution.

This field is useful for developers and admins who need complete visibility into how merges were performed, for syncing with external systems, rollback logic, compliance auditing, or custom reporting. You can parse this JSON data in Flows, Apex, or external ETL tools to take follow-up actions or generate traceable logs.

Developer Use Cases

• Trigger Post-Event Logic via Flow: Launch a Flow when an audit entry is created (e.g., TypeString = 'Merge') to perform follow-up actions. Example: Automatically merge related Opportunities when a Contact is merged, or notify record owner.
• Audit Trail Reporting: Use this object to build compliance reports or dashboards showing user and system deduplication actions over time.
• Merge Tracking: When TypeString = 'Merge', analyze the contents of dupcheck__Data__c to see which records were merged, the user who performed it, and what changed.
• Error Forensics: Use dupcheck__Data__c to retrieve structured payloads such as user info, timestamps, merge context, and record data for debugging and audit.
• Use Related IDs for External Sync: The dupcheck__RelatedIds__c field contains the IDs of the "loser" records in a merge. You can use these IDs in integrations to update or archive records in external systems.