Ed-Fi Known Errors and Dependencies

As of state reporting version 25.11.2.0, these are the known errors and dependencies with Ed-Fi Publishing. If your issue is not indicated below, please reach out to powerschool@ed.sc.gov for assistance. Another resource for SC known issues with Ed-Fi publishing is available through PowerSchool Community.

Ed-Fi Known Errors and Dependencies

Resolvable Issues

Organization Information

Code Problem Solution

409 error


Organization Information, Locations error. { "message": "The value supplied for the related 'School' resource does not exist.","correlationId": "Root=1-669e7264-4f6d436871092cf952761405"

Return to the Plugin Management Configuration page, click on PowerSchool DataExchange (DEX), click on Profile Configuration.  Review the type of profile you selected.  The profile type needed is v7.  If you have selected v3, submit a case to PowerSchool to have the profile corrected.
409 error

Organization Information, Locations error. { "message": "The value supplied for the related 'School' resource does not exist.","correlationId": "Root=1-669e7264-4f6d436871092cf952761405"

}

Return to the Plugin Management Configuration page, click on PowerSchool DataExchange (DEX), click on Profile Configuration.  Review the type of profile you selected.  The profile type needed is v7.  If you have selected v3, submit a case to PowerSchool to have the profile corrected.

Organization Schedules

Code Problem Solution
Varied error messages* Error related to terms and enrollments. Ensure student's summer school entry and exit dates do not overlap with their home school entry and exit dates.
Dependency* Records are held in dependency on Student Unique ID. This indicates that there are missing SUNS numbers. You may have to get a SUNS ID manually from the SUNS application (found in SCDE web portal). Also check to see if your district has "Near Matches" in the SUNS database. Fill in the Student State Number (or wait for it to populate). Then, republish.

400 error code: { "message": "Validation of 'Course' failed.
\n\tValidation of 'CourseIdentificationCodes' failed.
\n\t\tCourseIdentificationCode[1]:
CourseIdentificationSystemDescriptorId is required.
\n\t\tCourseIdentificationCode[1]: IdentificationCode is required.\n"
}


 
Credit Type is now a mandatory field. Many courses have been used without having a value in that field so they are now appearing as errors.

Add Credit Type for the course:

This video clarifies how to resolve this error with a "Quick Import" in PowerSchool when there are many errors. Here are steps to accompany the Quick Import video.

Ed-Fi : Fixing Credit Type Errors with "Quick Import" in PowerSchool


 

Student Identification
 

Code Problem Solution

Dependency

Inactive/Graduated student records are being held in dependency. From your Ed-Fi Dashboard click "Run Now" followed by "Unpublish Ineligible." This will start publishing in several categories on your Dashboard. Give this time to complete in all categories before you publish another resource.

Student Enrollments
 

Code Problem Solution

400 Error

Data are not landing in the ODS for US Birth Country. 

 

Sample error message: { "message": "Unable to resolve value 'US' to an existing 'CountryDescriptor' resource." }

Select an acceptable "Birth Country" value: https://www.youtube.com/watch?v=kV6gPW5LcCg
Dependency A dependency on Student School Record means that there is an issue with the publishing of Student School under the Student Enrollment category. Student School might be missing, for example.

The dependency can occur in any category below Student Enrollments.

To troubleshoot, try republishing Student Enrollments.

If this doesn’t work, there could be an issue with the record not meeting the selection criteria for publishing. A good place to start checking is the Enrollment History page and checking that the dates make sense. That is, an end date can’t be before a start date. It also can help to check the selection criteria for Student Enrollments publishing here: Student Enrollments

Once this Student School event is published under Student Enrollments, the dependencies lower down the board should publish.

Student Contacts
 

Code Problem Solution

403 Error

“Data cannot be updated until linked to a school.” 

Contacts are attempting to publish while not being linked to an active student record.

Reference “Active Contacts Associated to Only Inactive Students” in the Contacts tab in Level Data to identify these individuals and update contacts and relationships. 

 

If the student is a current student, Republish Records from the student’s individual Publishing page and then republish Contacts for this student.

Student Sections
 

Code Problem Solution

Dependency

Students who have transferred out from previous years but were accidentally enrolled in current year sections.

Delete the invalid section enrollments for these students:

The dependency is due to there being no school enrollment for these students for the current year. There should be no attendance for them for the current year, either. If this is the circumstance, then the issue may be resolved by deleting the invalid section enrollments for these students and then running a “Purge Unpublished” for the Student Sections category in the dashboard. 

A word on deleting the invalid records:

Deletion of Attendance and CC records can be done via DDA. It is important to note when working in DDA to make sure you have a good backup before deleting anything. Verify counts and the records being deleted prior to deleting. It would be prudent to work in DDE and then only switch over to DDA when you are ready to delete the records. Never have multiple PowerSchool tabs open to DDE/DDA when making changes in DDA.

409 Error Errors for courses with Alternate Course Numbers Remove the Alternate Course Number
Dependency Records are held in dependency on Student School Record and/or Sections. Fix any issues of overlapping enrollment on the Transfer Info page. Then, check to make sure class enrollments match school enrollments and fix if not.
409 Error The value supplied for the related 'Section' resource does not exist.", "correlationId”

- Purge Unpublished for the Student (or Teacher) Sections

- Publish All on Org Info, Org Schedules & Student (or Teacher) Sections


 

Staff Associations
 

Code Problem Solution

Dependency

Records are held in dependency on Staff School Record.

First, check to make sure the staff record is marked as active on the Staff Information page if the teacher should be active. If the teacher should NOT be active, check to see if they are assigned any course sections. You may have to delete the course sections if so. Also, be sure the teacher is active in all the schools where they have active sections.
 

Student Discipline
 

Code Problem Solution

400 Error

{"message": Unable to resolve value '____' to an existing 'BehaviorDescriptor' resource.","correlationId"}

re-download descriptors and republish
400 Error { "message": "The request is invalid.", "correlationId": "Root=1-68373bda-1631b4dc582705760623e35a", "modelState": { "request.disciplineDate": [ "The supplied value is invalid." ] } } ensure that actions have valid begin dates and republish
400 Error  { "message": "Validation of 'DisciplineIncident' failed.\n\tIncidentDescription contains a potentially dangerous value.\n" }

Check the incident: 

  • Start Page > Incident Management
  • Filter by ID = ___ (incident IDs listed in errors) and Apply
  • Select Incident
  • Read Description of Incident and look for unexpected characters - likely "<" or ">" - these may have been posted from an HTML doc
  • Remove characters, save Incident, republish Discipline

Transcripts
 

Code Problem Solution

409 Error

Error message: "{ "message": "A natural key conflict occurred when attempting to update a new resource with a duplicate key. This is likely caused by multiple resources with the same key in the same file. Exactly one of these resources was updated." }"

To resolve, duplicate course numbers will need to be corrected before republishing. Please only make changes to course numbers mid-year with the greatest caution, as doing this mid-year can cause issues.
Error: 409 {“message”: ‘The values supplied for properties ‘CourseAttemptResultDescriptor, CourseCode, CourseEducationOrganizationId, EducationOrganizationId, SchoolYear,
StudentUniqueId, TermDescriptor’ of entity ‘CourseTranscript’ are not unique.”
District PowerSchool administrators should reach out to the school to see if the grades need to be corrected.
409 Error Academic Records errors. Sample error message (error messages may vary): "Validation of StudentAcademicRecord failed. \n\f\validation of 'StudentAcademicRecordAcademicHonors' failed.\n\#studentAcademicHonor[0] HonorDescription is required \n" Include all relevant data for the credential or award. For example, if the date is provided for the Employability Credential, but neither the "Seeking" nor the "Earned" check box is checked, this error will occur.
*indicates that this error will cause subsequent errors further down the dashboard

Issues that will be fixed with the next PS Release –

Assessments

Code Problem Which Release Will Fix

Student Discipline

Code Problem Which Release Will Fix

Student Contacts

Code Problem Which Release Will Fix

Student Grades

Code Problem Which Release Will Fix
Depedency Records are held in dependency on Student Grades TBD