The following entities are included in the Discipline domain:


Entity: DisciplineIncident

Entity: StudentDisciplineIncidentBehaviorAssociation

Entity: DisciplineAction


Level 1 Errors - Discipline


Most TEA Ed-Fi codes are hard-coded in Aeries and do not need to be mapped.

* An asterisk in the Label & Aeries Table.Field column indicates a code set where local codes can be used. Any local codes used by the district must be mapped to TEA Ed-Fi codes on School Info > Imports and Exports > Ed-Fi Code Mappings


Entity: DisciplineIncident

All Assertive Discipline records for the current school year (Including non-PEIMS incidents) will sync to the IODS.

Element ID
(Code Table)
Data Element NameAeries PageLabel & 
Aeries Table.Field
ReferenceSchoolSee Education Organization domain > School entity
Assertive DisciplineSchool
ADS.SCL
LOC.CC + LOC.DC + ADS.SCL
E1016IncidentIdentifierAssertive DisciplineIncident ID
ADS.IID
E1083 (C190)IncidentLocationAssertive DisciplineLocation
ADS.LCN *
Ed-Fi Descriptor Code Set Mapping: Incident Location Descriptor (ADS.LCN) *

Only Discipline Incidents with a mapped location will sync.
E1734SafeSupportiveSchoolProgramTeamReviewAssertive Discipline (Additional Info tab)SSSP Team Review
ADS.SSP
TRUE if ADS.SSP = Yes; otherwise FALSE
Extracted even if SSSP Team Review Date is blank.



Entity: StudentDisciplineIncidentBehaviorAssociation

All Assertive Discipline records for the current school year with a Violation mapped to a a valid TSDS Behavior Descriptor will sync to the IODS.

Note: Level 1 validation errors will occur for any non-PEIMs reportable codes and will not sync to the IODS.
To avoid these level 1 validation errors for non-PEIMS reportable codes, enter these incidents on the Discipline page.

Element ID
(Code Table)
Data Element NameAeries PageLabel & 
Aeries Table.Field
ReferenceStudentSee Student Identification and Demographics domain > Student entity
ReferenceDisciplineIncidentSee Discipline domain > DisciplineIncident entity (IncidentIdentifier element)
E1006
(C165)
BehaviorAssertive DisciplineViolations
ADS.CD-ADS.CD 5 *


Ed-Fi Descriptor Code Set Mapping: Behavior Descriptor (ADS.CD) *

Map only and all PEIMS reportable violations.

Entity: DisciplineAction

All Administrative Decisions (Dispositions) records for the current school year entered on the Assertive Discipline page and mapped to a valid TSDS Discipline Descriptor code will sync to the IODS.

Level 1 validation errors will occur for the following and will not sync to the IODS :

  • Any non-PEIMs Administrative Decisions (Dispositions) entered on the Assertive Discipline page not mapped to a valid TSDS Discipline Descriptor.
  • Any records where a corresponding StudentDisciplineIncidentBehaviorAssociation record does not already exist for this incident.

(multiple allowed)

Element ID
(Code Table)
Data Element NameAeries PageLabel & 
Aeries Table.Field
ReferenceStudentSee Student Identification and Demographics domain > Student entity
ReferenceStudentDisciplineIncidentBehaviorAssociationSee Discipline domain > StudentDisciplineIncidentBehaviorAssociation entity
E1003
Reference
AssignmentSchoolSchool Options (district)County + District
LOC.CC + LOC.DC
Assertive DisciplineAdministrative Decisions (Dispositions)
School of Disciplinary Assignment
DSP.SA
LOC.CC + LOC.DC + DSP.SA
See Education Organization domain > School entity
E1037
Reference
ResponsibilitySchoolSchool Option (district)County + District
LOC.CC + LOC.DC
Assertive DisciplineSchool
ADS.SCL
LOC.CC + LOC.DC + ADS.SCL
See Education Organization domain > School entity
E1004DisciplineActionIdentifierAssertive DisciplineAdministrative Decisions (Dispositions)
sequence (not displayed)
DSP.SQ
IID_ADS.SQ_DSP.SQ1
E1036DisciplineDateAssertive DisciplineAdministrative Decisions (Dispositions) -
Action Decision Date
DSP.DA
Administrative Decisions (Dispositions) -
Start Date (Served)
DSP.DD
Administrative Decisions (Dispositions) -
Start Date (Assigned)
DSP.IDD
DSP.DA if populated; otherwise
DSP.DD if populated; otherwise
DSP.IDD
  • Must be in current school year.
  • Must not be equal to or greater than September 1 of the next school year.
E1008ActualLengthOfDisciplinaryAssignmentAssertive DisciplineAdministrative Decisions (Dispositions) - 
Days (Served)
DSP.DY
E1005 (C164)Discipline (multiple allowed)Assertive DisciplineAdministrative Decisions (Dispositions) - 
Administrative Decision
DSP.DS *
Ed-Fi Descriptor Code Set Mapping: Discipline Descriptor (DSP.DS) *

Map only ad all PEIMS reportable codes. Any other codes will not load to the IODS will generate a Level 1 descriptor error.
E1007OfficialLengthOfDisciplinaryAssignmentAssertive DisciplineAdministrative Decisions (Dispositions) - 
Days (Assigned)
DSP.IDY
E1009 (C166)DisciplineActionLengthDifferenceReasonAssertive DisciplineAdministrative Decisions (Dispositions) - 
Reason Different
DSP.RDD * 
Ed-Fi Descriptor Code Set Mapping: Discipline Action Length Difference Reason Descriptor (DSP.RDD) *

DSP.RDD if populated; otherwise 00 for No Difference.
E1656InconsistentCodeOfConductAssertive DisciplineAdministrative Decisions (Dispositions) - 
Action Inconsistent With Code of Conduct Policy
DSP.IC
E1725NonMembershipDisciplineRestraintIndicatorAssertive Discipline (Behavioral Emergency Actions tab)Code
BER.CD
1 if BER.CD = anything other than blank; otherwise 0



Level 1 Errors - Discipline


See Also: Ed-Fi - Troubleshooting Errors.


TSDS ErrorRecommendation
Descriptor ErrorsVerify the mappings on the Ed-Fi Code Mappings page.
{message":  "Unable to resolve value " to an existing 'BehaviorDescriptor' resource."}Verify all PEIMS reportable local behavior codes are mapped correctly in the Ed-FI Descriptor Code Set Mapping: Behavior Descriptor (ADS.CD)

Note:  If you record non-PEIMS incidents on the Assertive Discipline page, these records will fail with this error and not sync to the IODS.  To avoid these errors, record non-PEIMS incidents on the Discipline page in Aeries.
{message:  "Validation of 'DisciplineAction' failed. \n\tValidations of 'DisciplineActionStudentDisciplineIncidentBehaviorAssociations' failed.DisciplineActionStudentDisciplineIncidentBehaviorAssociations[0]: BehaviorDescriptorID is required."}This Discipline Incident does not have a record in the StudentDisciplineIncidentBehaviorAssociation entity with a valid TSDS Behavior Descriptor.  
{message: "Validation of 'DisciplineAction' failed. DisciplineActionDisciplines requires at least one object in the collection.}This Discipline Incident does not have a valid Administrative Decisions (Dispositions) mapped to the Code Set:  Discipline Descriptor (DSP.DS) * 
{message:  "The value supplied for the related 'studentDisciplineIncidentBehaviorAssociation' resource does not exist."}The Discipline Action entity is trying to sync an incident that does not have a record in the StudentDisciplineIncidentBehaviorAssociation entity.    

Check for failed records in the StudentDisciplineIncidentBehaviorAssociation entity for this incident and resolve first.

409 CONFLICT

{message: “Access to the resource item could not be authorized because the 'Student' was not found.”}

Verify that student was loaded to ODS.

403 FORBIDDEN

{message: “Authorization denied. No relationships have been established between the caller's education organization id claim (194902) and one or more of the following properties of the resource item: 'SchoolId', 'StudentUniqueId'.”}

Verify that school was loaded to ODS. Then verify that student with that specific Unique Student ID was loaded for that school to ODS.