Follow up note.... if you choose to go the "Full Batch" update route, then that effectively means that Banner contains all the requisite information about roles for the LMS (teacher, student, ta, designer, observer etc).
Our Banner instance only knows/cares about teachers and students, meaning that any additional roles are added directly in the LMS via the UI. Teaching Assistants, Grad Assistants, Observers, Designers, ITCs, etc all fall into this case (added via UI, not via SIS).
If you do a full batch update, then it will blow away any custom enrollments. As explained to us by Canvas support, the full batch update is the "nuclear" option.
Quote from Canvas' website about SIS imports:
CAUTION! This is sometimes referred to as the nuclear option because it can
delete large data sets without any prompt or warning for confirmation. This option
will affect only data created via previous SIS imports.
So..... if Banner knows "EVERYTHING" about your enrollments, then batch updates are the easiest method to use. If you need to add custom role'd people to the LMS, then full batch updates will blow away those customizations.
Sidenote: we run our process every 2 hours, and process about 90,000 enrollments, 6500 courses, 6500 sections, and 40,000 users (all part of the original SIS Zip that comes out of Banner). Our diff process results in only a few hundred (at most) changes every 2 hours though, which makes the process extremely quick once we upload to canvas.
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.