...
- Unknown Timetable issues:
- Check for the existence of the following user procedure: uspuwkTimetable. This runs before the timetable is imported. If there is a user procedure then this may be updating data before coming through.
- Timetable only shows for 1 staff member
Check the following configuration key if this is set to true the both staff members will have a timetable created. This is false by default:
Timetabler AutoImport Timetable AllowDuplicates True/False If False only one staff member is assigned to the timetable record. This is to avoid duplicates in the Staff Timetable.
If True any staff members that are listed against the timetable record as assigned.
- Timetable entries without students are not imported.
Check the following configuration key. If this is set to true any timetable entries without students will be imported. If they have the same timetable going to multiple timetable groups the timetable may be duplicated for entries without students since we use the students to split up the classes. Note this key is not relevant for Yard Duties / Meetings / Not Available classes.
Timetabler AutoImport Timetable AllowDuplicates True/False If False only one staff member is assigned to the timetable record. This is to avoid duplicates in the Staff Timetable.
If True any staff members that are listed against the timetable record as assigned.
- Timetable Import is running slowly:
- Check which version the school is running. There are specific fixes for each version. Running the wrong version could result in issue.
- Version 70 - There was a slow trigger created as part of version 70. See DSY-21092 for fix.
- Extras are not importing and are not in the wkxiTimetableSubstitutes table:
- Try running the import into the work tables manually. They may have non-numeric period numbers.
Code Block language sql title Manual Import to work tables EXEc spuwkTimetable @TimetableCode = '2021T1' SELECT * FROM wkxiTimetableSubstitutes WHERE TimetableCode = '2021T1'