Updating course may change grade policy

[buckett]

We recently changed the settings on a large number of courses and did this by loading the existing settings, changing a value and saving them back, this meant we sent the whole course settings object back. When we did this it resulted in a large number of notifications going out saying that the grade policy on the course had changed (we hadn't changed it).

It appears theres a bug in Canvas that means that if the default value is false when you query the API you get the false value back, if you then set the value to false users will get a notification that the value has changed.

The workaround (until Instructure fix it) is to create a new course object with just the values that you want to update and save that course back through the API instead.

[curtain]

That is super helpful info. Thank you! sf

…

--------------------- Scott Finkeldei curtain@ksu.edu Director of Academic and Student Technology Kansas State University

________________________________ From: Matthew Buckett <notifications@github.com> Sent: Thursday, December 19, 2019 3:24 AM To: kstateome/canvas-api <canvas-api@noreply.github.com> Cc: Subscribed <subscribed@noreply.github.com> Subject: [kstateome/canvas-api] Updating course may change grade policy (#120) We recently changed the settings on a large number of courses and did this by loading the existing settings, changing a value and saving them back, this meant we sent the whole course settings object back. When we did this it resulted in a large number of notifications going out saying that the grade policy on the course had changed (we hadn't changed it). It appears theres a bug in Canvas that means that if the default value is false when you query the API you get the false value back, if you then set the value to false users will get a notification that the value has changed. The workaround (until Instructure fix it) is to create a new course object with just the values that you want to update and save that course back through the API instead. — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub<#120?email_source=notifications&email_token=AAFD5QDQVDH4AHQKB5N4CEDQZM4WTA5CNFSM4J5AUWU2YY3PNVWWK3TUL52HS4DFUVEXG43VMWVGG33NNVSW45C7NFSM4IBSSFZQ>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AAFD5QFLG572NJJRTXEQEMLQZM4WTANCNFSM4J5AUWUQ>.