Unable to update Students via data-upload-utility after v01.060.05.201 update

[BlueGibbs]

Hi,
We're trying to push alt_id to TASS using the data-upload-utility. This was working just fine until the most recent update, after which lots of students were suddenly failing. The API returns a generic HTTP 500 status, but logs show "Error Executing Database Query". We're at the limit of what we can diagnose without knowing what the TASS internals are doing, and TASS software support are refusing to help (CS-271150 in Jira, if you want to check) so we're kinda stuck.

Note it is just the setStudentDataUploadUtility method that is affected. setEmplloyeeDataUploadUtility method works fine.

We've discovered that updating a student's alt_id field via the Data Upload Utility in the TASS web interface fixes whatever the underlying issue is, which seems to point to something wonky in the data model or a database issue. It does give us a work around, but it means that our automated system will still be calling for human assistance on a semi-regular basis.

I'm happy to supply log details or examples directly (I can't supply student information in a public forum) if that will assist in diagnosing the issue, or dig deeper into logs if you can tell me where to look.

[BlueGibbs]

We've now discovered the work-around does not actually work. It appears that the API does not actually attempt to update the student record if the new value matches the existing value. So the API response saying the record has been updated is a tad misleading.

It appears something is happening when the API is attempting to apply the change (The student record is locked for a few minutes after the update fails) so it seems like the API internal validation checks succeed, but when it attempts to actually update the student record, the process dies. As noted before the logs under TASS API Applications simply says "Error Executing Database Query." all of which points to a subtle error in the code used to update the database. The fact no one else is having the issue suggests there's some problem with updating only the alt_id field so probably an extra field in the SQL that is being set to blank or null and causing the query to fail.

If you cannot be arsed fixing your product, can you at least supply the SQL used by this component so I can patch around your crappy code?

[BlueGibbs]

I've found the problem. When an update is made the API attempts to record the app code in the update_by field... Which appears to be fine for the employees table, but this field is limited to 8 characters in students table.

For anyone encountering a similar issue in the future, check the error.log file on the tass application server. It should have the SQL query generated by the student\persist.cfc module and (hopefully) point you in the direction of what brain-damage in TASS is causing your issue.