Vision: BehaviourEventsAffectedStudents Odata Feed
We have introduced a new OData feed, BehaviourEventsAffectedStudents, to provide a clearer and more reliable way to identify students affected by behaviour events. This removes the need to identify affected students from names and allows records to be linked directly to the existing Behaviour Events feed using unique identifiers.
Historical data will be transferred for behaviour events within the current academic year only. Ongoing changes will be synchronised via scheduled transfers, manual transfers and real-time updates (if enabled).
What's New
Each row represents a single affected student associated with a behaviour event.
When a BehaviourEvent has multiple affected students:
- A separate row is created for each affected student.
- The same EventRecordId may appear on multiple rows.
- AffectedStudentId and AffectedSchoolStudentId can be used to uniquely identify the student.
If a BehaviourEvent has no affected students, no rows are returned for that EventRecordId.
The existing BehaviourEvents feed remains unchanged, including column names, column order, values and integrations.
Notes
- EventRecordId can be used to link records between the BehaviourEvents and BehaviourEventsAffectedStudents feeds.
- If transfers are disabled and later re-enabled, missed changes are automatically caught up for behaviour events within the current academic year.