The release notes detail the new features, bugs, and known issues in release 2025.09.
Features
There are no new features in release 2025.09.
Bugs
The table Bug fixes details the bug fixes in release 2025.09.
|
Reference |
Header |
Business impact |
|---|---|---|
|
618865 |
Staging UI API calls - duplicate records |
A ticket was raised that pointed to duplicate records being returned by the APIs during batch processing by systems using the APIs for reporting processes. Initial investigations found no duplicates in the tables themselves. Azure logging was researched and no specific pointers to duplicate rows were found there. An environment was created with a large number of Unit Enrolments and after B2G submission found that for records with errors or warnings, some duplicate records were indeed returned. Further examination has found malformed joins in Entity Framework. An interim fix has been applied by adding a sort-by clause to the API call if one was not already passed in by the caller, this forces SQL Server to ensure there are no duplicates and bypasses the Entity Framework problem. This has been done for Students and Unit Enrolments, the most commonly reported duplicates. This bug has been duplicated and the work to correct the malformed joins in Entity Framework will be ongoing and released once completed. |
Known issues
There are known issues for the criteria builder, download records, and notifications.
Criteria builder
The known issues for the criteria builder are detailed below.
- URL length for bookmarking
-
URLs containing filter strings are limited to approximately 2,000 characters. Realistic scenarios suggest that a search with eight criteria creates a URL with around 1,000 characters. Complex criteria can be built, but customers should monitor URL lengths manually as the criteria builder does not currently track this. The message that the browser might return is The resource you are looking for has been removed, had its name changed, or is temporarily unavailable.
- Criteria 'is one of' and spaces
-
Avoid spaces when entering multiple criteria values. For example, entering a, b, c will only return results for a. Therefore, enter criteria without spaces a,b,c to correctly return results for all values. The team is addressing this issue to remove spaces automatically.
- Toggling element numbers clears filters
-
If a filter has been applied and the user toggles the element numbers on or off, the filter is cleared. This is because the fields in the criteria builder need to be refreshed based on the element number needing to be displayed.
Attention.This issue will not be addressed and customers will need to ensure the element number has been toggled correctly before creating a filter.
Download records
The download is limited to 10,000 records due to HTTPS timeout of 30 seconds.
Notifications
The known issues with notifications are detailed below.
- Notification status
-
TCSI notifications do not maintain a lifecycle status as documented by the TCSI website. As such, some notifications may not be deleted automatically. Examples of this are the SVE and VER notification categories, where during our testing these notifications were not updated or deleted. This could be due to the extensive age of the data.
If resolved notifications are still present in the Notifications user interface, then users with the Delete Notifications permission can manually select and delete them permanently to complete the tidy up of the outstanding list of notifications. If the manual deletion of some of these categories is problematic, please raise it as a concern.
If you manage these types of notification categories using integration and internal reporting, the clear-down process can be updated in a manner similar to CHE, CHA, S2E, and SIS notifications. That is, remove the notifications automatically once the notifications are older than seven days.
- Notification clear-down duration
-
Tests in a tenant with over three million notifications show that it takes many hours to complete the notification clear down. Although this was in a test environment, it still raises a risk. Therefore, customers with several million notifications should enable the Notifications Automation on a Friday. The clear-down process then starts at 2 AM on Saturday morning. Enabling the clear-down process on a Friday should reduce any impact on online users of the solution rather than if it runs during the week and it subsequently runs into business hours.