Topics Map > Canvas
Topics Map > Known Issues (all tools) > Canvas - Known Issues
Canvas - Known Issue - “N/A” values appearing in the exported gradebook; impedes import of edited gradebook [UW-Madison]
An issue within Canvas has been detected that presents in two different situations.
- Instructors may notice several "N/A" values in the exported gradebook.
- Instructors may notice a subset of students are appearing associated with a quiz in SpeedGrader.
"N/A" values in the gradebook
In the first example, instructors who export the gradebook may notice “N/A” values are appearing in some cells. (see image)
In the Canvas gradebook, those same cells appear simply as ungraded null values.
Further, upon editing the gradebook for the purpose of importing new grades, any cell that contained an “N/A” value does not get successfully imported.
Not all students are available in SpeedGrader
In the second example, when an instructor attempts to view a quiz in SpeedGrader, it appears only a subset of 19 students have received the quiz. (see image) In this example, there are 76 students in the class.
Affects
At present, the only constant thread we notice is that the “N/A” values only appear for assignments that do not have a due date.
Workaround
The fastest workaround for an instructor is to edit each assignment or quiz that is presenting either of these traits, and make a modification to one of the values in the "Assign" options. Specifically, success has been achieved by:
- adding a due date to the assignment or quiz, and
- altering the "Assign To" field, saving the change, then returning the field back to its original value.
If there are more than a few assignments that need to be fixed and you'd like help fixing them, please contact the DoIT Help Desk to collect information and escalate to the Learn@UW Team.
Also, courses can be identified and passed along to Instructure Support. They will run the course through an internal process to resolve the issue.
Status
-
This issue was recognized in UW-Madison’s instance on Tuesday, February 18.
-
The fix was recognized on Thursday, February 20.
-
This Known Issues document and a solution was socialized on Friday, February 21.
- This Known Issues document was updated and expanded to include a second expression of the problem on Friday, March 3.