GetTimetable/Synergetic: Difference between revisions

From UmsWiki
Jump to navigation Jump to search
Kia (talk | contribs)
Kia (talk | contribs)
No edit summary
Line 10: Line 10:
Name of the setting.
Name of the setting.


=== Connection ===
====SQL Server====
DNS or IP address of the Microsoft SQL server where the Synergetic database is stored.
====Database name====
Synergetic database name.
====Username====
SQL Username to access database.
====Password====
SQL Password to access database.
===Increase identifier===
This is only used in UMS when there is 2 or more administrative systems of the same type extracted into the same UMS database/installation.
This must match the one under the data source for templates.
===[[GetTimetable/Export_settings|Export settings]]===
===[[GetTimetable/Export_settings|Export settings]]===
===Add year to groupname===
When UMS extracts classes from Synergetic it will add "'''_FileYear'''" to the end of the groupname.
This must match the one under the data source for templates.
===Add semester to groupname===
When UMS extracts classes from Synergetic it will add "'''_ActualSemester'''" to the end of the groupname. This comes after '''FileYear''' if it is selected.
This must match the one under the data source for templates.


==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

  1. Date = 04-02-19
  2. Start time = 08:40
  3. End time = 09:43
  4. Classcode = PKMQ
  5. FileYear = 2019
  6. 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'