There are a few errors you might encounter when attempting to deliver Back-To-School Registrations.

NOTE: If you are trying to deliver a record and are getting stuck on some errors, give the SIS team a call!

Below is a list of common errors and how you can fix them so that you can deliver data.

Identifying Errors:

If you have an error when delivering, you will see messages such as these:

To fix them, you will have to scroll down until you find the error. The errors are typically contact-specific, meaning that the individual contact causing the error will be identified:

Error: INVALID_CONTACT_DATA: psx.html.contacts.validation.original_contact_type_already_assigned for originalContactType

The problem: In "Contacts Management" in PowerSchool, this particular contact has a "CALPADS Contact Type" which is duplicated between it and another contact. It could be duplicates of the same contact, or two different individuals.

Error: NO ERROR MESSAGE

The problem: Sometimes, you will get an error message, but no other information on the record.

This is similar to the last error message about "originalContactType", but is caused by more than 1 instance of contacts having duplicate "CALPADS Contact Type".

For example, you can't have four individuals different people (or duplicates of the same person) both with "Guardian" AND "Father" CALPADS Contact Types. So if you have 4 Contacts in "Contacts Management" and two of them have "Father" as the CALPADS Contact Type, and two of them have "Guardian", the system doesn't know which one to call out. So it gives an error with no message.

The solution: Find the duplicates, and do one of the following:

1. If they are the same person, remove one of them from the student record.
   1. This is also a clue that you should go through the contacts consolidation process to combine these contacts.
2. If they are two different people, remove the "duplicate" original contact type from one of them.

Once there are no longer and duplicate "CALPADS Contact Types" you can deliver the record.

Error: INVALID_CONTACT_DATA..... same_phone_numbers_cannot_have_the_same_type...

Example:

The problem: I'm not entirely sure. Sometimes there's an issue with phone numbers on particular contacts. Luckily, the fix is quick!

The Fix:

Find the contact in question on the student's "Contact Management" page and click on that contact. Scroll down and delete ALL phone numbers off that contact.

Once you deliver this record into PowerSchool, it will bring in the new phone numbers for that individual anyways, so you aren't really deleting anything isn't about to come back anyways.

Error: INVALID_CONTACT_DATA..... two_phone_numbers_cannot_have_the_same_sequence...

Example: 

The Problem:

Each contact (and contact phone number) has a "sequence" number. This number dictates what order they show up in. For contacts themselves, it's the order they show up in on the "Contact Management" page. For phone numbers, it's the order that the phone numbers are in for a given contact.

The Fix:

This one is tricky, and pretty rare. What I've found is that you can change the "Sequence" for phone numbers around. If there are three phone numbers listed with "1", "2", and "3", as their sequence numbers, try changing them to "2", "3", "4" to try and resolve conflicts.

Error: Unable to deliver. More than one schema is matched to the same record.

Example: 

The Problem:

You can only map a contact to a student once. So if you've got "John Smith, Father" mapped twice to the same contact in the PowerSchool SIS, you have to get rid of one.

NOTE: Take a second look at these when they come up. I've encountered "John Smith Sr." and "John Smith Jr." - they can look very similar when delivering, but make sure you're matching things up appropriately (or removing duplicates as shown below).

The Fix:

To fix this error, first you will want to specify "no match" on the duplicate contact:

Step 1: Click on "Match"

Step 2: Select "No Match" at the bottom of the page.

Step 3: Clear out all the data from the left-hand column for this contact. Then try and deliver the record.