Skip to main content

CALPADS error brief · IVR

IVR0116

Duplicates within File based on Primary Key
Severity Fatal
Error type Input Validation
Record type IVR

Official CALPADS rule

What CALPADS is rejecting

Two or more records exist with the same primary key fields.

Focus fields

Fields validated

20.05 School of Attendance 20.07 SSID 20.13 Incident ID Local 20.14 Student Offense Code

Recommended correction path

Suggested resolution

CALPADS SOFF correction guide · Fatal input validation

IVR0116: Duplicates within File based on Primary Key

Two or more records exist with the same primary key fields.

Official CALPADS rule

Severity: Fatal   Type: Input Validation

Fields validated:

  • 20.05 School of Attendance
  • 20.07 SSID
  • 20.13 Incident ID Local
  • 20.14 Student Offense Code

Recommended correction path

  1. 1

    Confirm the intended student and incident

    Compare SSID, local student ID, school, Reporting LEA, academic year, Incident ID Local, and the source discipline record before changing anything.

  2. 2

    Identify the failed relationship

    Determine whether the problem is a missing required value, enrollment ownership, CDS relationship, academic year, SSID, submitter role, or duplicate primary key.

  3. 3

    Bring in the right owners

    Coordinate the CALPADS coordinator, registrar, site discipline administrator, SIS analyst, and—when applicable—the special education case manager or SELPA data lead.

  4. 4

    Correct dependencies in order

    Repair legitimate SENR, CDS, account-role, SIS, or extract data first. Never manufacture enrollment, substitute an SSID, or broaden access merely to make SOFF post.

  5. 5

    Verify the accepted relationship

    Confirm the corrected SOFF record under the intended student and incident, reconcile its SINC/SIRS companions, and check the next extract for recurrence.

Where this correction sits in the 2026–27 calendar

Capture throughout the yearKeep incident IDs, offenses, results, statutory-offense decisions, weapon details, and special-education safeguards aligned while evidence is fresh.
EOY 1 submission window opens; Student Incidents are part of the consolidated EOY 1 collection.
CDE’s recommended date for reaching zero EOY 1 errors.
EOY 1 amendment window closes; required SELPA approval must be complete.

Dates are from the current CDE CALPADS 2026–27 calendar. Verify the official calendar before acting because dates can change.

Before closing the ticket

  • Confirm the corrected SOFF record under the intended student and Incident ID Local in CALPADS.
  • Reconcile the related SINC parent and every applicable SIRS/SOFF child record.
  • Document whether the defect arose in source evidence, coding, translation, enrollment, configuration, or extract logic.
  • Check other incidents affected by the same local rule before EOY 1 certification.

Official references and practical support

SIS, discipline, and extract support

Begin with your vendor’s current California/CALPADS documentation. Incident models, local offense codes, weapon mappings, and SINC/SIRS/SOFF extract paths vary by product and configuration. Inclusion is not an endorsement; some resources require customer access.