A release announcement will be posted on PowerSchool Community when the installer is available for download. Refer to 2026 Provincial Reporting Releases for release dates.
|
Reference |
Summary |
Release Note |
|---|---|---|
|
PSSR-422511 |
All States/Provinces: Student Incident Profile Report Update |
Student Incident Profile Report: Version 1.15 The Student Incident Profile Report now lets users control incident grouping in the report output. The Page Break option appears under Order Report By. The Page Break options are Student, Incident, and None. For details, see the State Reporting Online help. |
|
PSSR-421726 |
All States/Provinces: Attendance Profile Report Update for Tracks |
Attendance Profile Report: Version 1.13 The Attendance Profile report has been updated and will now honor a student’s track (if set) when calculating membership, attendance, and absence data. |
|
PSSR-422733 |
All States/Provinces: Learning Preferences Code Management Page Update |
The Learning Preferences Code Management page (path below) has been updated and will now display all entered/saved Learning Preference codes, regardless of the presence of an Effective Start Date value.
|
|
PSSR-419980 |
All States/Provinces: New Incidents and Details Report |
Incidents and Details Enterprise Report: Version 1.0 A new Incidents and Details report is now available within Enterprise Reporting. Click here for more information on Enterprise Report setup and use. |
|
PSSR-419584 |
Correction to Language Dropdown Option |
Corrected spelling errors in multiple locations where the language “Aramaic” was previously misspelled as “Aramic.”
|
|
PSSR-402437 |
Course Offering - Description Update |
This release updates the Course Offerings displayed throughout the UI to ensure they align with the Ministry’s most recent official descriptions. Users can now access accurate, up‑to‑date values in the Course Offering drop‑down list when navigating through the school and district courses pages. These updates provide clearer guidance and improve decision-making by ensuring all Course Offering codes reflect their intended Ministry definitions. Navigation: School Management, Courses and Programs, Course Sections, School Management, Courses and Programs, and then Courses
|
|
PSSR-420151 |
Daily Attendance Record Updates |
Daily Attendance Record: Version 3.7 Updated the Daily Attendance Record report to correctly handle students enrolled in only one period. The G (General Absence/Grant) code is now accurately applied to the appropriate date for single‑period student enrollments. |
|
PSSR-334705 |
EQAO Extracts - Report UI - Dates Not Populated when Math 9 Spring is the Default Submisison |
EQAO Extracts: Version 8.1 This update resolves an issue in the EQAO interface where the Math 9 Spring assessment did not automatically populate the “Include Courses Ending Between” date range. When loading the EQAO page, the system correctly defaulted to Math 9 Spring, but the “Include Courses Ending Between” date range fields appeared blank instead of showing the expected default dates. Users were required to manually enter the dates or toggle to another submission and back as a workaround. This fix ensures that when Math 9 Spring loads by default, the correct date range is automatically populated, providing accurate defaults and removing the need for manual intervention. |
|
PSSR-377142 |
EQAO Extracts – Math 9: Handling Students in Multiple Concurrent Math Classes |
EQAO Extracts: Version 8.1 This update resolves inconsistent output in the EQAO Math 9 extract when a student is enrolled in more than one qualifying math course during the same Winter or Spring administration period. The report now consistently applies the correct selection logic: when both Applied (1P) and Academic (1D) courses are present, the Academic (1D) course is extracted; when both 1P and 1W are present, the 1W course is extracted. If the student is enrolled in two qualifying courses of the same level (1W, 1P, or 1D), the report will extract the course with the latest enrollment date or, if the dates match, the most recently entered record. These rules are now applied uniformly regardless of where the report is run (district office, school level, or for a selected student), ensuring the same course is consistently selected. |
|
PSSR-420077 |
New OnSIS VErification Report - Section A Courses for Grades 9 - 12 |
Additional References: PSSR_420059, PSSR-420064, PSSR-420072 OnSIS Verification - Details Report: Version 3.0 OnSIS Verification - Summary Report: Version 3.2 This release introduces a new OnSIS Verification Report designed to display detailed information for validating Classes with a single segment (course) for Grades 9 to 12. To ensure complete and accurate data generation, users must first import the appropriate PAE files for the submission and then run the OnSIS Secondary Report with the Save XML flag selected. These steps ensure all necessary XML data is properly stored before executing the new verification report. |
|
PSSR-418893 |
OnSIS Data Validation - Night School Issue Finding OLC Historical Grades |
OnSIS Data Validation: Version 4.5 When a student has an OSSLT‑E test with an Alpha Score indicating they are working toward the credit through OLC, the system previously required the Store Code for the historical grade of the OLC course to be defined for the corresponding TermID in order for it to be recognized as a final grade. The report has now been enhanced to identify the appropriate OLC final mark record regardless of the Store Code definition. |
|
PSSR-424567 |
OnSIS Secondary - OYAP-FAST Logic Updates |
OnSIS Secondary School Submission: Version 22.8 This update enhances OYAP‑FAST reporting logic by automatically determining the OYAP_FAST_FLAG and generating the appropriate OYAP‑FAST segment based solely on the student’s OYAP‑FAST program status, independent of the UI OYAP‑FAST Participant flag, thereby eliminating the need for manual updates. The system now evaluates program data to determine whether the student is Active, Completed, or Dropped and applies the corresponding reporting rules, including ADD/UPDATE actions for active or completed programs and DELETE actions for dropped or removed programs. Programs started and dropped within the same submission are not reported, while programs started and completed within the same submission are included. When multiple OYAP‑FAST enrollments exist, the system selects the correct one using defined sorting logic. These enhancements ensure accurate and consistent OYAP‑FAST reporting aligned with ministry requirements. |
|
PSSR-420078 |
OnSIS Secondary - SAVE Class ML Segments into Permanent Tables |
OnSIS Secondary School Submission: Version 22.8 The OnSIS Secondary School Submission Report has been enhanced to store Class Segment data in the permanent table S_ON_XML_CLASS_S and the Class “Segment” data in the permanent table S_ON_XML_SEGMENT_S when the Save XML option is selected during report execution. This improvement ensures that all segment‑related XML data is captured and retained for downstream verification and reporting processes. |
|
PSSR-420956 |
OnSIS Secondary Submission - Dropped Course Showing on the report |
OnSIS Secondary School Submission: Version 22.8 This fix addresses an issue in the report where a course was incorrectly reported when a student started and dropped the class within a submission period, then re‑enrolled in the same course in the following submission period. In these cases, the class should not be included in the current submission, regardless of whether the later enrollment has marks. Previously, the system generated an ADD record for the dropped course, causing students who were not active on the count date to appear on course lists in OnSIS. The reporting logic has been updated so that courses fully started and dropped within the submission period are excluded, ensuring only valid, active course enrollments are reported for the count date. |
|
PSSR-375759 |
Secondary Report Cards - Updates to Prevent Report from Failing |
Secondary Report Cards - GradeBook: Version 9.0 The report error‑handling logic has been enhanced to prevent the report from failing when certain fields exceed their maximum character limits. Previously, oversized values in fields such as Principal Name, Council Chair, Student Mailing Address, and the student’s Legal Name fields (Legal Surname, Legal First Name, Legal Second Name) caused the code to fail and generated an error log page. With this update, the system now handles these scenarios gracefully by preventing the error log from being generated and instead displaying a clear, meaningful message to inform users of the issue. |