SIS ID Already in use message
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
We have an issue in which a we cannot push out a course shell to a teacher because Canvas gives us a message that tthe SIS ID is already assigned. The teacher had an account that was manually created, but has since been deleted; and the SIS ID is not assigned to anyone else in the system. How do we manage the Canvas system so it allows the assignment of the SIS ID within Canvas?
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi, @ray_senesac .
Many items (including users and courses) are not physically deleted in Canvas. They are merely logically deleted, still existing in the database but hidden from the UI.
My recommendation is to upload a SIS Import CSV file using the "change_sis_id.csv" format shown here: SIS Import Format Documentation - Canvas LMS REST API Documentation. The old_id should be the one that you wish to reuse. For the new_id I suggest using the old one with an extra character that wouldn't appear in an actual id. I typically add an underscore at the end. After you upload, you should be able to use the old id as if it had never been used before.
(Before they introduced this CSV format, we had to reactive the old id with the object type's respective CSV format, edit it in the UI, and then delete it again.)
Best,
Nelson
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
To prevent it, you would need to make sure that before a user is deleted or a login is deleted the SIS ID is removed. We do this with our blueprint courses since we manually set these and sometimes delete them to replace them with a new version.
This is still prone to user error/oversight, but being aware of this and building into any processes that result in user and/or login deletions will help reduce the likelihood of the issue in the future. You might be able to do a theme modification to hide the delete options when a user has an SIS ID, but that wouldn't prevent deletes by API (if the user has permission) or SIS Import.
If anyone else has any suggestions for how they handle it differently, I would be interested in knowing too.
This discussion post is outdated and has been archived. Please use the Community question forums and official documentation for the most current and accurate information.