ICampus reports 500 errors from REST/API interface - Cascading updates

Date
10/27/2015
Level
Level 4
Jitbit #
3590718
Summary
ICampus reports 500 errors from REST/API interface - Cascading updates
Impacted
Vendor unable to submit data
Service Impact
Service Interrupted as vendor could not submit data
Incident Detail
The core table for the edfi.section table was missing an update cascade option on the foreign key referencing the edfi.classperiod table
Technical Detail/Fix
The vendor was experiencing a 500 error on the Class Periods resource when making a change to the Name after it has been associated with a Section. They though that Cascading Updates should handle this change but it did not appear to be the case. They felt that their resource is coded correctly because when they make the same change for a Period that is not associated with a Section they did not get the error and the update is made.
To fix the issue, a cascade update script was created to update the ODS to include the change.
Creation date: 12/4/2015 9:16 AM ()      Updated: 12/4/2015 9:16 AM ()