Things to Know
- Information on this page is subject to change. This page was last updated January 10, 2025.
- Features below are not functional in the application until UAT release date.
- You may need to clear your cache in order to enable changes in this release.
Release Summary
Here's a quick overview of the updates in this release:
- Fixed unnamed fields in the SP Org Unit report causing integration and processing issues.
- Resolved a 500 error during unit uploads and improved error messaging.
Release Dates and Downtime
Release dates are subject to change. Release date changes will be noted in the Change Log below.
Downtime required: None
| UAT-SG | January 7th @ 12:00 PST |
| UAT-AU | January 7th @ 12:00 PST |
| UAT-UK | January 7th @ 12:00 PST |
| UAT-CA | January 7th @ 12:00 PST |
| UAT-US | January 7th @ 12:00 PST |
| Prod-SG | TBD |
| Prod-AU | TBD |
| Prod-UK | TBD |
| Prod-CA | TBD |
| Prod-US | TBD |
Change Log:
Jan 10: Prod dates (previously anticipated for Jan 9th) have been changed to TBD at this time while an issue is addressed.
Detailed Release Notes
Resolved
Issue: A change to the SP Org Unit report layout introduced unnamed fields in the data output. These additional fields caused integration code to misinterpret the file structure, resulting in:
- Incorrect data being sent for processing
- Jobs getting stuck in a loop
Resolution: The issue was resolved by updating the SP Org Unit report layout to exclude the unnamed fields.
Issue: Attempting to upload units via the "api/v2/administration/batch/upload/unit" endpoint resulted in a 500 error response with no informative error message.
Resolution: The issue has been resolved by updating the upload functionality to handle the edge case properly. Units now import successfully, and in the event of a failure, a clear and informative error message is provided.
(Ref ID: 26.02.02_Patch)