Community

Making REST calls can be difficult without coding skills. However, the SIS integration is relatively easy to use with some basic Excel know-how. If you want to do batch updates, start here. You can upload CSV files (simple tables with a header row) to add hundreds or thousands of courses, accounts, enrollments, etc at a time. And if you add the same account/course/enrollment again (with the same unique SIS ID for the course/student/etc) it won't add a duplicate, it'll update the existing item. So you can also UPDATE thousands of entries at a time. The things you can manage with SIS files includes Users (teachers, students, admins), Accounts (sub accounts, don't confuse with users), Terms, Courses, Sections (of courses), Enrollments (linking users to courses), Groups and Group Memberships (dividing course enrollments into smaller sets for collaboration and group assignments), User Observers (allowing parents/employers to keep tabs on their student), Admins (to grant additional powers to staff), Logins (only needed if you manage multiple auth methods for users), and Change SIS ID (in the rare case you need to manipulate the normally fixed SIS IDs). This covers the most common mass-insert and mass-update needs, and just requires some basic spreadsheet skills. Can you do more with the REST API? Absolutely. Of the things you listed, this can manage batch publishing. If you use blueprint courses (which I highly recommend) then you can also batch create courses from the blueprints which removes the need to batch-copy content. Batch management of the Grade Scheme is still an API-only task as far as I'm aware though. ... View more

I just want an API as soon as possible... REST, GraphQL, whatever. The sooner we have the ability to automate the better. 😁 ... View more

That's annoying; most APIs I have used indicate when they are paginated, with a result count or page number attribute or similar. But thank you very much @melodyc_lam, I'd still be beating my head against a wall if it weren't for you. 😁 ... View more

I hadn't known about or noticed that parameter, so thank you very much! It certainly resolves the issue of having to query the parent. However... [ {"id":1,"role":"AccountAdmin",[...] {"id":3,"role":"StudentEnrollment",[...] {"id":4,"role":"TeacherEnrollment",[...] {"id":5,"role":"TaEnrollment",[...] {"id":6,"role":"DesignerEnrollment",[...] {"id":7,"role":"ObserverEnrollment",[...] {"id":11,"role":"Help Desk",[...] {"id":12,"role":"Herzing Staff",[...] {"id":14,"role":"Quizzes.Next Service",[...] {"id":15,"role":"LTI Account",[...] ] This does not resolve the issue that I am presented with options in the UI for this subaccount that do not show up via the REST API. ... View more

I posted a suggestion to sort the data tables before export to Ideas. Unlike differential imports (which is also valuable), sorting the data before splitting into million-row chunks would require very little effort, for a moderate increase in the ease-of-use of the data portal. ... View more