Summary

Investigated duplicate rows in Payton Team - Requests 30+ No Production, using Craig Dean Sr. as the example from the screenshot.

Findings

The duplicate Craig Dean rows are two distinct live litify_pm__Request__c records, not duplicate rendering from the report type. Both are open 911 Audio requests for LMPD Records, requested 2025-09-23, created by Jessica Pulido about four minutes apart.

Under report-equivalent filters, 153 rows match and 2 duplicate groups were found, creating 2 extra rows total:

• Craig Dean Sr., 911 Audio, LMPD Records, requested 2025-09-23.
• Sarah Ellis, Health Lien, OPTUM SUBROGATION SERVICES-KATCH, requested 2026-02-13.

Work Completed

• Retrieved and inspected the live report metadata for Payton Team - Requests 30+ No Production.
• Confirmed the report type is normal Request plus Matter, not a child-object join that multiplies rows.
• Backed up the report XML to /Users/samaguiar/Documents/Projects/admin/backups/litify-request-report-dedupe-2026-05-17/Payton_Team_Requests_30_No_Production.pre-dedupe.report-meta.xml.
• Tried a direct Request Id exclusion filter. Salesforce rejected litify_pm__Request__c.Id as an invalid report filter column, and no deploy occurred from that attempt.
• Deployed a reusable checkbox field, Suppress from Open Request Reports, plus a report filter excluding rows where that checkbox is true.

QA

• Metadata validation for the checkbox/report-filter path succeeded: 2 components, 0 component errors, 112 tests completed, 0 test errors.
• Metadata deploy succeeded: 2 components, 0 component errors.
• Tooling API confirms the field metadata exists as CustomField 00NUV00001FcqUH2AZ.

Current Blocker

The duplicate records were not marked suppressed because Salesforce has not exposed the new field on the managed litify_pm__Request__c sObject for data updates yet. Data API and Apex both returned invalid-field errors for Suppress_from_Open_Request_Reports__c. No records were deleted, cancelled, or altered.

Recommended Next Step