A release announcement will be posted on PowerSchool Community when the installer is available for download. Refer to 2026 State Reporting Releases for release dates.
|
Reference |
Summary |
Release Note |
|---|---|---|
|
PSSR-429831 |
All States/Provinces: Discipline Incident Letter Update |
Discipline Incident Letters: V2.1 Resolved an issue where the Discipline Incident Letters report displayed an incorrect Behavior Policy Description. The report now correctly pulls the Policy Description mapped to the selected Behavior Code(s) in the incident. |
|
PSSR-410230 |
All States/Provinces: Student Test Result Update |
Navigation: Start Page → Select Student → Academic Records → Test Results → New/Edit Test Results Users can now enable Change History on the Student Test Results page, allowing all updates—including scores—to be tracked. |
|
PSSR-432291 |
Data Entry: Track Description and Types |
A new Track Information section has been added to the School Info page under District Management → School Info, allowing Oklahoma districts to enter and manage a Description and Type for each of the six school calendar tracks (A–F). This supports Oklahoma DOE requirements for the Calendar Summary object for SIF Unity. Track Information section: A new section displays tracks A–F with their Description and Type. Administrators can add, edit, and delete track records using slide-out drawers.
The track data is stored per school year (via
|
|
PSSR-422847 |
Enhanced Track Configuration for Calendar Publishing |
Track calendars (A–F) now use configurable Track Names, Descriptions, and Types to correctly publish the associated information from the new Track Information section. When Track Information is entered, the DEX system publishes the Calendar Description and Calendar Type using the Calendar Summary derived from the corresponding track data. The Calendar Summary for the in‑session calendar continues to use its existing mappings. The Calendar Description follows the format: “{Track Description}; Track: {A–F}”. |
|
PSSR-430236 |
Improved Visibility for Staging Errors in Data Exchange |
Data staging errors can occur due to variety of reasons when the SQL used to generate the data fails. Common causes include key‑constraint violations, single‑row sub-queries returning multiple rows, and syntax issues. The DEX system now identifies and reports staging errors more accurately. When a staging failure occurs, the process logs the issue clearly and avoids showing misleading success messages based on cached data. Treating these failures as publishing errors improves visibility for users and helps them take corrective action. |
|
PSSR-431451 |
SSE and SAS Objects Update for Charter Schools |
Attendance Summary: Version 1.2
A new “Is Charter District?” setting has been added to the Compliance Tab on District Information page to support accurate publishing for charter districts.
Also, the format for the Calendar Summary reference in the Student School Enrollment object is now formatted with dashes. |