As of July 12, 2021, this "Learn Veracross" site has been deprecated. It will remain live through December 2022, but will no longer be updated. All knowledge content has moved to the new Veracross Community. Please update your bookmarks.
Overview
The Veracross Data Importer allows schools to import new behavior incidents for students. This import type is considered an importer — it only allows you to import new behavior incidents and not update existing ones. Though behaviors are often closely associated with comments in the context of Veracross, this import type is for behaviors only. To view the Comment Import Type, please read our documentation on the Comment import type here.
Uploading Behavior incidents involves the following two steps:
- Preparing the data for upload using the Behavior import type template, which is provided before data import on the Importer site.
- Uploading the data using the Veracross Data Importer.
Preparing the Data for Upload
The user must prepare a comma separated value (CSV) file containing all data to import. This file must contain all columns in the order listed below, even if no content is populated in the columns. If there is no content in a column, that row must be left blank.
Fields in the Import Type Template
In addition to a number of required fields, this template has an instance of a "either this field or that field are required" scenario; specifically, regarding person_id, person_reference_type, and person_reference_value. See the notes in the table below for more information.
Outside of the scenario highlighted above, all required fields are designated in the Value Considerations column.
| Column (Field) Name | Value Considerations |
|---|---|
| Required fields: person_id or person_reference_type and person_reference_value | |
| person_id | Numeric format. The person_id can be found in the Person ID field in a standard Find Person query. |
| person_reference_type | Must be an already existing person reference type. This information can be found in a Person Reference Type query. Must be either of the following:
|
person_reference_value | Text/numeric format. This value is the reference value in a Find Person Reference Number query. |
| incident_type | Required field. Text/numeric format. The incident type of the incident as it exists in Veracross. This information can be found in this Behavior Incident Type query. Must be either of the following:
|
| incident_date | Required field. Date format. Date when the incident occurred. Date must be in the 'YYYY-MM-DD' format. |
| incident_notes | Text format. A location to store additional notes about the behavior incident. This field has no character limit. |
| reporting_internal_class_id | Numeric format. The Internal Class ID field of the class where the behavior incident took place. Find this value in this Find Classes query (as the Internal Class ID field). |
| reporting_class_id | Text/Numeric format. This is the class ID for the class where the behavior incident took place. The school year for this value is assumed from the date given in the 'incident_date' column. Find this value in this Find Classes query (as the Class ID field). |
| reporting_person_id | Numeric format. Person ID of an existing person in the database. Find this information in a Find Person query. |
| outcome_type | Text/numeric format. The outcome type of the incident as it exists in Veracross. This information can be found in this Behavior Outcome Types query. Must be either of the following:
|
| outcome_date | Date format. Date when the outcome is defined. Date must be in the 'YYYY-MM-DD' format. |
| outcome_notes | Text format. A location to store additional notes about the outcome of the behavior incidient. This field has no character limit. |
| status | Text format. The status of the behavior incidient if the Category in the Behavior/Comment Statuses query is "Status". This value is the Description field in the Behavior/Comment Statuses query. The wording must be exact, but it is not case sensitive. |
| status_date | Date format. Date when the status on the behavior incident was set. Date must be in the 'YYYY-MM-DD' format. |
| assigned_person_id | Numeric format. Person ID of the person who is assigned to follow up on the behavior incident. This person must already exist in the system. Find this value in a Find Person query. |
| follow_up_status | Text format. The status of the behavior incidient if the Category in the Behavior/Comment Statuses query is "Follow Up Status". This value is the Description field in the Behavior/Comment Statuses query. The wording must be exact, but it is not case sensitive. |
| follow_up_status_date | Date format. Date when the follow-up is due. Date must be in the 'YYYY-MM-DD' format. |
| notification_notes | Text format. A location to store additional notes about the outcome of the follow-up to the behavior incidient. This field has no character limit. |
Additional Considerations
In addition to the criteria set in the table above, the Behavior import type has a number of additional considerations that should be taken into account:
- this import type only inserts new behavior incidents — it does not alter existing behavior incidents
- if a behavior incident is imported from a school year before the current school year, the importer assumes and assigns a grading period of ALL.
- this import type is not for importing comments. For this process, read our documentation on the Comment Import type here.