State Reporting 23.3.2.0 Release Notes

Problem: The order and timing of deletes were not always occurring correctly based on dependencies of each resource. For example, when a section is deleted, events are generated for section, studentSectionAssignment, staffSectionAssignment, etc. These records are processed in any order, however, a section cannot be deleted until all dependent resources have been deleted. This resulted in a failed delete with the state ODS and this failure is not communicated back to the user, thus leaving the ODS and PowerSchool out of sync.

Solution: When delete events are published, they will now occur with the lowest record first back up to the highest record. This will result in studentSectionAssignment and staffSectionAssignment being published before the section is published. This may not work correctly each time due to simultaneous publishing. If a record fails, it now appears in the Errors section on the dashboard with an error from the ODS stating that there is a dependency preventing the record from being deleted. The record will then retry the delete every 10 minutes up to 1 hour. After 1 hour, the record will remain as an error and reconciliation will need to be run to remove the dependencies.