Understanding how data is managed and groomed in Veracross is fundamental to database management. Learn the methods used in Veracross here.
Articles
Axiom Record Overview
In order to track many discrete pieces of information within the system, Veracross organizes information into unique records.
Detail Screen Overview
Managing records within Veracross is one of the most fundamental Axiom tasks. This article will explain how to use Axiom for record management, such as adding, deleting, and updating records.
Adding Files to People in Batch
You can upload files in batch — using .zip files — to person, household, and organization records in Axiom. This article covers the step-by-step instructions.
Attaching Links to Person Records
Here is the new version of this article in the Veracross Community. Overview In addition to storing files on person records, Veracross is also able to store links on Candidate, Student, Staff, and Faculty person detail screens. This featur...
Deleting Person Information (GDPR-Related)
Here is the new version of this article in the Veracross Community. Overview From both a philosophical and technical standpoint, Veracross encourages schools to keep data. The only person records that should be actually deleted are those w...
Deduping Categories
Here is the new version of this article in the Veracross Community. Overview The deduping category (or “dupe group category”) value that the system assigns to any potential duplicate households, people or organizations is helpf...
Duplicate Record Management
Here is the new version of this article in the Veracross Community. Overview When two or more records exist for the same person, household, or organization, the records should be merged so that each person/household/organization is represe...
Managing Related Records in Axiom
Here is the new version of this article in the Veracross Community. Overview Records can be linked to other records within the system. For example, users can indicate relationships by linking person records on the Related People tab of a p...
Merge Duplicate Records
Here is the new version of this article in the Veracross Community. Please take great care when you are merging data : double-check the records, as they cannot be “un-merged” by Veracross. Contact your account manager if you be...
Person ID Field
Here is the new version of this article in the Veracross Community. Overview In Veracross, each person is automatically assigned a person ID when their record is created. That unique identifying number remains theirs forever. It is not ch...
Record Action Menus
Each record in the system is associated with a set of Action items, accessed via the icon in the Launchpad.
Transaction (Audit) Log
Veracross tracks user and system made changes to data including changes to people, households, organizations, applications, as well as all academic information (grades, enrollments, etc.). This can be helpful to track down when changes were made to data, what the changes were, and by whom they were made.
Going Remote with Veracross: A UNIS Hanoi Case Study
Here is the new version of this article in the Veracross Community. Overview Schools across the globe are moving to online learning while teachers and administrators work furiously to facilitate the transition. While this is new to many s...
When I’m merging records, should I merge the Household or Person records first?
Duplicate records can occur for a variety of reasons in Veracross; that's why we recommend you regularly engage in grooming your school's data to mintain data integrity.
Why is this data integrity check still appearing, even after I cleared it?
If you believe that you've corrected an item that was appearing on one of your data integrity checks but it is still appearing, follow these steps:
How do I merge adult and child records?
When going through the data grooming process, occasionally, you will try to merge two records unsuccessfully because one is an "Adult" record and one is a "Child" record. If you are sure that these records should be merged, perform the following steps to merge these records:
How can I see a history of changes on a record?
The Audit Log is a helpful tool used to track changes and updates on an individual record. Throughlooking at the audit log, you can see what was changed, the date it was changed, and the user who made the change.
Why are some integrity checks not being identified during the nightly scripts?
By default only integrity checks with a Severity level of "Critical" are run in the nighty scripts. All other levels of integrity checks are not run but can be enabled by request. All other levels of integrity checks are only update...
Are the end dates on Department classification types managed manually or does the system update them automatically?
Department classification types are automatically populated with an end date (and the active flag turned off) whenever the type no longer applies to a person. This check happens during the nightly refresh of person classifications, so these en...
If I don't merge records on the duplicate record queries, will they remain there forever?
If no merging duplicate record action has been taken on a Person or Household record within 45 days of being flagged, the system will automatically unflag the record as a duplicate. Organizations will be unflagged after 90 days. There is paramete...
What is the best way to deal with organization duplicates that aren't actually duplicates?
Sometimes, multiple organizations exist in your database that may seem like duplicates, but actually aren't. This situation is most common with organizations that do have the same name but multiple office locations with different addresses ...
What does the "Inter-Household Donation Soft Credit without Soft Credit Type" integrity check indicate?
This integrity check will display records when the donation has a Household soft credit for a member who is not part of the same household as the donor. To clear the error: Update the soft credit type to "Other" or remove the soft cred...
What do the numbers and letters signify in the dupe groups listed in the Duplicate Record queries?
The number/letter combinations in the Duplicate Record queries make up specific dupe group categories that the system assigns to any potential duplicate households, people or organizations. The leading numbers (01, 03, etc.) estimate the like...
Where/how can we store Social Security Numbers in Axiom?
Veracross does not support storage of social security numbers (SSNs) in any field for any purpose. Veracross’s number one priority is the security of customer data, as such we need to carefully balance what fields are available in the appli...
How do I remove a record from the Duplicate list once I see that they are truly not a duplicate?
To protect a record from being merged during the deduping process, navigate to the Other tab and set the Surviving Record to be itself. The record is then removed from the dupe group in the overnight process, or by forcing the deduping list to ...
How do I keep the system from automatically creating relationship records between individuals?
We at Veracross understand that there are times when schools need to maintain individual person records but these records should not be linked to any other records (e.g. ex-husband/wife gets linked to individuals related to their former spouse)...
What happens during the nightly scripts?
The nightly scripts are a collection of procedures that help maintain system and data integrity. The nightly scripts include procedures like: Refresh Portal Membership Execute Integrity Checks Generate Attendance Records Refresh Person Classi...
Is the audit log ever deleted?
The Audit Log is useful for tracking changes that have been made to a particular record. In general, Veracross does not delete core audit log information, but there are cases where system level activity log items are removed to remove clutter i...
How do I merge records when encountering the “cannot merge person records, protected by surviving_record_fk matching person_pk” error message?
This error is encountered when the Surviving Record field on the Other tab of one or all of the person records to be merged is populated. This field protects the record from any automatic or manual merges being performed. To merge these record...