CALPADS error brief · IVR
IVR0116
Official CALPADS rule
What CALPADS is rejecting
Focus fields
Fields validated
11.05 - School of Attendance 11.06 - Academic Year ID 11.07 - SSID 11.13 - CTE Pathway CodeRecommended correction path
Suggested resolution
CALPADS SCTE correction guide · Fatal input validation
IVR0116: Duplicates within File based on Primary Key
The uploaded SCTE file contains two or more rows with the same school, academic year, SSID, and CTE pathway—the SCTE primary key.
Official CALPADS rule
Fields validated: 11.05 School of Attendance; 11.06 Academic Year ID; 11.07 SSID; 11.13 CTE Pathway Code
Each primary-key combination may appear only once in a submitted SCTE file.
Recommended correction path
- 1
Isolate every duplicate set
Group the file by the four primary-key fields and retain the complete duplicate rows, source record IDs, and export context.
- 2
Compare all non-key values
Check student identity and completion-year values. Determine whether the rows are identical or expose conflicting source data.
- 3
Trace the duplication upstream
Review pathway rosters, course-to-pathway joins, student program records, report filters, appended files, and repeated extraction steps with the CTE lead and SIS analyst.
- 4
Keep one accurate source record
Consolidate or correct the authoritative data and extraction logic. Remove a row from the upload only after establishing which representation is valid.
- 5
Regenerate and test uniqueness
Create a fresh file, run a primary-key duplicate check before upload, post it, and confirm the student’s pathway appears once with the correct completion year.
Where this correction sits in the 2026–27 calendar
Dates are from the current CDE CALPADS 2026–27 calendar. Verify the official calendar before acting because dates can change.
Before closing the ticket
- Record the duplication mechanism.
- Run the uniqueness check across the entire SCTE file.
- Reconcile distinct completer counts with the CTE coordinator.
Official references and practical support
SIS and extract support
Start with your vendor’s current California/CALPADS documentation. Paths and field mappings vary by product and district configuration. Inclusion is not an endorsement; access may require a customer account. Links verified August 14, 2026.


































































