Skip to main content
Skip table of contents

State Reporting 24.4.1.0 Release Notes

A release announcement will be posted on PowerSchool Community when the installer is available for download. Refer to 2024 State Reporting Releases for release dates.

Reference

Summary

Release Note

PSSR-343354

Ed-Fi: ESOL Dual Language Immersion Misspelled "Lanuage"

LanguageInstructionProgramServiceDescriptor ‘Dual Lanuage’ misspelling is corrected to 'Dual Language'.

PSSR-339996

Ed-Fi: Publishing Errors for Student Assessments

Error occurs when publishing student assessments due to unique constraint violation in the cst_pubpublished table (ORA-00001: CST_PUBPUBLISHED_U1). The issue arises from duplicate entries in the StudentAssessmentScoreResults data, leading to process failure. The expected behavior is for student assessments to be published successfully without errors. If there are duplicate assessments of the same name, the most current result will publish.

PSSR-336978

Ed-Fi: SC-ALT Assessment Customization Mapping

This ticket includes the SC-ALT_AssessmentCustomization requirements, per SCDE. The vendor namespace has been updated per SCDE to uri://cambiumassessment.com/AssessmentRoster.

PSSR-339821

Request a Flag to Exclude School Enrollments

The Student School Association resource has been updated to exclude the enrollments from publishing which are marked Yes for Exclude this enrollment record from ED-FI field.

PSSR-339219

SCDE Ed-Fi: Student Selection Criteria Change

The Student School resource has been updated to not publish if there are multiple enrollments for a student on a single day in the same school and the enrollment has an exit code GC.

PSSR-342775

Student Programs Stuck in Processing Where ‘Instructional Settings’ Field Has A Value

The issue involves Student Programs getting stuck in processing when the Instructional Settings field contains a value. When students with a value of SE in the Instructional Setting are viewed on the dashboard. Their records remain in processing status indefinitely. The expected behavior is for these records to no longer get stuck in processing.

JavaScript errors detected

Please note, these errors can depend on your browser setup.

If this problem persists, please contact our support.