Univention Bugzilla – Bug 50115
migration from old importer to new
Last modified: 2020-04-17 14:33:10 CEST
When importing for the next school year via the *new* importer it collides with the existing objects. They've been imported via the legacy csv import and lacking the uid attributes; also there are no counter / index objects. Of course the existing students and teachers only should change classes and should be reused without impacting changes. I guess we need some kind of migration script to add the missing attributes (record_uid, source_uid) and proper values as well as the counter / index objects.
Another customer affected.
I changed the title, correct me if I'm wrong: this issue only occures if accounts have been imported with an "old" import mechanism but the school year migration is done with the "new" mechanism (?) This reduces IMHO the importance
(In reply to Ingo Steuwer from comment #3) > I changed the title, correct me if I'm wrong: this issue only occures if > accounts have been imported with an "old" import mechanism but the school > year migration is done with the "new" mechanism (?) > > This reduces IMHO the importance 6 months after the incidents and no more than 2 tickets I assume this really is of a lesser importance. If this still happens I guess we already have a way to work around.
(In reply to Nico Stöckigt from comment #4) > (In reply to Ingo Steuwer from comment #3) > > I changed the title, correct me if I'm wrong: this issue only occures if > > accounts have been imported with an "old" import mechanism but the school > > year migration is done with the "new" mechanism (?) > > > > This reduces IMHO the importance > > 6 months after the incidents and no more than 2 tickets I assume this really > is of a lesser importance. If this still happens I guess we already have a > way to work around. I unset the "Waiting for Support" flag then also.