Table of Contents
Overview
Acad Org Configuration for Instructor Edit
Associated Class Cannot Be Blank Or Zero
Auto Enroll 1 & 2 Must Be Different
Cannot Change Part of Term if Class Already has Enrollments
Cannot Update Min Enrollment Field when Class Status is Cancelled
Changing Class Dates Error
Class CI Save Failure
Class has been Hard Deleted in PeopleSoft
Could Not Find Class
Could Not Set CI Property EMPLID
Could Not Set CI Property EMPL_RCD
Could Not Set CI Property SESSION_CODE
Incorrect Component Selected
Incorrect Component and Associated Class
“Internal Error" or “Error Loading Additional Pages”
Load Factor
Meeting End Date Must Be Before Section and Session End Date
Missing Course in PeopleSoft
Parsing XML Error
Part Time Instructors Cannot Be Assigned to Full Time Sections
Preferred Room Capacity Cannot Be Zero
Prim Instr Section Must Exist
Relationships (Combined Sections) Must Have Same Instructor
Relationships (Combined Sections) Must Use SIS groupId if it Exists
Reserve Capacity Total Must Not Be More Than Enrollment Capacity
Sections Cannot Be Combined
Set Class Type Error
Setting Diploma Print Flag With No Diploma Description
Setting Empty Program Type
Setting Empty Transcript Level
Start Date Must Be Before End Date
Start Time Must Be Before End Time
Subject Area + Course Number Combination is Not Unique
Unable to Cancel Graded Class
Unable to Persist Some Updates on SIS
Update Call Concurrencies
Violation of Business Logic/Rules in PeopleSoft
Related Articles
Overview
Student Information System (SIS) platforms have certain requirements that must be met in order for data to be accepted during a merge. If those requirements are not met, a merge error can occur.
This article captures common merge errors for PeopleSoft. .
Many errors can be prevented by creating a rule in Coursedog; learn more about rules.
Go here for a look at additional integration errors that can occur regardless of SIS.
If you are unable to resolve a merge error by following the directions noted below and you aren’t yet live, reach out to your Project Manager. If you are fully implemented, open a support ticket (and alert your Customer Success Manager as well).
Acad Org Configuration for Instructor Edit
Name of Error in Merge Report
Update Failure - Fields with Errors: (CLASS_INSTR.EMPLID,CLASS_INSTR.EMPL_RCD) - Could not set CI Property EMPLID: 10958208; Could not set CI Property EMPL_RCD: 4; At least one CI update failed - We will NOT attempt CI save - Rejecting transaction.
Explanation
Assignment for the instructor fails as the User attempts to perform the assignment transaction via the component interfaces as the integration does not have adequate access to the person records, only the I/A records.
The user is assigning the instructor from the pool of person records since the configuration on the Academic Organization page is set to "Edit Instructor Against '' Personal Data, which might not be a best practice and is out of scope of the Coursedog integration.
How to Resolve
- To resolve this issue, assign to the user attempting to perform the assignment transaction via component interface in PeopleSoft access, a primary permission list that has full access to the person records.
- This assignment is done in the PeopleSoft User Profile page.
- There is a section at the bottom of that page with a prompt for selection of the primary permission list.
- Perform this action when such an issue occurs.
Associated Class Cannot Be Blank Or Zero
Name of Error in Merge Report
"status": "fail",
"response": "Update Failure - Fields with Errors: (CLASS_TBL.ASSOCIATED_CLASS) - Could not set CI Property ASSOCIATED_CLASS: 0; At least one CI update failed - We will NOT attempt CI save - Rejecting transaction."
Explanation
The Associated Class number must be a non zero number and posted to the SIS on all create/update operations.
Best Practice / How to Resolve
Ensure the section has an Associated Class number that is non zero.
Long-Term Fix
We have implemented a rule in the baseline PeopleSoft environment that warns Schedulers when they have made this mistake.
If marked as a “Required Rule”, then Schedulers cannot save the section until they resolve the problem.
Auto Enroll 1 & 2 Must Be Different
Name of Error in Merge Report
"status": "fail",
"response": "Update Failure - Fields with Errors: (CLASS_TBL.AUTO_ENROLL_SECT_1,CLASS_TBL.AUTO_ENROLL_SECT_2) - Could not set CI Property AUTO_ENROLL_SECT_1: 1; Could not set CI Property AUTO_ENROLL_SECT_2: 1; At least one CI update failed - We will NOT attempt CI save - Rejecting transaction."
Explanation
Each section in PeopleSoft has an Auto Enroll 1 & Auto Enroll 2 field.
If these fields are filled out and set to the same value in Coursedog, then when we post the update to PeopleSoft, it will reject any updates.
How to Resolve
Edit the section(s) to update the Auto Enroll fields to be different.
Long-Term Fix
We have added a rule to the PeopleSoft baseline environment in Coursedog to help prevent schedulers from submitting a section edit/add if this rule is broken. If marked as a “Required Rule”, then Schedulers cannot save the section until they resolve the problem.
Cannot Change Part of Term if Class Already has Enrollments
Name of Error in Merge Report
“...This class has enrollment. You are not allowed to change the session code…”
Explanation
This can happen if a Scheduler tries to update a Part of Term where enrollments exist (PeopleSoft does not allow this).
How to Resolve
Reset the Part of Term
Long-Term Fix
Coursedog’s “Edit Part Of Term With Meetings and Enrollment” prebuilt rule can prevent this situation, but it needs to be turned on and enabled.
Cannot Update Min Enrollment Field when Class Status is Cancelled
Name of Error in Merge Report
(CLASS.TBL.MIN.ENRL) - Could not set CI Property MIN_ENRL: [ID]; At least one CI update failed...
Explanation
If a user tries to set a class as cancelled while the section has a non-zero minimum enrollment field Peoplesoft error - will not allow Min Enrollment field updates if the class status is cancelled.
Best Practice / How to Resolve
Resolve the min enrollment field update by revisiting class status or reset and update in the SIS.
Ensure minimum enrollment is zero when cancelling a section.
Changing Class Dates Error
Explanation
This is caused by a confluence of factors with the underlying PeopleSoft code, how the data is entered, and nuances with component interface behavior.
This can manifest on class date changes and or session changes where the new session dates are in a different range.
This only happen when:
The class has existing meeting patterns.
The new class start date is moved to a date that is greater than or equal to the previous end date.
Specifically, CLASS_MTG_PAT.START_DT.FieldEdit and CLASS_MTG_PAT.END_DT.FieldEdit code triggers an error message and will reject the update.
How to Resolve
Open a Coursedog support ticket if you are unable to resolve independently.
Class CI Save Failure
Name of Error in Merge Report
Class CI Save Failure - PS_EVENT_LAST_TBL is in use
Explanation
This is an error raised by PeopleSoft as a safeguard against potential data conflicts, likely caused by concurrent updates to the same table (e.g. two people editing the same section at once).
This mechanism is in place to ensure data integrity, and in these cases, PeopleSoft prevents changes until the conflicting process completes.
How to Resolve
Rerun the merge
Name of Error in Merge Report
"status": "fail",
"response": "Update Failure - Class CI Save Failure. Check that this class can be saved in the PeopleSoft UI.; Data being added conflicts with existing data. (18,2) - When adding a new item to the database, the system found a conflicting item already exists.This problem can happen if another user has entered similar information at the same time as you. Note the changes you have made, cancel the page, then retry your changes.If the problem persists, it may be because of an application or other programming error and should be reported to technical support staff.This error occurs when the keys on the record being inserted match a record that is already in the database. The application must ensure that each inserted record has unique keys.; Error saving Component Interface. {N_CLASS_DATA} (91,37) - An error occurred while saving the Component Interface. The most likely cause is that required fields were uninitialized, or that the business logic enforcement written in PeopleCode returned an error."
or
Update Failure - Class CI Save Failure. Check that this class can be saved in the PeopleSoft UI.; Data being added conflicts with existing data. (18,2) - When adding a new item to the database, the system found a conflicting item already exists.This problem can happen if another user has entered similar information at the same time as you. Note the changes you have made, cancel the page, then retry your changes.If the problem persists, it may be because of an application or other programming error and should be reported to technical support staff.This error occurs when the keys on the record being inserted match a record that is already in the database. The application must ensure that each inserted record has unique keys.; Error saving Component Interface. {N_CLASS_DATA} (91,37) - An error occurred while saving the Component Interface. The most likely cause is that required fields were uninitialized, or that the business logic enforcement written in PeopleCode returned an error."
Explanation
This issue occurs when PeopleSoft is attempting to update multiple sections of the same course at once. It is unrelated to our merge settings, but an issue on the PeopleSoft side.
If a user tries to create a duplicate section number for a course in a term, they will receive a PeopleSoft error.
For example, if BIO200 Section 01 exists in Fall 2020, then there can be no other Section of BIO200 with the 01 Section Number.
How to Resolve
In Coursedog we prevent Schedulers from making this mistake by automatically incrementing the “add section” number and code that watches for two Schedulers creating a section at the same time. However, if this does occur it might be necessary to delete the section in Coursedog and then recreate it.
The path to resolution is to have the user retry saving these sections one at a time (i.e. save one section, wait for it to sync, then save the next).
Class has been Hard Deleted in PeopleSoft
Name of Error in Merge Report
Update Failure - Fatal Error: Could not find CLASS_NBR: 2078 in component buffer to updated. Aborting operation; Failure due to application security. Processing will stop. (0,0) N_CLASS_V2.classUpdateHandler.OnExecute Name:onRequest PCPC:13368 Statement:169
Explanation
Someone deleted the class from PeopleSoft that Coursedog is trying to post, and the Merge Settings in Coursedog are set to Always Coursedog, preventing the deletion from being respected by Coursedog.
Also, someone has edited the class in Coursedog, and we’re trying to post it yet it doesn’t exist in the PeopleSoft system.
Best Practice / How to Resolve
Ensure the merge settings “Default Source of Truth” is set to “Resolve as Coursedog”. This will allow the class to be deleted from Coursedog.
Could Not Find Class
Name of Error in Merge Report
“postBody.classNbr is required”
or
“Update Failure - Fatal Error: Could not find CLASS_NBR in component buffer to updated. Aborting operation; Failure due to application security. Processing will stop. (0,0) N_CLASS_V2.classUpdateHandler.OnExecute Name:onRequest PCPC:13744 Statement:170”
Explanation
These errors will occur if the data in Coursedog gets out of sync with the SIS data (most often caused by overlapping merges, i.e. a manual merge being run at the same time as a real-time merge).
How to Resolve
Confirm the section does not exist in PeopleSoft.
Delete the section in Coursedog.
Rebuild the section in Coursedog.
Save section and let the section sync to PeopleSoft.
Could Not Set CI Property EMPLID
Name of Error in Merge Report
“Could not set CI Property EMPLID”
Explanation
This issue is often caused by invalid effective dates for instructors.
Best Practice / How to Resolve
This can be corrected by editing data in the SIS.
Specifically, navigate to the Instructor/Advisor Table under Curriculum Management > Instructor/Advisor Information and ensure that the Instructor effective date is Less than or equal to the Term Start Date
Could Not Set CI Property EMPL_RCD
Name of Error in Merge Report
Could not set CI Property EMPL_RCD
Explanation
This issue is often caused by invalid effective dates for instructors.
Best Practice / How to Resolve
This can be corrected by editing data in the SIS.
Specifically, navigate to the Instructor/Advisor Table under Curriculum Management > Instructor/Advisor Information and ensure that the Instructor effective date is Less than or equal to the Term Start Date
Could Not Set CI Property SESSION_CODE
Name of Error in Merge Report
Could not set CI Property SESSION_CODE
Explanation
Sections that were rolled over in PeopleSoft might carry over the session reference that might not exist for that level.
Example
A Summer Session section produced an integration error when attempting to POST session_code=1 because no such session exists for the Term.
The rolled over section was trying to POST a session code for Regular Academic Session (Undergraduate) / session_code 1.
Since it was a session that did not exist for the term, it left the Session as blank in Coursedog.
How to Resolve
Correcting this in the Coursedog UI will allow the correct value to then be sent.
Incorrect Component Selected
Name of Error in Merge Report
Update Failure - Fields with Errors: (CLASS_TBL.SSR_COMPONENT) - Could not set CI Property SSR_COMPONENT: LLC; At least one CI update failed - We will NOT attempt CI save - Rejecting transaction.
Explanation
The Component drop down field in the section editing modal should show only the correct options for the Scheduler to select from and display only those approved for the course, so this error should only come up if rolled term data refers to component options that are no longer valid.
How to Resolve
Open the section in the Section Dashboard and select the correct Component from the drop down menu and save.
The section will sync with the SIS and the error will be corrected.
Incorrect Component and Associated Class
Name of Error in Merge Report
Update Failure - Fields with Errors: (CLASS_TBL.SSR_COMPONENT,CLASS_TBL.ASSOCIATED_CLASS) - Could not set CI Property SSR_COMPONENT: LAB; Could not set CI Property ASSOCIATED_CLASS: 9999; At least one CI update failed - We will NOT attempt CI save - Rejecting transaction.
Explanation
Associated class errors are often paired with COMPONENT errors.
How to Resolve
Review which components are permitted.
Edit the component and associated class fields via Coursedog’s Section Dashboard.
Once saved the section will sync with the SIS, and the error will be resolved.
“Internal Error" or “Error Loading Additional Pages”
Name of Error in Merge Report
Internal error encountered
Explanation
This will occur if the school’s SIS is overloaded and cannot process the request.
How to Resolve
Reduce the load on the SIS either by increasing the #CPUs and Memory, or else process the integration during lower load periods.
Load Factor
Name of Error in Merge Report
Update Failure - Fields with Errors: (CLASS_INSTR.INSTR_LOAD_FACTOR) - **Could not set CI Property INSTR_LOAD_FACTOR: 0;** At least one CI update failed - We will NOT attempt CI save - Rejecting transaction."
Explanation
In the Instructor Roles and Details modal, you set “Load Factor” to “0”.
PeopleSoft does not permit a value of 0; however, if entered directly into the PeopleSoft UI, PeopleSoft converts a “0” to an empty value.
Best Practice / How to Resolve
Rather than setting a “0” value, it is recommended to simply leave the Load Factor blank in order to achieve the desired result in the SIS.
Meeting End Date Must Be Before Section and Session End Date
Name of Error in Merge Report
Update Failure - Fields with Errors: (CLASS_MTG_PAT.END_DT) - Could not set CI Property END_DT: 2021-08-12; At least one CI updated failed - We will NOT attempt CI save - Rejecting transaction.
Explanation
In PeopleSoft, meetings can have their own date ranges that are separate from either the section dates or the session dates.
The end date for each meeting, if set, must be less than or equal to the session end date and the term end date.
How to Resolve
This is something Schedulers can resolve themselves by going into the section editing modal and updating the meeting dates to be within the allowed range.
Missing Course in PeopleSoft
Name of Error in Merge Report
"Unable to sync some changes...unable to validate some updates...errorDetails: {[Property ID], error:”\”postBody.institutionId/” is required. \postBody.courseId” is required. \postBody.crseOfferNbr” is required. \postBody.classAssocTable[0].courseId” is required…
Explanation
For PeopleSoft integrations, the Courses displayed for each term in Academic Scheduling are filtered to only show active courses that are effective by the term's start date, and have canSchedule=true.
For an unknown reason, in PeopleSoft it is possible to create a section for a course A in Term B, even if Course A is not effective for Term B. When that data gets loaded in Coursedog, it causes two issues:
The course is missing in Coursedog, so a user can search for that course or any of the course's sections
When sending updates (posting/merging) from Coursedog to PeopleSoft, the above error will appear.
How to Resolve
If this happens, schools need to update the effective date of the course in PeopleSoft, then reload all scheduling data into Coursedog.
Parsing XML Error
Name of Error in Merge Report
Update Failure - Failure parsing inbound XML. It does not match expected structure.; Failure due to improper XML (0,0) N_CLASS_V2.classUpdateHandler.OnExecuteName:onRequest PCPC:5096 Statement:76
Explanation
This error could occur if the data contains an unhandled set of special characters that causes the data to not be able to be transformed correctly.
How to Resolve
Open a support ticket with Coursedog.
Part Time Instructors Cannot Be Assigned to Full Time Sections
Name of Error in Merge Report
Ex: Warning -- Instructor Class is Full-Time, Job is Part-Time. (14600,602) -
Instructor class and job do not match for full/part time assignment.
Explanation
If an instructor is part time, the job record associated with a section must also be part time. Otherwise peoplesoft will return an error.
How to Resolve
Resolve the conflict
Long-Term Fix
This is a situation that Schedulers must be trained on.
If they make this mistake, they will see an error in the section editing modal on the next edit indicating the failure and the cause noted above.
Preferred Room Capacity Cannot Be Zero
Name of Error in Merge Report
"status": "fail",
"response": "Update Failure - Fields with Errors: (CLASS_TBL.ROOM_CAP_REQUEST) - Could not set CI Property ROOM_CAP_REQUEST: 0; At least one CI update failed - We will NOT attempt CI save - Rejecting transaction."
Explanation
When creating and/or updating sections, PeopleSoft will not let Preferred Room Capacity to be empty or zero. As a result, if this field is not set, we default the value to 1.
Best Practice / How to Resolve
Ensure sections have Preferred Room Capacity set at 1 or more.
Long-Term Fix
We have added a rule to the baseline PeopleSoft environment to prevent Schedulers from making this mistake.
If marked as a “Required Rule”, then Schedulers cannot save the section until they resolve the problem.
Prim Instr Section Must Exist
Name of Error in Merge Report
"status": "fail",
"response": "Update Failure - Fields with Errors: (CLASS_TBL.PRIM_INSTR_SECT) - Could not set CI Property PRIM_INSTR_SECT: 001; At least one CI update failed - We will NOT attempt CI save - Rejecting transaction."
Explanation
If a user sets the Prim Instr section to a value that does not exist (i.e. a section that is not in PeopleSoft), an error will occur.
Best Practice / How to Resolve
Ensure Primary Instr Section match the section number of the section being edited exactly.
Long-Term Fix
In some PeopleSoft integrated environments, we can require that the Primary Instr Section match the section number of the section being edited exactly and can create a rule as noted below.
If marked as a “Required Rule”, then Schedulers cannot save the section until they resolve the problem.
Relationships (Combined Sections) Must Have Same Instructor
Name of Error in Merge Report
“Update failure - CI Save failed for SCTN_CMBND; Class Numbers: xxx and xxx cannot be combined because they have different instructors...
Explanation
Relationships in Coursedog set as "Same Time Same Day Same Room" relationships must also have the same instructor.
How to Resolve
Edit the instructor assignment
Long-Term Fix
Coursedog will not warn the Scheduler if they make this mistake; Schedulers should be trained to ensure the same instructor is assigned to sections in a “Same Time Same Day Same Room” relationship.
Relationships (Combined Sections) Must Use SIS groupId if it Exists
Explanation
Relationships in Coursedog must use the SIS groupId field if it exists on the SIS, i.e. alwaysInstitution or resolveInstitution.
Otherwise a new groupId will be calculated to send back to the SIS, and the SIS will create a separate/new relationship.
How to Resolve
Coursedog Data Engineers will ensure your default Merge Setting configuration for groupId is set up correctly.
Reserve Capacity Total Must Not Be More Than Enrollment Capacity
Name of Error in Merge Report
Ex: The Enrollment Reserve Capacity Total (42) must not exceed the Class Enrollment
Capacity of 30. (14620,42) - The sum of Enrollment Reserve Capacity cannot
be greater than the Class Enrollment Capacity.
Explanation
If a user creates a reserve capacity group, the reserve capacity total cannot exceed the enrollment capacity.
Best Practice / How to Resolve
Edit the receive capacity to be less than enrollment capacity.
Long-Term Fix
This is a situation that Schedulers must be trained on.
If they make this mistake, they will see an error in the section editing modal on the next edit indicating the failure and the cause noted above.
Sections Cannot Be Combined
Name of Error in Merge Report
Update Failure - CI Save Failed for SCTN_CMBND; Class numbers: [ID] and [ID] cannot be combined because they have different [meeting patterns or rooms]
Explanation
If two sections cannot be combined, it is likely that they do not have the same meeting patterns and room assignments.
However, in rare cases, this error can occur even if two sections have the exact same meeting pattern and room assignment. This is a bug in PeopleSoft.
How to Resolve
If users see this, they should remove both meeting patterns from the sections, then create the relationship, then try to add the meeting patterns back in.
Set Class Type Error
Name of Error in Merge Report
"Update Failure - Fields with Errors: (CLASS_TBL.CLASS_TYPE) - Could not set CI Property CLASS_TYPE: E; At least one CI update failed - We will NOT attempt CI save - Rejecting transaction."
Explanation
Issue appears when setting the Class Type of certain sections as Enrollment sections when they should be Non-Enrollment sections.
Here’s what PeopleSoft says about the Class Type field:
The class type of Enrollment indicates which section is the primary section at enrollment time.
The class type of Non-Enrollment is used to indicate that the section choice is the student's secondary enrollment option, or that the section is used in auto-enrollment. Within a class, only one component can possess the class type of Enrollment.
How to Resolve
Edit Class Type field directly in the Coursedog section editing modal for the sections in question and save, allowing the section to sync with the SIS.
Setting Diploma Print Flag With No Diploma Description
Name of Error in Merge Report
The Diploma Description is required if the Diploma Print Flag is on. Enter a description if the Print Flag is on
Explanation
If a user sets the Diploma Print Flag to “Yes”, they must also provide a diploma description.
How to Resolve
Provide a diploma description.
Setting Empty Program Type
Name of Error in Merge Report
Update Failure - Fields with Errors: (ACAD_PLAN_TBL.ACAD_PLAN_TYPE) - Could not set CI Property ACAD_PLAN_TYPE
Explanation
The Program academic plan type (ACAD_PLAN.ACAD_PLAN_TYPE) field must be set
How to Resolve
Set the Program’s academic plan type (ACAD_PLAN.ACAD_PLAN_TYPE) field.
Setting Empty Transcript Level
Name of Error in Merge Report
Update Failure - Fields with Errors: (ACAD_PLAN_TBL.TRANSCRIPT_LEVEL) - Could not set CI Property TRANSCRIPT_LEVEL
Explanation
The Program transcript level (ACAD_PLAN.TRANSCRIPT_LEVEL) field must be set.
How to Resolve
Example Scenario
Set the Program transcript level (ACAD_PLAN.TRANSCRIPT_LEVEL) field
The class meeting pattern has the same start and end dates as the class start/end.
User changes the session to a later session 7/5/21 – 8/3/21.
Incoming request from Coursedog has class start/end date & class meeting pattern dates matching the 7/5/21 and 8/3/21.
Class start and end dates are adjusted just fine but when the new class meeting pattern date change is attempted to change from 5/31/21 to 7/5/21, it gets an error because 7/5/21 is AFTER the current end date of 6/29/21 because it hasn’t changed yet.
Resolution
In the above example scenario, the Manual Path to Resolution is as follows:
Remove the meeting in Coursedog. Save and allow the real time synchronization to occur.
Change the part of term (session). Save and allow the real time sync to occur
Add the meeting back in and save. Synchronization should then correct the issue.
Start Date Must Be Before End Date
Name of Error in Merge Report
Fields with errors: CLASS_TBL.END_DT. Could not set CI property END_DT...
Explanation
This error will be returned if the section start date falls after its end date.
How to Resolve
Resolve the date conflict in the section(s).
Long-Term Fix
This can be prevented by implementing a simple rule in Coursedog that prevents Schedulers from saving the section when the dates violate the rule.
Your provisioned integrated environment should already have this rule added for you by your Customer Success team.
Start Time Must Be Before End Time
Possible Names of Error in Merge Report
Fields with errors: CLASS_MTG_PAT.MEETING_TIME_END. Could not set CI property...
Explanation
If a user creates a section meeting where start time is after the end time, then PeopleSoft will return an error.
How to Resolve
Resolve the time conflict in the section(s).
Long-Term Fix
Your customer success team will add a rule to prevent the Scheduler from being able to save the section, so long as the “This rule cannot be violated” checkbox on the rule is checked.
Subject Area + Course Number Combination is Not Unique
Name of Error in Merge Report
Update Failure - Failure: Attempting to load CRSE_ID:A. However, B was loaded into the Component buffer. Check that your INSTITUTION/SUBJECT/CATALOG_NBR is unique.
Explanation
In PeopleSoft, it is possible to create a course offering that has a Subject Area + Course Number combination that is not unique, and that matches that of another course offering with a different Course ID.
In the following scenario, for example, there are two unique Course IDs, and within each, there are course offerings with the same Subject Area + Course Number:
In Coursedog, when a user attempts to create or update a section associated with these Courses, an integration error will occur, preventing Coursedog from successfully creating or updating these sections. This is due to an issue at the Component Interface layer in PeopleSoft that determines how course information is loaded when these create or update operations are executed.
How to Resolve
No fix is expected from PeopleSoft in the near future; see “Recommendation” below for a workaround.
Recommendation / Workaround
If possible, change the course number of one of the duplicate courses, so that it contains a unique Subject Area + Course Number value.
Unable to Cancel Graded Class
Name of Error in Merge Report
Update Failure - Fields with Errors: (CLASS_TBL.CLASS_STAT) - **Could not set CI Property CLASS_STAT:X;** At least one CI update failed - We will NOT attempt CI save - Rejecting transaction."
Explanation
PeopleSoft does not allow cancelling a section in which students have received grades.
You will see this error in the section’s sync status bar.
Below is the error message presented within PeopleSoft for the same operation.
How to Resolve
To cancel the class, all grades assigned for the class must be removed within PeopleSoft as noted in the PeopleSoft error.
Unable to Persist Some Updates on SIS
Name of Error in Merge Report
“Unable to persist some updates on SIS”, “Unexpected state deprecating Course dog entity [ID]; No changes made to Course dog data…”
Explanation
This can happen if a Scheduler clicks “Add Section” and then immediately re-enters the section, makes an edit and saves prior to the section syncing to the SIS.
Best Practice / How to Resolve
Coursedog automatically rectifies errors like this. There should be no cleanup needed by the Scheduler when this issue arises.
Update Call Concurrencies
Name of Error in Merge Report
Update Failure - Class CI Save Failure. Check that this class can be saved in the PeopleSoft UI.; Data being added conflicts with existing data. (18,2) - When adding a new item to the database, the system found a conflicting item already exists.This problem can happen if another user has entered similar information at the same time as you…
Explanation
For PeopleSoft, when updating two different sections that belong to the same course, the updates cannot be made at the same time and must be made sequentially.
Best Practice / How to Resolve
Note the changes you have made, cancel the page, then retry your changes.
Long-Term Fix
Coursedog generally prevents this issue from occurring and we don't see it happening in institution environments.
Violation of Business Logic/Rules in PeopleSoft
Name of Error in Merge Report
"status": "fail",
"response": "Update Failure - Fields with Errors: (CRSE_CATALOG.INSTRUCTOR_EDIT) - Could not set CI Property INSTRUCTOR_EDIT: ; At least one CI update failed - We will NOT attempt CI save - Rejecting transaction."
Explanation
Many PeopleSoft environments have business rules added to them to return errors and enforce rules. For example, certain instruction modes may not be permitted for certain campuses.
Best Practice / How to Resolve
Correct the value provided for the field to meet the business logic or rule requirements and save the section to submit again.
Long-Term Fix
Ensure that any field defined at the catalog (course) level is set to default from course or use course options where applicable.
Generally in Coursedog, you can add rules that prevent schedulers from violating your PeopleSoft rules and thereby prevent them from making these types of mistakes.
E.g. “Online Instruction Mode cannot be selected for classes on ‘Upper Campus’”.
Remember that you can set the flag for “This rule cannot be violated”, which will force the scheduler to fix the mistake before being able to save the section.