User Tools

Site Tools


Sidebar

Table of Contents

general:tsds_upgrade

This is an old revision of the document!


Preparing for the TSDS Upgrade Guide

District Administration

  • District Administration > Tables > District Information > Campus Name/Address
  • District Administration > Options > TSDS > Options
  • District Administration > Options > TSDS > Connection
  • District Administration > Inquiry > TSDS Level 1 Errors


Finance

  • Finance > Tables > TSDS Crosswalks


Grade Reporting

  • Grade Reporting > Maintenance > Master Schedule > District Schedule > Available Courses
  • Grade Reporting > Maintenance > Master Schedule > Campus Schedule > Section
  • Grade Reporting > Maintenance > Tables > TSDS Crosswalks


Personnel

  • Personnel > Maintenance > Staff Demo > Responsibility


Registration

  • Registration > Maintenance > District Profile > District Maintenance > Demographic Info
  • Registration > Maintenance > District Profile > District Maintenance > State Reporting
  • Registration > Maintenance > District Profile > Local Program Codes
  • Registration > Maintenance > Campus Profile > Campus Information Maintenance > Demographic Info
  • Registration > Maintenance > Campus Profile > Campus Information Maintenance > Control Info
  • Registration > Maintenance > Student Enrollment > Demo1

Currently, Prior Year Leaver data is updated on Registration > Maintenance > Prior Year Leaver Tracking. However, going forward, Prior Year Leaver data will be updated for the prior year on the following screens:

  • Registration > Maintenance > Student Enrollment > Demo1
    Allow data elements to be editable for one prior year in the Phone/Address group box if the student is listed in the Prior Year Leaver Tracking Directory.

  • Registration > Maintenance > Student Enrollment > Demo3
    Allow data elements to be editable for one prior year for Military Enlistment in the Status Indicators group box if the student is listed in the Prior Year Leaver Tracking Directory.

  • Registration > Maintenance > Student Enrollment > Contact (PY Leaver)
    Allow data elements to be editable for one prior year for contacts who are: Priority = 1 and Guardian = 1 if the student is listed in the Prior Year Leaver Tracking Directory.

  • Registration > Maintenance > Student Enrollment > W/R Enroll
    Allow data elements to be editable for one prior year in the Reason field if the student is listed in the Prior Year Leaver Tracking Directory.


Known Issues (as of 11/28/2023)

—-TCC is aware and is investigating that some TSDS Parallel LEAs are not receiving the nightly extract e-mails.
—-TCC continues to work with TEA on the Finance Actual domain for PEIMS Mid-Year. At this time, no actuals are being sent to TSDS.
WS-1071Registration > Maintenance > Student Enrollment > Demo2 > Census Block
- Programming for this is not complete. For Fall PEIMS Parallel Year, TCC will apply/provide a SQL to update this data to match the data in State Reporting. Programming will be completed in a future software update.
WS-1095When an employee has a termination date entered that is a future date and they are still considered to be employed, when the extract is run for the staff endpoint, the end date is not being populated for that future date.
—-Course Transcript - Duplicate Record Found error.
An error is received on the Extract email when a student has taken 2 courses with the same service ID in the same semester.
TCC is researching a solution to this issue.


API Error Response Codes

HTTP CodeExample MessageHow to Fix
400Validation of 'RESOURCE' failed. FIELD is required.​An element of the JSON that is required is missing and needs to be added. Required fields are marked with '*' in swagger https://api.ed-fi.org/v6.1/docs/swagger/index.html?urls.primaryName=Resources 
400'RESOURCE' failed. 'RESOURCE' reference could not be resolved.A resource that was referenced from an entity does not yet exist: load the dependency resource first. See https://techdocs.ed-fi.org/display/ODSAPIS3V61/Resource+Dependency+Order ​
401Unauthorized​​Unauthorized. The request requires authentication. The OAuth bearer token was either not provided or is invalid/expired. ​
403Authorization denied. The claim does not have any established relationships with the requested resource​​Likely Causes:​ \\Your API credentials are not associated with the proper EducationOrganization or Namespace. See information under the section of this guide on “Authorization”.​ \\The API cannot tie the resource you are creating or updating to a “root” entity for which you are authorized. For example, you may be trying to update a Student, but if that student is not enrolled (via StudentSchoolAssociation) the request will fail, as the API cannot determine that your client is authorized. 
When the record is person-based (e.g., Attendance, Grades, Section Associations), it usually means the Student, Staff, or Parent record is not in the ODS so the records being sent for that person cannot be created.​
409A natural key conflict occurred when attempting to create a new resource 'RESOURCE' with a duplicate key.​​The Ed-Fi API has a natural key system alongside a standard REST ID system. This error is often protecting against the erroneous creation of a duplicate record in the API. Unique Key Violation, referential errors: particularly anything that doesn't involve people or EdOrgs.​
409The resource (or a subordinate entity of the resource) cannot be deleted because it is a dependency of the 'RESOURCE' entity​​xxx


Technical Information

  • Extracts will run 6:00 PM, Monday - Friday.
  • DO NOT schedule TEA TSDS Level 2 Errors for the first two weeks of the initial data submission.


Initial Data Submission to TEA TCC hosted and managed ESCs:

  • Initial extract and API start will need to be coordinated through a Technical ASD ticket.
    • Submit the Technical ASD ticket the Monday prior to the LEA’s TSDS Parallel initial submission kick-off date.
    • Select the new System Category TSDS Parallel Setup.
    • List the County/District Number and the Name of the LEA participating in the TSDS Parallel Submission.
      • Only one ticket is needed for parallel LEAs starting the initial submission on the same date.
      • All LEA Names and County District Numbers need to be listed in the ticket correctly.
  • The initial data extract/API will begin 3:00 AM, Saturdays.


Self-hosted and managed ESCs:

general/tsds_upgrade.1702484967.txt.gz · Last modified: 2023/12/13 16:29 by apape