Forum Discussion
Possible problems with periodic sync aproach?
Thanks for the quick answer. I know that the sections stay intact but what about the students if in the new CSV-files there is no mention of the section listed in previous CSV-files. Here is the scenario:
Sync 1 with CSV files batch 1: Section A (SIS ID 11111) with students
Sync 2 with CSV files batch 2 (same sync profile as Sync 1): Section B (SIS ID 2222) with students . In the batch 2 there is no mention of Section A in the section CSV file nor the student enrollment or teacher roster CSV files!
What will happen to Section A after Sync 2 is run?
- Section A will be gone and students too (I beleive this will not be the case)
- Section A will be there but with no students
- Section A will be there with the students
So, I want to find out how does the comparison actually work between different CSV-files :)
Hello.
Despite of all answers, here are my 2 cents.
When you archive a section (it is not included anymore in the SDS data), the O365 Group and the attached Team in the cloud will remain at the state, where they are left at that point. You do not have to include those groups in further sync data.
SDS will not delete Groups/Teams.
This is not only tested, but running in production (several tenants/ > 100k Students) and actually, overall concept is based on the fact that "archived" sections will stay in the cloud until deleted by some other measures than SDS.
Best Regards
Marko
We have also done archiving at the end of the term. And it works just like you describe it. But we are looking for a "mid-term" solution to secure courses of previous periods. I guess we use a different sync profile for each period or build a database of some sort inbetween SIS and SDS as a "safety measure".