Skip to main content

CALPADS error brief · IVR

IVR0116

Duplicates within File based on Primary Key
Severity
FATAL error — Must be corrected to post the record or certify the data.
Error type SERV — Student Services
Record type IVR

Official CALPADS rule

What CALPADS is rejecting

If two or more records exist in the file based on the file type's primary key fields.

Focus fields

Fields validated

25.04 - Reporting LEA 25.07 - SSID 25.08 - Reporting SELPA 25.10 - Special Education Service Code 25.11 - Special Education Service Provider 25.16 - Plan Effective Start Date

Recommended correction path

Suggested resolution

SERV primary-key fields in Version 18

  • 25.04 Reporting LEA
  • 25.07 SSID
  • 25.09 Reporting SELPA
  • 25.11 Special Education Service Code
  • 25.12 Special Education Service Provider Code
  • 25.17 Plan Effective Start Date

Location, frequency, and duration do not distinguish the primary key. Two rows sharing all six values still collide even when those descriptive values differ.

What the duplicates may mean

RowsLikely causeCorrection
Identical in all 17 fieldsDuplicate extraction, API retry, or one-to-many database joinRemove the duplicate and repair generation logic.
Same key; different locationTwo local records collapsed onto one CALPADS service keyApply the Version 18 rule for duplicate services, including the location where the majority of the service is provided.
Same key; different frequency/duration Multiple schedules or versions were exportedUse the most-used frequency and duration supported by the operative plan and current specification.
Services that should be separateService code, provider code, or Plan Effective Start Date was omitted or mis-mappedRestore the supported distinguishing value; never fabricate one.

Do not simply delete the second row. First determine whether it is truly redundant or evidence that two factual services were collapsed by the export. Version 18 specifically uses a different provider to distinguish a duplicate service.

Recommended correction path

  1. 1

    Group rows by the full primary key

    Preserve every duplicate and highlight all non-key differences.

  2. 2

    Compare with the operative PLAN

    Verify student, service, provider, plan effective date, location, frequency, and duration.

  3. 3

    Choose the supported correction

    Remove a true duplicate, correct a wrong key, or reconcile multiple service arrangements under the current SERV rules.

  4. 4

    Repair the extraction or API process

    Prevent recurrence across students and services.

  5. 5

    Validate uniqueness before resubmission

    Confirm every primary key occurs exactly once.

Official SERV IVR0116 page