State Reporting

User Tools

Site Tools

Trace: • Course Completion (Extended)
general:tsds_upgrade

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision		Previous revision
general:tsds_upgrade [2023/12/13 16:32] – apapegeneral:tsds_upgrade [2023/12/18 18:51] (current) – apape
Line 58: Line 58:
 \\  \\ 
  
-====Known Issues (as of 11/28/2023)==== +====Known Issues (as of 12/18/2023)==== 
-^----|TCC is aware and is investigating that some TSDS Parallel LEAs are not receiving the nightly extract e-mails.| +^----|TCC is aware and investigating that the extract process is not running for some TSDS Parallel LEAs.  When this occurs, the extract email is not sent and the As-of-Status Last Friday October codes are not updated. API errors that occur are invalid and should not be researched until this is resolved..| 
 ^----|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.| ^----|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-1071|Registration > 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-1071|Registration > 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-1095|When 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.| ^WS-1095|When 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.|  ^----|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 Code^Example Message^How to Fix^ 
-|**400**|Validation 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 ​|​ 
-|**401**|Unauthorized​​|Unauthorized. The request requires authentication. The OAuth bearer token was either not provided or is invalid/expired. ​|​ 
-|**403**|Authorization denied. The claim does not have any established relationships with the requested resource​​|**Likely Causes**:​ \\ 1. Your API credentials are not associated with the proper EducationOrganization or Namespace. See information under the section of this guide on "Authorization".​\\ \\ 2. 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.\\ \\ 3. 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.​|​ 
-|**409**|A 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.​|​ 
-|**409**|The resource (or a subordinate entity of the resource) cannot be deleted because it is a dependency of the 'RESOURCE' entity​​|The resource that the application is attempting to delete is referenced from another entity. Delete the other dependent entity first.​|​ 
- 
- 
-\\ 
- 
  
 ====Technical Information==== ====Technical Information====
general/tsds_upgrade.1702485154.txt.gz · Last modified: 2023/12/13 16:32 by apape

Page Tools

Except where otherwise noted, content on this wiki is licensed under the following license: CC Attribution-Share Alike 4.0 International

Americans with Disabilities Act (ADA) and Web Accessibility

The Texas Computer Cooperative (TCC) is committed to making its websites accessible to all users. It is TCC policy to ensure that new and updated content complies with Web Content Accessibility Guidelines (WCAG) 2.0 Level AA. We welcome comments and suggestions to improve the accessibility of our websites. If the format of any material on our website interferes with your ability to access the information, use this form to leave a comment about the accessibility of our website.