Table of Contents
Overview
Course Cannot be Found in the Course Catalog in Scheduling
Failure to Create Course that Already Exists
Missing Credit Type for Course
Missing EventId, EventSubType or CreditType
Transaction Count after EXECUTE
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 PowerCampus.
Many errors can be prevented by creating a rule in Coursedog; learn more about rules here.
For a look at additional integration errors that can occur regardless of SIS, go here.
For a general overview of managing merge errors, go here.
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).
Course Cannot be Found in the Course Catalog in Scheduling
Name of Error in Merge Report
Failed creating section because {courseId}/{subtype} is not in the course catalog
Example
Failed creating section because ADV57075/CRSE is not in the course catalog
Explanation
In PowerCampus when creating a section for a course, the subtype must match one of the subtypes that has been set at the course level.
If a subtype is selected that does not exist for the course, the integration will not be able to identify the course in the course catalog. This will cause this merge error and prevent the user from creating the section.
Best Practice / How to Resolve
In order to resolve this error, the user should select a valid subtype for the section.
Failure to Create Course that Already Exists
Name of Error in Merge Report
Failed creating Event because it already exists
Explanation
This error occurs when the integration tries to create a course that already exists in PowerCampus. This can occur for various reasons.
PowerCampus does not support revisions of a course. All changes to an existing course need to be made on the same revision. Any revisions made in Coursedog will need to be deleted which will need to go through a support ticket.
Integration Filters can also prevent the integration from being able to identify that a course already exists in the SIS. If revisions are not being used, please check the filters.
Best Practice / How to Resolve
Ensure only one revision exists for the course. If multiple exist, please apply all changes to the revision that does not have a date assigned. Once the changes are applied to the correct revision, create a support ticket for the Coursedog team to remove the extra revision.
If only one revision exists, verify Integration Filters are not being applied to the Course Curriculum merges.
Missing Credit Type for Course
Name of Error in Merge Report
Failed creating EVENTCREDITTYPE due to Cannot insert the value NULL into column 'CREDIT_TYPE', table 'Pwr_Campus.dbo.EVENTCREDITTYPE'; column does not allow nulls. INSERT fails.
Explanation
Credit Type is a required field that must be set for a Course in PowerCampus.
Best Practice / How to Resolve
Update the course in Coursedog to use a valid Credit Type and resave.
Missing EventId, EventSubType or CreditType
Name of Error in Merge Report
Failed creating EventCreditType due to required input fields: EventId, EventSubType and CreditType
Explanation
EventId, EventSubType, and CreditType are required fields. The creditType must be set at both the course level and the subtype level on the course template. The EventCreditType uses the value set at the subtype level.
Credit Type also needs to have attribute mappings set up in the integration hub to support POSTing this value.
Best Practice / How to Resolve
Update the Sub Type’s Credit Type on the course and resave.
Credit Type also needs to have attribute mappings set up in the integration hub to support POSTing this value.
Transaction Count after EXECUTE
Name of Error in Merge Report
Internal error occurred : Transaction count after EXECUTE indicates a mismatching number of BEGIN and COMMIT statements. Previous count = 0, current count = 2."}
Explanation
This failure currently happens for two known reasons:
When you try to insert a professor that already exists or
When you do not provide the necessary fields in the input payload.
If it is neither of these reasons, a support ticket will need to be opened with the Coursedog team to work with N2N to investigate further.
Best Practice / How to Resolve
Ensure that the professor does not already exist on the section and that all required meeting pattern information is being sent.
If these are all correct, please create a support ticket for the Coursedog team to work with N2N on finding a resolution.