Imported File Batch Details
There is a detail tab next to each batch which will take you to the batch detail screen. Click on the eye icon to the right. The batch detail screen allows you to view all data that was included in the original upload. It allows you to view the full student detail including all errors. Click on the eye next to the failed import It will open a window displaying the batch details in the manner reflected below.
Pending shows the records that have been successfully uploaded but has not yet been processed by Campus Ivy
Submitted shows the records that have been successfully uploaded and processed by Campus Ivy.
Warning shows the records that have successfully uploaded but has a conflict that you should be aware of; the record will be processed but may cause a significant change to a student's record.
Errors shows the records that have a significant issue and cannot be uploaded to the Campus Ivy CORE system; there will be a detail note on each error.
File Upload Screen: Detail Explanation
Where should Errors be fixed?
Some imports come directly from an integration such as an API integration with Nexus or an FTP connection such as Orbund. This simply mean that the data will flow into CORE without being initiated by a person. Other imports are and can be done manually that means that you may need to generate an export or create an import from an excel template.
What’s the difference you may ask? The difference is where the corrects are made. If your institution has an integration with no manual initiation, then when errors are identified the changes need to made in the student record of the SIS or by the SIS. Changed made in CORE or on the import itself will be override on the next scheduled import causing a round robin of errors.
If the import is being done manual from a spreadsheet, then changes can be updated directly on the spreadsheet and reimported ‘at will’ to clear.
Please note that errors can by as simple as:
removing a space - sp ace to space
adding or removing a letter to match the configuration, i.e. Enrollment Status from 'Graduated” to “Graduate”
giving Campus Ivy a call to see what your program is names in our system so that you can have us update the name or change how you are placing it on the spreadsheet.
Or it can be as complex as:
SIS sending over wrong program code or version
Missing fields like SAP Status or DOB
Drilldown on Errors
Errors may be in the wording e.g. Message: “The Proof of Graduation type (“HSD”) is not accepted. The correction this cause it making it HS. Sometimes a name change will do the trick or a call to Campus Ivy to see how it is named in the system.