Short Text: Required field is missing: Count Date Receiving Services for October 1 Child Count.
Long Text: Count Date Receiving Services is determined from the Ed-Fi element Receiving Services within the student School Association Wisconsin Ext resource. This element is missing or incomplete and is expected because the October 1 Child Count is included within this period of enrollment. Contact your vendor to understand where this information must be entered in your local SIS to transfer to DPI via the Ed-Fi API.
NOTE: If you have a third-party, special education vendor tool, the IEP begin date should be sent to WISEdata using this third-party, special education vendor tool. If you need help, please reach out to your SIS vendor support representative to learn how to submit this value. DPI cannot provide SIS specific support.
How to Fix:
- Verify the student’s enrollment dates at your school.
- Also check to see if the student has a student Special Education Program Association (sSEPA) record.
- Both an active sSEPA record and an active enrollment record are required in order for the October 1 Inclusion Count flag to be set to "True." Both values are needed to submit the Count Date Receiving Services October 1 data element.
- This value can be viewed on the Student Details screen in WISEdata Portal.
- Expand the gray “Enrollments” header to view the enrollment record.
- Expand the gray “Count Inclusion October 1” sub-header to view the “Count Date Receiving Services October 1” flag. This will display a value of Not Set because of the IEP dates.
- If the student was attending during the Oct. 1 Child Count and has an active sSEPA, then enter the required information for the October 1 Child Count field into your primary SIS to state that the child was receiving services as of the count date.
- NOTE for SUBMITTING Oct 1 FLAG: USE PRIMARY SIS
- If you have a third-party, special education vendor tool, the October 1 count inclusion flag (“Count Data Receiving Services Oct 1”)should be sent to WISEdata using your MAIN SIS. This data element is part of the student enrollment record. The enrollment record then pushes this value in to the SSEPA record. A third-party, special education vendor tool cannot edit values in the enrollment record – only in the SSEPA record.
- NOTE for SUBMITTING SSEPA DATES: USE PRIMARY SIS
- If you have a third-party, special education vendor tool, the IEP/ISP Begin and End Date should be sent to WISEdata using your third-party, special education vendor tool to edit the SSEPA record.
- If you DO NOT HAVE a third-party, special education vendor tool, the IEP/ISP Begin and End Date should be sent to WISEdata using your primary SIS.
- If you need help, please reach out to your SIS vendor support representative to learn how to submit this value. DPI cannot provide SIS specific support.
- If there is an issue where a student has a sSEPA record from a previous enrollment at another district that has since ended but not been closed, you may need to reach out to the other agency to correct sSEPA dates, and then the error.
- Update with a push to WISEdata Portal.
- You can use the “Queue Manual Validation and Import” option in WISEdata Portal. If you enter your email, check that the value has updated in WISEdata Portal when you receive your email notification.
- You can wait for the overnight validation and check WISEdata Portal the following day.
/msdyn_blobfile/$value)
Example: Penny currently attends Empire Elementary school as a first grade student. She enrolled in 2024-25 as a five-year-old kindergarten student and has attended all of the current 2025-26 school year. Penny’s record is throwing an error that she doesn’t have information on whether or not she was receiving special education services on the Oct. 1 count date. District Deb sees that Penny was evaluated over the summer between her kindergarten and 1st grade year, and that she qualified for special education services, and now has an active IEP.
Deb corrects the error by submitting all required SSEPA related data elements into her third-party special education vendor tool. She also ensures that all of Penny’s enrollment data elements are also correctly submitted.
Deb pushes a “Queue Manual Validation and Import” option in WISEdata Portal, and makes sure to enter her email (spelled correctly) to get the notification when her update is ready to view. She then check that the values were updated in WISEdata Portal on Penny’s Student Details screen when she receives the email notification.
Deb sees that the error is now removed.
Technical Details:
- Logic: Throw the error if
- (1.) sSA Ext is missing and student's Enrollment and SSEPA include count date - OR -
- (2.) sSA Ext is submitted but the Oct1 receiving services is missing and student's Enrollment and /sSEPA include count date.
- /sSEPA check can be from any school.
Throw after count date.
|
