Gateway to Prep Import Type

Overview

Gateway to Prep Schools (GTP) is a third-party online application system designed to help admission candidates navigate through the application process. Through this tool, applicants are able to research schools of interest, inform schools of their interest in them, and submit applications to multiple schools.

Using the Data Importer web application (import.veracross.com/<yourschool>), Veracross is able to import data from Gateway to Prep Schools in order to create application records in Veracross.

Uploading Gateway to Prep Schools data involves two steps:

  1. Preparing the data for upload using the Gateway to Prep Schools template (csv file). This template file is accessible from the Data Importer site. Read more about the Veracross Data Importer.
  2. Uploading the data via the Veracross Data Importer app.

Note: This importer type is an extra-cost add-on integration service. If your school is interested, ask your account manager.

Preparing the Data to Upload

Prepare a comma-separated value (CSV) file containing the data for the Veracross field column listed below. This CSV file must contain a column for each Veracross field listed below and they must be in that same order. Even if no content is populated in a columns, the column must still exist as a placeholder in order for the Data Importer to properly read the file. In order to produce CSV for this import type, use the Gateway to Prep Student Profile CSV export. The fields on this export will match the fields required by this import type. Upload the CSV file using the Data Importer.

Gateway to Prep Mapping Reference

Veracross uses Gateway to Prep’s data dictionary to help define field mapping references. This information is then used to make initial mapping references on behalf of the school. Any fields that are ambiguous or unknown are left unmapped so the schools and their Account Manager can discuss the best mapping option for those fields. When Gateway to Prep mapping references has been set up at a school, two new queries will be available on the System homepage under the Veracross Integrations section.

  • Gateway to Prep Mapping
    This query represents the initial mapping Veracross creates based on GTP’s data dictionary. It displays a list of all GTP values and how they map to Veracross table names and descriptions. Work with the Account Manager to verify the mapping.
  • Incomplete Gateway to Prep Mapping
    This query displays a list of all unmapped GTP values. Schools should work with their Account Manager to determine if these fields need to be mapped to a Veracross value (it is possible not all will be necessary to map). Schools should communicate any changes that need to be made to the mapped references. Veracross will then add the appropriate reference to complete the mapping.

Field Mapping

Data is mapped to fields from GTP to Veracross using three import strategies:

Import TypeDescription
Insert OnlyValue will be applied to VC record only upon VC record insert.
Updated per importValue is applied to corresponding VC record replacing any existing value.
Update if blankValue is applied to corresponding VC record if the VC field in question is blank.

In the following tables, information in the “Import Type” column indicates which Veracross field is updated with data from GTP only once at initial upload, updated/replaced per import, or updated only if blank.

Candidate 

Admission Candidate Mapping

Veracross will insert new admission candidate (child) records into the database from GTP, unless it finds an existing person record using the following criteria:

  • An existing Veracross person record exists where the Legacy ID is the GTP ID (this is called Application ID field in the GTP data).
  • The data source is set to either “Gateway to Prep Candidate” or “Third Party: Gateway to Prep ID.”

Alternatively, the data import checks for cases where the first name, last name, and date of birth match data from Gateway to Prep. The matching checks against both normal person records and person records that were previously merged. If no matching person record is found, a new person record is created.

Some fields on the admission candidate record are only populated upon initial record creation; they are not synced from GTP to Veracross after initial record creation. These fields have an import type of “insert only” in the following Admissions Candidate field imports table.

Fields
The following table specifies all fields mapped from GTP to Veracross for admissions candidate records.

GTP FieldVeracross Person FieldImport Type
application_idLegacy IDInsert Only
app_fnFirst NameInsert Only
app_mnMiddle NameInsert Only
app_lnLast NameInsert Only
app_nicknamePreferred NameInsert Only
app_suffixName SuffixInsert Only
cityofbirth + stateofbirth + countryofbirthPlace of BirthInsert Only
app_dob1 / app_dob2 / app_dob3Date of BirthInsert Only
app_sexGenderInsert Only
race_african_amerEthnicityInsert Only
race_africanEthnicityInsert Only
race_asian_amerEthnicityInsert Only
race_asianEthnicityInsert Only
race_hispanicEthnicityInsert Only
race_mexicanEthnicityInsert Only
race_mideasternEthnicityInsert Only
race_native_amerEthnicityInsert Only
race_hawaiianEthnicityInsert Only
race_puertoricanEthnicityInsert Only
race_whiteEthnicityInsert Only
race_otherEthnicityInsert Only
race_noresponseEthnicityInsert Only
app_emailEmail 1Updated if blank
app_phPhone HomeUpdated if blank
app_cellphPhone MobileUpdated if blank
grade_currentCurrent GradeInsert only*
year_applying_forYear Applying ForInsert only*
grade_applying_forGrade Applying ForInsert only*
residential_statusResident Status Applying Forinsert only*

* Note: Information in the fields current grade, year applying for, grade applying for, and resident status applying for is updated during the first data sync (insert only) for Candidate information for the year they are applying for. Schools do have the ability to manually override these imported values and all future data imports will not override these changes. For example: a candidate applies for next year and the data from GTP to Veracross populates the “year applying for” field as next year, but later the school decides to admit this candidate for the current year as a mid-year admit and thus manually updates the “year applying for” field on the Candidate record to the current year. Rerunning the upload will not override the school’s manually changed value to the mid-year date.

Candidate Language

Veracross will insert any new language records, that do not exist, into the database from GTP.  When a new language record is added in Veracross, the “primary code” and the “language spoken at home” field are both set to true.

The field on the candidate language record is only populated upon initial record creation; it is not synced from GTP to Veracross after initial record creation. This field has an import type of “insert only” in the following Candidate Language field imports table.

Fields
The following table specifies all fields mapped from GTP to Veracross for person language records.

GTP FieldVeracross Language FieldImport Type
homelanguageLanguageInsert Only

Candidate Citizenships

Veracross will insert any new citizenship records, that do not exist, into the database from GTP.

Fields
The following table specifies all fields mapped from GTP to Veracross for person citizenship records.

GTP FieldVeracross Citizenship FieldImport Type
citizenshipcountryInsert Only
dualcitizenshiporigincountryInsert Only
uspermresidentcountryInsert Only
othercitizenshipcountryInsert Only
othercitizenship2countryInsert Only

Candidate Role

By default, Veracross adds the “Prospect” role to all candidates from GTP if they do not currently have the prospect, applicant, or future student roles. However, if the “imported as completed” Admission Checklists include ALL Admission Checklists flagged as “Required for Application,” then two things are triggered in the system: a) an Application record is created for the Applicant (inheriting data from the Candidate Admission record above), b) the “Prospect” role becomes “Applicant.”

Candidate Household Mapping

Veracross will insert new household records into the database from GTP unless it finds an existing household record using the following criteria in this order:

  1. If an existing candidate record was found in the above Candidate mapping, and this candidate had a household specified, this existing household will be used for the candidate’s household.
  2. Otherwise, If the candidate did not have a household specified yet, then existing Veracross household data will be reviewed where the Veracross Household Legacy ID matches GTP ID and the data source is “Gateway to Prep Candidate Household.”

The mapping checks against both normal household records and records that were previously merged. If it does not find a match, a new household record is created. All fields on the household record are synced ONLY upon initial record creation. These fields have an import type of “insert only” in the following Candidate Household field imports table.

Fields
The following table specifies all fields mapped from GTP to Veracross for candidate person household records.

GTP FieldVeracross Household FieldImport Type
application_idLegacy IDInsert Only
app_lnHousehold NameInsert Only
app_addressAddress 1Insert Only
app_address2Address 2Insert Only
app_address3Address 3Insert Only
app_cityCityInsert Only
app_stateState/ProvinceInsert Only
app_zip_pcodePostal CodeInsert Only
app_countryCountryInsert Only

Parents

Parent Mapping

Veracross will insert new parent records into the database from GTP unless an existing person record is found using the following criteria:

  • The existing person’s Veracross Legacy ID matches the GTP ID.
  • The data source is set to “Gateway to Prep Parent.”

Alternatively, the relationship between the parent and the candidate is used to match parent records. Veracross will look for a relationship where the parent’s first name and last name matches the GTP parent’s first and last name, and the relationship to the candidate in Veracross is identical to the relationship coming from GTP.

If no matching record is found, a new person record for the parents is created. Note, parents must have a first and last name specified to create a new record. Some fields on the parent records are synced ONLY upon initial record creation. These fields have an import type of “insert only” in the following Parents field import table.

Fields
The following table specifies all fields mapped from GTP to Veracross for parent person records.

GTP FieldVeracross Person FieldImport Type
application_idLegacy IDInsert Only
parent1courtesytitleName PrefixInsert Only
parent1firstFirst NameInsert Only
parent1middleMiddle NameInsert Only
parent1lastLast NameInsert Only
parent1suffixName SuffixInsert Only
parent1occupationJob TitleInsert Only
parent1aliveDate of DeathInsert Only
parent1birthplacePlace of BirthInsert Only
parent1homeemailEmail 1Update if blank
parent1workphonePhone businessUpdate if blank
parent1cellphonePhone MobileUpdate if blank
parent2courtesytitleName PrefixInsert Only
parent2firstFirst NameInsert Only
parent2middleMiddle NameInsert Only
parent2lastLast NameInsert Only
parent2suffixName SuffixInsert Only
parent2occupationJob TitleInsert Only
parent2aliveDate of DeathInsert Only
parent2birthplacePlace of BirthInsert Only
parent2homeemailEmail 1Update if blank
parent2workphonePhone businessUpdate if blank
parent2cellphonePhone MobileUpdate if blank
parent3courtesytitleName PrefixInsert Only
parent3firstFirst NameInsert Only
parent3middleMiddle NameInsert Only
parent3lastLast NameInsert Only
parent3suffixName SuffixInsert Only
parent3occupationJob TitleInsert Only
parent3aliveDate of DeathInsert Only
parent3birthplacePlace of BirthInsert Only
parent3homeemailEmail 1Update if blank
parent3workphonePhone businessUpdate if blank
parent3cellphonePhone MobileUpdate if blank
parent4courtesytitleName PrefixInsert Only
parent4firstFirst NameInsert Only
parent4middleMiddle NameInsert Only
parent4lastLast NameInsert Only
parent4suffixName SuffixInsert Only
parent4occupationJob TitleInsert Only
parent4aliveDate of DeathInsert Only
parent4birthplacePlace of BirthInsert Only
parent4homeemailEmail 1Update if blank
parent4workphonePhone businessUpdate if blank
parent4cellphonePhone MobileUpdate if blank

Parent Household Mapping

GTP stores household address data for parents in two places: Household 1 fields and Household 2 fields. Parents 1 and 2 use data from Household 1 fields, and Parents 3 and 4 use data from Household 2 fields.

Veracross will insert new parent household records into the database from GTP unless an existing parent household record is found using the following criteria:

  • The existing Veracross household Legacy ID matches the GTP ID.
  • The data source is set to “Gateway to Prep Parent Household.”

Alternatively, the related candidate’s household is used for Parents 1 and 2 (Household 1) if the candidate’s household address matches the parent’s address. If the address in Household 1 is blank, it is also set to the candidate’s household address.

If no matching record is found, a new household record is created.

All fields on the household record are synced ONLY upon initial record creation. These fields have an import type of “insert only” in the following Parents Household field import table.

Fields
The following table specifies all fields mapped from GTP to Veracross for parent household records.

GTP FieldVeracross Household FieldImport Type
application_idLegacy IDInsert Only
parent1lastHousehold NameInsert Only
household1address1Address 1Insert Only
household1address2Address 2Insert Only
household1address3Address 3Insert Only
household1cityCityInsert Only
household1stateState/ProvinceInsert Only
household1zipPostal CodeInsert Only
household1countryCountryInsert Only
household1homephonePhoneInsert Only
parent2lastHousehold NameInsert Only
household2address1Address 1Insert Only
household2address2Address 2Insert Only
household2address3Address 3Insert Only
household2cityCityInsert Only
household2stateState/ProvinceInsert Only
household2zipPostal CodeInsert Only
household2countryCountryInsert Only
household2homephonePhoneInsert Only

Parent Employer Mapping

Veracross will insert new organization records for the parent’s employer into the databases from GTP, unless it finds an existing organization record using the following criteria:

  • An existing Veracross organization record exists where the Legacy ID is the GTP ID.
  • The data source is set to either “GTP Parent Employer.”

Alternatively, Veracross will look for existing employer organizations where the employer name in GTP matches the organization name in Veracross and the GTP employer address matches the organization’s “Address Line 1” in Veracross.

If no matching record is found, a new organization record will be inserted with an organization type of “Business.”

All fields on the organization record are synced ONLY upon initial record creation. These fields have an import type of “insert only” in the following Parents Employers organization field import table.

Fields
The following table specifies all fields mapped from GTP to Veracross for parent employer organization records.

GTP FieldVeracross Person FieldImport Type
application_idLegacy IDInsert Only
parent1employerOrganization NameInsert Only
parent1businessaddressAddress 1Insert Only
parent2employerOrganization NameInsert Only
parent2businessaddressAddress 1Insert Only
parent3employerOrganization NameInsert Only
parent3businessaddressAddress 1Insert Only
parent4employerOrganization NameInsert Only
parent4businessaddressAddress 1Insert Only

Parent Employer Relationship Mapping

Once a organization record is either found or created, a parent receives the “employer” relationship with their employer organization.

All fields on the parent employer relationship record are synced ONLY upon initial record creation. These fields have an import type of “insert only” in the following Parents Employer Relationship field import table.

Fields
The following table specifies all fields mapped from GTP to Veracross for parent employer relationship records.

GTP FieldVeracross Person FieldImport Type
parent1businessaddressAddress 1Insert Only
parent1occupationTitleInsert Only
parent1workphonePhoneInsert Only
parent2businessaddressAddress 1Insert Only
parent2occupationTitleInsert Only
parent2workphonePhoneInsert Only
parent3businessaddressAddress 1Insert Only
parent3occupationTitleInsert Only
parent3workphonePhoneInsert Only
parent4businessaddressAddress 1Insert Only
parent4occupationTitleInsert Only
parent4workphonePhoneInsert Only

Candidate/Parent Relationship Mapping

Veracross will insert new candidate parent relationship records if the relationship does not exist.

Note on Import Type “Updated per import”
If the records do exist, but the relationship in Veracross is either “non-specified,” “unspecified relative,” or “other” Veracross will update the candidate parent relationship and legal custody on the Veracross relationship record from the GTP data. 

If the candidate parent relationship in Veracross already matches the relationship from GTP, no updates will be made.

Fields
The following table specifies all fields mapped from GTP to Veracross for candidate/parent relationship records.

GTP FieldVeracross Person Relationships FieldImport Type
parent1typeRelationshipUpdated per import (see note)
legal1Legal CustodyUpdated per import (see note)
parent2typeRelationshipUpdated per import (see note)
legal2Legal CustodyUpdated per import (see note)
parent3typeRelationshipUpdated per import (see note)
legal3Legal CustodyUpdated per import (see note)
parent4typeRelationshipUpdated per import (see note)
legal4Legal CustodyUpdated per import (see note)

Siblings

Candidate Sibling Mapping

Veracross will insert new person records for the candidate’s sibling into the database from GTP unless an existing person record is found using the following criteria:

  • The existing person’s Veracross Legacy ID matches the GTP ID.
  • The data source is set to “GTP Sibling.”

The mapping checks against both normal person records and records that were previously merged.

Alternatively, the relationship between the sibling and the candidate is used to match sibling records. The sibling’s first name and last name and their gender must match the GTP sibling’s first and last name, and gender and the relationship to the candidate in Veracross is one of the following: “brother, sister, step brother, step-sister, half brother, half sister, brother-in-law, and sister-in-law.

If it does not find a match, a new person record is created. All fields on the person record are synced ONLY upon initial record creation. These fields have an import type of “insert only” in the following Candidate Sibling field import table.

Fields
The following table specifies all fields mapped from GTP to Veracross for candidate sibling person records.

GTP FieldVeracross Person FieldImport Type
application_idLegacy IDInsert Only
siblingnamefirst_0First NameInsert Only
siblingnamemiddle_0Middle NameInsert Only
siblingnamelast_0Last NameInsert Only
siblingsex_0GenderInsert Only
siblingnamefirst_1First NameInsert Only
siblingnamemiddle_1Middle NameInsert Only
siblingnamelast_1Last NameInsert Only
siblingsex_1GenderInsert Only
siblingnamefirst_2First NameInsert Only
siblingnamemiddle_2Middle NameInsert Only
siblingnamelast_2Last NameInsert Only
siblingsex_2GenderInsert Only
siblingnamefirst_3First NameInsert Only
siblingnamemiddle_3Middle NameInsert Only
siblingnamelast_3Last NameInsert Only
siblingsex_3GenderInsert Only

Candidate/Sibling Relationship Mapping

Veracross will insert new candidate sibling relationship records if the relationship does not exist. All sibling relationships get a brother/sister relationship to the candidate depending on the sibling’s gender. If the sibling has no gender, they get an “unspecified relative” relationship.

If the records do exist, but the relationship in Veracross is either “non-specified,” “unspecified relative,” or “other” Veracross will update the candidate/sibling relationship to brother or sister depending on the sibling’s gender.  

Current School 

Candidate Current School Mapping

Veracross will insert new school organization records for the candidate’s current school into the databases from GTP, unless it finds an existing school organization record using the following criteria:

  • An existing Veracross organization record exists where the Legacy ID is the GTP ID.
  • The data source is set to either “GTP Current School.”

Alternatively, Veracross will look for existing school organizations where the school name in GTP matches the organization name in Veracross and the GTP school address matches the organization’s “Address Line 1” and city in Veracross.

If no matching record is found, a new organization record will be inserted. All fields on the organization record are synced ONLY upon initial record creation. These fields have an import type of “insert only” in the following Candidate Current School field import table.

Fields
The following table specifies all fields mapped from GTP to Veracross for candidate current school organization records.

GTP FieldVeracross Organization FieldImport Type
application_idLegacy IDInsert Only
school_nameOrganization NameInsert Only
school_typeIndustryInsert Only
school_address1Address 1Insert Only
school_address2Address 2Insert Only
school_address3Address 3Insert Only
school_cityCityInsert Only
school_stateState/ProvinceInsert Only
school_zipcodePostal CodeInsert Only
school_countryCountryInsert Only

Candidate Current School Relationship Mapping

Once an organization record is either found or created, a candidate receives the “current school” relationship with their current school. 

Fields
The following table specifies all fields mapped from GTP to Veracross for candidate current school relationship records.

GTP FieldVeracross Organization Relationship FieldImport Type
school_yearsattendedNotesInsert Only

Other Admission Record Mapping

Candidate Admission Mapping

Veracross inserts the following fields from GTP onto the Person Admission record in Veracross:

GTP FieldVeracross Person FieldImport Type
year_applying_forYear Applying ForInsert Only
year_applying_forMonth Applying ForInsert Only
grade_applying_forGrade Applying ForInsert Only
residential_statusResident Status Applying ForInsert Only

Candidate Test Scores Mapping

New test scores records are created from GTP to Veracross. Included test types are: ACT, ISEE, PSAT, SAT, SSAT, and TOEFL. In order for the test score data for each of these test types to be imported, the standardized test type record in Veracross must be enabled. Learn more about test type configuration in Veracross

All fields on the candidate test scores record are only populated upon initial record creation; they are not synced from GTP to Veracross after initial record creation. These fields have an import type of “insert only” in the following Candidate Test Scores field imports table.

Fields
The following table specifies all fields mapped from GTP to Veracross for person test scores records.

GTP FieldVeracross Standardized Test FieldImport Type
test_actTest TypeInsert Only
test_act_datem / 1 / test_act_dateyTest DateInsert Only
test_iseeTest TypeInsert Only
test_isee_datem / 1 / test_isee_dateyTest DateInsert Only
test_psatTest TypeInsert Only
test_psat_datem / 1 / test_psat_dateyTest DateInsert Only
test_satTest TypeInsert Only
test_sat_datem / 1 / test_sat_dateyTest DateInsert Only
test_ssatTest TypeInsert Only
test_ssat_datem / 1 / test_ssat_dateyTest DateInsert Only
test_toeflTest TypeInsert Only
test_toefl_datem / 1 / test_toefl_dateyTest DateInsert Only

Candidate Interests Mapping

Most GTP interest data maps to the interests notes field on the person interest record. Each unique field is labeled in the interest notes field according to the field in GTP (for example: hpw field maps to the interests notes field and is labeled as “hours per week” in Veracross).

Any new interests that do not exist in Veracross for this candidate will be inserted.

All fields on the candidate interest record are only populated upon initial record creation; they are not synced from GTP to Veracross after initial record creation. These fields have an import type of “insert only” in the following Candidate Interests field imports table.

Fields
The following table specifies all fields mapped from GTP to Veracross for person interest records.

GTP FieldVeracross Person Interest FieldImport Type
application_idLegacy IDInsert Only
activity_0InterestInsert Only
activityyears_0Years ExperienceInsert Only
activityinvolvement_0NotesInsert Only
activityother_0NotesInsert Only
hpw_0NotesInsert Only
participate_0NotesInsert Only
position_0NotesInsert Only
activity_1InterestInsert Only
activityyears_1Years ExperienceInsert Only
activityinvolvement_1NotesInsert Only
activityother_1NotesInsert Only
hpw_1NotesInsert Only
participate_1NotesInsert Only
position_1NotesInsert Only
activity_2InterestInsert Only
activityyears_2Years ExperienceInsert Only
activityinvolvement_2NotesInsert Only
activityother_2NotesInsert Only
hpw_2NotesInsert Only
participate_2NotesInsert Only
position_2NotesInsert Only
activity_3InterestInsert Only
activityyears_3Years ExperienceInsert Only
activityinvolvement_3NotesInsert Only
activityother_3NotesInsert Only
hpw_3NotesInsert Only
participate_3NotesInsert Only
position_3NotesInsert Only
activity_4InterestInsert Only
activityyears_4Years ExperienceInsert Only
activityinvolvement_4NotesInsert Only
activityother_4NotesInsert Only
hpw_4NotesInsert Only
participate_4NotesInsert Only
position_4NotesInsert Only
activity_5InterestInsert Only
activityyears_5Years ExperienceInsert Only
activityinvolvement_5NotesInsert Only
activityother_5NotesInsert Only
hpw_5NotesInsert Only
participate_5NotesInsert Only
position_5NotesInsert Only
activity_6InterestInsert Only
activityyears_6Years ExperienceInsert Only
activityinvolvement_6NotesInsert Only
activityother_6NotesInsert Only
hpw_6NotesInsert Only
participate_6NotesInsert Only
position_6NotesInsert Only
activity_7InterestInsert Only
activityyears_7Years ExperienceInsert Only
activityinvolvement_7NotesInsert Only
activityother_7NotesInsert Only
hpw_7NotesInsert Only
participate_7NotesInsert Only
position_7NotesInsert Only
activity_8InterestInsert Only
activityyears_8Years ExperienceInsert Only
activityinvolvement_8NotesInsert Only
activityother_8NotesInsert Only
hpw_8NotesInsert Only
participate_8NotesInsert Only
position_8NotesInsert Only

Candidate Application Received Record Mapping

Data import will create an individual event record with the event type “application received” if it does not already exist in Veracross.

Fields
The following table specifies all fields mapped from GTP to Veracross for the individual event records.

GTP FieldVeracross Person FieldImport Type
year_applying_forInquiry School YearInsert Only
grade_applying_forGrade LevelInsert Only
submission_dateEvent DateUpdated per import

Candidate Admission Checklist

When inserting candidate records, Veracross creates a set of Admission Checklist Items that apply to them. During the Gateway to Prep import, the system will mark as complete any checklist item specified as a Gateway To Prep checklist item (via the Gateway to Prep Mapping (see above)), setting the Completed Date to the GTP submission date.

Fields
The following table specifies all fields mapped from GTP to Veracross for the person admission checklist item records.

GTP FieldVeracross Admission Checklist FieldImport Type
submission_dateCompleted DateUpdated per Import


Important Note
The Gateway to Prep import does not import the individual GTP checklist items (and associated uploaded files). Instead, the Veracross GTP Import generates a link to the Gateway to Prep Student Profile is generated (based on application_id) for each imported Candidate. This link is accessible on the Candidate Detail > Links tab. The link is also included on Candidate Profile Document (under Web Forms, Files, & References).


Candidate Financial Aid

Veracross will update the “requesting financial aid” field for a candidate if it is specified in GTP. This update only occurs if the requesting financial aid data was previously not specified in Veracross.

Fields
The following table specifies all fields mapped from GTP to Veracross for the person financial aid records.

GTP FieldVeracross Financial Aid FieldImport Type
financialaidRequesting Financial AidUpdated if blank*

* Note: the data import will only update this information if what exists in Veracross is “False,” i.e., not requesting Financial Aid, and what exists in GTP is “True,” i.e., the candidate isrequesting Financial Aid.

Data Sync Log

Veracross will insert a record to the Admission History Log table every time the sync is run for an admissions candidate. This record will have an event type of “Gateway to Prep Sync,” and the system will store the raw information received from the Gateway to Prep import on the log record in the Formatted Data field.

Fields Not Imported

  • alienregnum
  • app_sex_identify
  • candidatedate
  • candidatesignature
  • candidatewaiver
  • citizenshipformscountry
  • citizenshipformsrequired
  • esignature
  • house1address1
  • house1address2
  • house1address3
  • house1city
  • house1country
  • house1homephone
  • house1state
  • house1zip
  • house2address1
  • house2address2
  • house2address3
  • house2city
  • house2country
  • house2homephone
  • house2state
  • house2zip
  • legacyname_0
  • legacyname_1
  • legacyname_2
  • legacyname_3
  • legacyrelationship_0
  • legacyrelationship_1
  • legacyrelationship_2
  • legacyrelationship_3
  • legacyrelationshipother_0
  • legacyrelationshipother_1
  • legacyrelationshipother_2
  • legacyrelationshipother_3
  • legacyschool_0
  • legacyschool_1
  • legacyschool_2
  • legacyschool_3
  • legacyyear_0
  • legacyyear_1
  • legacyyear_2
  • legacyyear_3
  • linkinfo
  • linkinfo_1
  • multimed_category
  • multimed_category_1
  • multimed_link
  • multimed_link_1
  • na_box_b
  • na_box_d
  • na_box_h
  • oschool_date1_0
  • oschool_date1_1
  • oschool_date1_2
  • oschool_date2_0
  • oschool_date2_1
  • oschool_date2_2
  • oschool_location_0
  • oschool_location_1
  • oschool_location_2
  • oschool_name_0
  • oschool_name_1
  • oschool_name_2
  • parent1college
  • parent1degreereceived
  • parent1fax
  • parent1graddegreereceived
  • parent1gradschool
  • parent1secondaryschool
  • parent1waiver
  • parent1waiverdate
  • parent1waiversignature
  • parent2college
  • parent2degreereceived
  • parent2fax
  • parent2graddegreereceived
  • parent2gradschool
  • parent2secondaryschool
  • parent2waiver
  • parent2waiverdate
  • parent2waiversignature
  • parent3college
  • parent3degreereceived
  • parent3fax
  • parent3graddegreereceived
  • parent3gradschool
  • parent3secondaryschool
  • parent4college
  • parent4degreereceived
  • parent4fax
  • parent4graddegreereceived
  • parent4gradschool
  • parent4secondaryschool
  • parentmaritalstatus
  • printpreviewed
  • race_african_amer_other
  • race_african_other
  • race_asian_amer_other
  • race_asian_other
  • race_hawaiian_other
  • race_hispanic_other
  • race_mexican_other
  • race_mideastern_other
  • race_other_other
  • race_puertorican_other
  • race_white_other
  • sbage_0
  • sbage_1
  • sbage_2
  • sbage_3
  • school_endsaftergrade
  • siblingcollege_0
  • siblingcollege_1
  • siblingcollege_2
  • siblingcollege_3
  • tribalaffiliation
  • tribalenrolled
  • txtactivities
  • txtinfo
  • uploadaddtlinfo
  • visatype