Universal
  • Invalid Data:Column Required (import_name)
    • Sometimes the error message intended for identifying a missing Required column will have the name of the import type as the missing column instead of an actual column, and all of the Required columns are already in the file. This generally indicates that there is a column at the end of the other columns with whitespace data entered, causing the validator to think there is an additional column with no header. To fix this, highlight several of the columns past the populated columns and delete the data
  • DATA_SAVE_ERROR: System.Reflection.TargetInvocationException: Exception has been thrown by the target of an invocation. ---> System.Data.SqlClient.SqlException: Execution Timeout Expired.  The timeout period elapsed prior to completion of the operation or the server is not responding. ---> System.ComponentModel.Win32Exception: The wait operation timed out
    • This indicates a timeout error caused by attempting to process too much data at once. The most common cause of this is the length of the import file exceeding 5000 records. This is the automatic cutoff limit, though this message may occasionally be seen with fewer records if there is a significant number of columns in the import
 
Academic Course
  • No Match:GradePlanGroup
    • Grade Plan Groups need to be created prior to being included in a data import, and must be spelled exactly the same as they are in the database
  • No Match:TranscriptCategory
    • Transcript Categories need to be created prior to being included in a data import, and must be spelled exactly the same as they are in the database
  • Invalid data:Column Required
    • This can be caused by a few things:
      • One of the Required fields (columns) is missing
      • One of the Required fields is blank
      • There are empty rows at the end of the import file
  • No Match:ACDepartment
    • There is no department for the level. The missing department needs to be created or an existing department with that name can be shared to the level supplied in the file
  • No Match:GradeLevel
    • The name of the grade supplied in the file doesn’t match an existing grade in the database
  • DATA_SAVE_ERROR: System.Reflection.TargetInvocationException: Exception has been thrown by the target of an invocation. ---> System.Data.SqlClient.SqlException: The level_num of the grade must match the level_num of the offering
    • For one or more records, the grade_level supplied in the file doesn’t belong to the level_description supplied
    • This could also be caused by a course code being used for more than one course. Unique course codes are required to finish the import process. If there are two courses with same code, one of them will need to be changed to make them both unique
  • DATA_READ_ERROR: duplicate column header names - unable to process
    • There are two or more columns in the data import file with the same name. One will need to be edited to be unique, or removed if it’s a duplicate
  • DATA_SAVE_ERROR: System.Reflection.TargetInvocationException: Exception has been thrown by the target of an invocation. ---> System.Data.SqlClient.SqlException: Offerings tied to a level_num organized by grade levels must be tied to a grade level.
    • Each level has an ‘Organized By’ flag (this can be seen by logging into a school without impersonating and going to Core > Settings > School & Grade Levels and editing into a school level)
      • If the Level is Organized By Grades, then in the data import file, at least one grade_level column must be included and grade_level columns should come before any columns for department_name.
      • If the Level is Organized By Departments, then in the data import file, at least one department_name column must be included and the department_name columns should come before any columns for grade_level.
    • If a school has multiple level, and each is organized by different values, then the data import file for courses needs to be split into two files, one for each Organized By type
  • DATA_SAVE_ERROR: System.Reflection.TargetInvocationException: Exception has been thrown by the target of an invocation. ---> System.Data.SqlClient.SqlException: The INSERT statement conflicted with the CHECK constraint "CK_ac_offering_num_section_min"
    • The Section Minimums must be less than or equal to both the Section Target and Section Maximum numbers.
  • DATA_SAVE_ERROR: System.Reflection.TargetInvocationException: Exception has been thrown by the target of an invocation. ---> System.Data.SqlClient.SqlException: The MERGE statement conflicted with the FOREIGN KEY constraint "FK_ac_offering_faculty__faculty_user_id". The conflict occurred in database "ds172_school"
    • There is a User (or Users) in the CSV file that has a duplicate account. The accounts would need to be merged or the User(s) needs to be excluded from the Import
 
Academic Section
  • No match:AC_offer
    • Either the course is in the file but not in the database, or the course name in the file is different from the course name in the system
      • Note: If the course code is included in the import, a scheme that doesn’t include course title can be used to simplify
  • No Match:Faculty
    • Either the faculty member is in the file but not in the database, or the faculty name in the file is different from the name in the system
      • Note: If Host ID is included in the file, firstname and lastname can be omitted
  • This_duration error
    • ‘This_duration’ refers to the starting term of the section, so only the starting term needs to be included. Additional terms being listed will throw an error
    • The term name must also be an exact match on the term name in Core > Settings > School Information > Years & Terms
 
 
  • Cannot verify section uniqueness
    • This indicates another section with the same course name and section identifier are included in the file. Section identifiers need to be unique to the entire school year, even if they’re in different terms
  • Validation Error: Not enough terms remaining
    • This indicates the course is a multi-term course, but the starting term doesn’t leave enough following terms for the course to complete
  • No Match:FacultyHostId(host_id);No Match:Faculty(firstname,middlename,lastname,nickname,suffix);
    • This indicates that there are no Faculty users with a Host ID that matches what’s supplied in the file. The Host ID value will need to be updated to the Host ID of the correct teacher
  • Invalid data: duration or offering empty
    • This indicates that a required field is missing for the record, in this case either duration or offering
 
Academic Enrollment
  • Conversion from string ‘1000 – 1’ to type ‘Integer’ is not valid
    • This indicates that the record in question has a value in a field (likely an ID field) that should be a number, but includes non-numeric characters as well
 
Emergency Contact
NOTE: This import creates the Emergency Contact connection between existing users with their existing data. It will not create new users, create relationships, or update user info.
  • No Match:Student(firstname,middlename,lastname,nickname,suffix,grad_year)
    • The information supplied in the file doesn’t match to a student in the database. Common potential issues include a nickname being entered as the firstname, the suffix being included as part of their lastname when it’s not in their profile (or vice versa), or the grad_year doesn’t match the value in the database
  • No Match:Relationship(user_2_user_id,user_id)
    • The second user (contact_firstname, contact_lastname) does not have a relationship to the first user as defined in the file (contact_relationship). For example, a relationship type of ‘Grandfather’ may be supplied in the file, but the expected value would be the gender-neutral ‘Grandparent’
  • No Match:UserTwoPhoneIndex(phone_number,user_2_user_id,phone_type_id)
    • The data supplied for the second user (contact_firstname,contact_lastname) doesn’t have a phone number of the type specified. Potential issues include:
      • The phone type is misspelled (ex. Supplied as ‘cellphone’ when it should be ‘wireless’
      • The phone number is mistyped (ex. The file formatted as (###) ###-#### when it’s ###-###-#### in the system)
      • The user doesn’t have a phone number for this type (ex. They have a number supplied as ‘wireless’ but only have a Home phone/no phone numbers.
 
  • Multiple Matches:UserTwoDetail(contact_firstname, contact_lastname, contact_middlename, contact_nickname, contact_suffix, contact_grad_year)
    • The supplied information for the second user matches on multiple users in the database (ex. A father and son have the same name in the system and only name information is supplied for matching. A way around this would be to make sure the suffix is filled out and included in the file, but this will also mean anybody in the file with a suffix will need to have it included
  • […] Violation of the PRIMARY KEY contstraint ‘PK_ec_user_phone’. Cannot insert duplicate key in object ‘dbo.ec_user_phone’ […]
    • This may appear at the bottom of a validation file where every line is listed as ‘Passed’. It indicates that a user’s information is being added as an emergency contact for a user twice. The duplicate entries will need to be removed, then the file should process
 
Role Membership
  • No Match:role_description
    • Either the name of the role_description value is misspelled, it doesn’t exist, or it’s a role that can’t be assigned through an import (such as employment roles, relationship roles, content editor roles, etc.)
 
Athletic Opponent
  • Invalid Data:Column Required(opponent_name)
    • One of the required fields (in this case, opponent_name) isn’t populated
  • State is too long; cannot set column ‘state’. The value violates the MaxLength limit of this column
    • The long state name (ex. New Hampshire) was supplied in the data file. Only two-character state abbreviations are acceptable (ex. NH)
  • Phone_number_1 is too long; cannot set column ‘phone_number_1’. The value violates the MaxLength limit of this column
    • The maximum number of characters for a phone number is 30. The value supplied is over 30 characters
 
Athletic Location
  • No Match:Opponent(opponent_name)
    • The value supplied for opponent_name doesn’t match an existing opponent in the database. Either the name is misspelled of the opponent hasn’t been created yet
  • Invalid Data:Column Required(location_name);Column ‘location_name’ does not allow nulls
    • One the Required fields (in this case, location_name) is not populated. Can also be caused by blank rows in the file
  • Input string was not in a correct format.Couldn’t store <> in travel_time Column. Expected type is Int32
    • The field travel_time expects integer values. If additional information (ex. The text ‘minutes’) is included in the field, this error will occur
 
Athletic Roster
  • No Match:Student
    • Generally occurs when one of these fields doesn’t match what’s in the database:
      • Firstname (misspelled or a nickname supplied)
      • Lastname (misspelling, swapped data for first and last, suffix included/missing when it shouldn’t, or characters such as hyphens being omitted)
      • Grad_Year (either the wrong value or the student doesn’t have an enrollment record for the supplied school year)
      • User doesn’t have the Student role
  • No Match:Section
    • Team hasn’t been offered for the school year/this_duration (season) identified in the file
  • Multiple Matches:AC_Offer
    • Either the Team has been offered twice in the same school year or there are two Teams with the same name (ex. One is Active and the other is Inactive, rename the Inactive team to make them both unique)
  • DATA_SAVE_ERROR: System.Reflection.TargetInvocationException: Exception has been thrown by the target of an invocation. ---> System.Data.SqlClient.SqlException: Violation of PRIMARY KEY constraint 'PK_ac_enrollment'. Cannot insert duplicate key in object 'dbo.ac_enrollment'. The duplicate key value is (1830032, 3174756).
    • This indicates that one (or more) records in the data are listed twice, or the student for the team listed is already on the roster. To identify the user, use the second number in the pair as the end of the error (ex. The value 3174756 above refers to the User ID of the issue user)
 
Athletic Schedule
  • No Match:AC_Offer
    • The name supplied for course_title is either misspelled or doesn’t exist in the database. If the team does exist and is spelled correctly, then the team either hasn’t been set up or hasn’t been offered for the school year/this_duration (season) identified in the file
  • No Match:Duration
    • The value supplied for this_duration can’t be found for the supplied school year/level in the file. Either it doesn’t exist or it is misspelled. (ex. Athletics may have a Fall term where Season Name = Fall and Description = Season, but in the file the value for ‘this_duration’ is listed as Fall Season. What should be supplied is just the season name (Fall))
  • No Match:Section
    • The import will attempt to find the team based on the supplied school year/level/duration. If there are any errors related to these three items, this message will always appear. Addressing the issues with level, school year, and duration will usually resolve this error, though there are cases where the team also still needs to be offered for the school year identified
  • No Match:Location
    • Either the location name is misspelled or doesn’t exist in the system
  • No Match:Opponent
    • Either the opponent name is misspelled or doesn’t exist in the system
  • Multiple Match:Opponent
    • This indicates there are two or more opponents with the same name in the database, so the import doesn’t know which one to select. The duplicate either needs to be removed or modified to make them unique.
  • Multiple Match:Location
    • This indicates there are two or more locations with the same name in the database, so the import doesn’t know which one to select. The duplicate either needs to be removed or modified to make them unique.
 
Distribution Group
  • Invalid Data:duplicate user in distribution group
    • This means that either the user is already a member of the distribution group, or they are in the import file twice. This could also be triggered by a duplicate Host ID in the file, as even if they have different names, the duplicate Host IDs will be treated as a duplicate record
  • Invalid Data:Column Required (firstname)
    • One of the required fields in the import file isn’t populated with data (in this case, firstname)
  • Multiple Matches:UserHostID
    • Two or more users in the database have the same Host ID. Host IDs should be unique and not shared
  • No Match:DistributionGroup
    • Either the distribution_group listed that is being inserted into wasn’t created before the import, or the name in the file is misspelled
 
Events
  • DATA_SAVE_ERROR: System.Reflection.TargetInvocationException: Exception has been thrown by the target of an invocation. ---> System.Data.SqlClient.SqlException: The conversion of a datetimeoffset data type to a datetime data type resulted in an out-of-range value.
    • This indicates that either the dates entered are in the past, or the start and end date or times on the same date are reversed to create a reverse run time
User Management Imports (address, email, etc.)
  • No Match:User
    • This indicates there file didn’t match to a user in the system, which could potentially be caused by a misspelled name or non-existent User ID