IN THIS ARTICLE
A Gradient Leader with System Admin or School Support access can view a history of imports with status labels for Completed, Incomplete, and Failed imports as well as import details to review updates, additions, and errors as needed.
Where is the Import Log?
Imports can be viewed from Admin Mode.
- The Imports tab is found in the More tab drop-down menu.
What does the Import log show?
By default, all imports will be listed with options to filter the list by import type and import status.
The import list will display:
Field | Description |
File Name | A selectable field that reveals import details with options to download the file if needed |
School | Reflects the school or district associations of the user/method of import |
Status | Shows Completed, Incomplete, or Failed |
Type |
Shows Full (combined import), Roster (classes only), Students (student only), or Staff (staff only) |
Summary |
Shows a count of additions, updates, and errors with red text to alert you to check the file and import details |
Import Date | Shows the date the import was started |
What are my options for troubleshooting?
The import log can be used to identify when a problem may have occurred and the specific changes to the file that could be the cause. If you need help understanding the import log entries, contact support@gradecam.com or read more about your options below.
Click on any blue File Name to review Import Details.

Common Import Errors:
- Imports may FAIL. This often happens when either TERM or SCHOOL_ID are missing or mismatched. An import will also fail if the column order or column headers differ from the import file template.
- Teachers may notice that class names are hard to differentiate in Gradient and request a class name change. Prior to the 23-24 school year, if CLASS_ID was not originally used in the import file and class names were later "updated" with a file import, the unintended result was that NEW classes were created instead of updating the original names.
- This issue should no longer occur now that a NEW Import File has been created for the 23-24 academic year and beyond.
- Periods may not have been included in the original import file used prior to the 23-24 school year. If PERIOD was later added to an import file, it would create NEW classes (creating duplicates) instead of updating. Periods must be added from the beginning or manually.
- This issue should no longer occur now that a NEW Import File has been created for the 23-24 academic year and beyond.
Comments
0 comments
Article is closed for comments.