Infinite Campus and Inactive Enrollments

[MrReed]

Over the summer, we were switched to OneRoster 1.2 for rostering from our SIS

After this update, we have a strange new issue that is affecting student enrollments in a specific situation.

Our issue occurs when a student:
1) Is enrolled in a specific section (in the SIS)
2) Has a schedule change dropping that section (in the SIS)
3) Has a later schedule change..and is added back to that same section (in the SIS)

The student is now actively enrolled in the section according to the SIS, but Canvas marks their enrollment as "inactive" every single night in our data sync because it sees an "end date" on their enrollment (but ignores the start date that is newer)

Even when we add the students to the Canvas roster manually, the nightly sync will mark them as inactive again.  So we have several students that lose access to their current course every night.

This is an issue that is new to us with the OneRoster 1.2 switch over.  Does anyone have any experience with this situation?  (we are still waiting for Canvas support to address our ticket currently)

[tom_ashley]

This exact issue happened to my district. Once Canvas SIS support techs got back us, they resolved it quickly.

[JustinBrecht · Accepted solution]

Hello,

We too had this exact same issue. word from word, same process of switching from 1.1 to 1.2 one roster interoperability connector using Infinite campus . Canvas support SIS team was able to fix the issue. With the explanation that "This issue was caused by Infinite Campus sending student enrollment information in a format that wasn't quite what we expected. We made an adjustment to your integration to work around the issue."

[FrankieKirk]

We are also experiencing this issue after the OneRoster 1.2 upgrade.  In order to actually remove the inactive status for those students, not just reactivating the user in the Canvas course, the end dates in IC would have to be removed.  

@JustinBrecht - Thank you for posting your comment, which I am going to copy and paste into the Canvas Support ticket that I created for this issue.