Why are Extract changes needed as a result of the Post-Redesign Project?

Background: Since CALPADS launched their new environment, many customers are having their files rejected because of overlapping record errors. These files were never rejected before. For example, when a student exits one school and enrolls in another school in the district, the file is rejecting the 2nd enrollment record that is in the SENR file. CALPADS recently admitted that there are two sets of file validations that are running when a file is submitted. Instead of just checking for internal file errors as they originally planned, a second file validation process checks for conflicting data within the existing CALPADS records. A single error in ANY of these validations causes the entire file to be rejected. CALPADS has been communicating to both LEAs and Vendors that they have been investigating how to resolve these errors for a couple of weeks. 

Today, at the regularly-scheduled Vendor Call, they informed all SIS Vendors that the new CALPADS system MUST run both these validation checks before accepting any records into their system, and they will NOT be going back to allowing some records to post and rejecting only the problematic ones. Therefore, the ONLY way forward is to make the Vendors change how the extract files are created, to allow them to pass into their system. We had NO warning that this directive would be coming, and are left with no other options. 

Therefore, we are beginning to make immediate changes to our CALPADS File Extraction process. The only way forward, rather than create one file (SENR) with all the student enrollment changes, we must create 3 files, one with records to be deleted, one with records to be updated, and one with records to be added. This will be true for ANY CALPADS extract file, except for full replacement files.

We are beginning this work immediately and will ship changes as soon as they are ready. We will be concentrating on making changes to the Enrollment Update files first, then the EOY files, and finally the remaining CALPADS extract files. We will be updating this post as we go along, with the exact plans moving forward, let you know when releases are ready for deployment, and also work on updating our documentation since that will also need to change.

We ask for your patience as we respond to these new challenges. Rest assured, we will do everything in our power to help make this change as easy for our customers as possible.