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 :)
Thanks for the info. I was afraid this was the case. This is not so good news. It increases the risk of accidently deleting members (students) from existing teams from previous periods. All it takes is one mistake when transferring student data from SIS… So, this means we must include all the members (students) of all the teams of previous sections with every new SDS file transfer. I wonder what this end of term functionality that Matt mentioned will do? Hopefully pause sync of the sections of previous school year :)
We will try to be smart about the end-of-term functionality that is coming, and I will make sure the engineers see your feedback. Thanks!