Person Profile Code Import Type

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.

Here is the new version of this article in the Veracross Community.

Overview

The Veracross Data Importer allows you to apply profile codes to people in batch. This import type is considered an importer but not an updater — it applies profile codes to people but cannot remove them. Profile codes applied through this import type must already exist within Axiom; it does not facilitate the creation of new profile codes. Learn about using and creating profile codes in Axiom by reviewing documentation on the topic.

Uploading Person Profile Code records involves the following two steps:

  1. Preparing the data for upload using the Person Profile Code import type template, which is provided before data import on the Importer site.
  2. 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.

Recommendation: Use the import template provided at import.veracross.com/your_school, rather than creating your own CSV file. This can eliminate many unintentional errors.

Fields in the Import Type Template

This template has an instance of a "either this field or that field are required" scenario. See the notes in the table below for more information.

Column (field) NameNotes
Required fields:
person_id or
person_reference_type and person_reference_value
person_idNumeric format. The person_id can be found in the Person ID field in a standard Find Person query.
person_reference_type

Text/numeric format. 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 type id (numeric format)
  • person reference type description (text/numeric format)

person_reference_valueText/numeric format. This value is the reference value in a Find Person Reference Number query.
profile_codeRequired field. Text/numeric format. Either the profile code ID (numeric) or the profile code description (text). These can be found in a standard Profile Codes query on the System homepage in the Profile Code ID and Description columns, respectively.

Q&A

In addition to the criteria set in the table above, this import type has a number of additional considerations that should be taken into account.

QuestionAnswer
Can I remove profile codes from a person using this import?Sorry, but no. This import type acts as an importer and not an updater — it can insert (add) new records, but cannot modify (remove) existing ones.
Can I create new profile codes through this import type?No — new profile codes and profile code categories must be created in Axiom. Read our documentation to find out more.