GetTimetable/Synergetic: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
|||
Line 10: | Line 10: | ||
Name of the setting. | Name of the setting. | ||
===[[GetTimetable/Export_settings|Export settings]]=== | ===[[GetTimetable/Export_settings|Export settings]]=== | ||
==FAQ== | ==FAQ== |
Revision as of 09:41, 14 April 2020
Prerequisites
The semester start date has to be week 1 (day number 1 to 5) in the timetable. Extraction will not work correctly if this is not the case.
Setup
Format and content
Description
Name of the setting.
Export settings
FAQ
UMS uses this for SQL extraction
select * From vStudentTimetableFullAll JOIN FileSemesters ON (FileSemesters.FileYear = vStudentTimetableFullAll.FileYear) And (FileSemesters.FileSemester = vStudentTimetableFullAll.FileSemester) LEFT JOIN pvCommunity ON vStudentTimetableFullAll.StaffID = pvCommunity.ID Where StudentID = 15731 And ClassCode = '08Sci3' order by ClassCode
The CREATE UNIQUE INDEX statement terminated because a duplicate key was found for the object name 'dbo.ImportFromDB_SkemaBrikker
This could be the result of someone scheduling the same class with PeriodNumberSeq = 1 and PeriodNumberSeq <> 1
It will give an error that ends with something like this.
The duplicate key value is (04-02-19_08:40_09:43_PKMQ_2019_1, 1)
This can help find the problematic timetable block. Decipher it like this
- Date = 04-02-19
- Start time = 08:40
- End time = 09:43
- Classcode = PKMQ
- FileYear = 2019
- ActualSemester = 1
The date is calculated based on 2 weeks schedule. This means the date is not too useful.
You can look in UMS using this SQL to find the Day number
Select *
From ImportFromDB_TimeTable_Synergetic
Where
Skemabegivenhed_ID = '04-02-19_08:40_09:43_PKMQ_2019_1'