eDM Error Dictionary

ERROR IDENTIFIER SAMPLE eDM ERROR ERROR DESCRIPTION RESOLUTION STEPS REFERENCE
cvc‐attribute.3 The value '' of attribute 'id' on element Attribute 'id' is invalid. An Attribute type 1) This error occurs in conjunction with error "cvc‐id.2: There are multiple occurrences of ID value.
'XXXXXXXXX' is not valid with respect to its restricts its valid values to follow certain
type, 'ID'. pattern, but an invalid value is being used. 2) This error is due to the value of the of the 'ID' not being valid. The value for ID must be a valid XML
name beginning with a letter and containing alphanumeric characters or the underscore character
without any whitespace. Each value must also must be unique.

In the sample error below, the value is not unique.

<DisciplineIncident id="ID_11111">
<IncidentIdentifier>11111</IncidentIdentifier>
<TX‐CampusIdOfEnrollment>#########</TX‐CampusIdOfEnrollment>
</DisciplineIncident>
<DisciplineIncident id="ID_11111">
<IncidentIdentifier>11112</IncidentIdentifier>
<TX‐CampusIdOfEnrollment>#########</TX‐CampusIdOfEnrollment>
</DisciplineIncident>

3) To locate the errors in the XML file, process it in the TSDS Validation Tool. The Detail Errors will identify
which line(s) in the XML file are in error.

4) To correct the errors, please contact your vendor for support. To assist your vendor, print or export all
errors from the TSDS Validation Tool.

cvc‐complex‐type.2.3 Element 'XXXXXX' cannot have character Element has text content while schema 1) This errors is occurring due to the format of the XML tag.
[children], because the type's content type definition says it must only have element
is element‐only. content. 2) There may be either a double "greater‐than" character or invalid characters at the end of closing tag.
These extra characters are considered as element data.

In the sample error below, invalid characters are shown.

<SchoolType>XXXXXX</SchoolType>>>
or
<SchoolType>XXXXXX</SchoolType>&gt;

3) To locate the errors in the XML file, process it in the TSDS Validation Tool. The Detail Errors will identify
which line(s) in the XML file are in error.

4) To correct the errors, please contact your vendor for support. To assist your vendor, print or export all
errors from the TSDS Validation Tool.

File Manager Errors 1 10/10/2018

 eDM Error Dictionary

ERROR IDENTIFIER SAMPLE eDM ERROR ERROR DESCRIPTION RESOLUTION STEPS REFERENCE
cvc‐complex‐type.2.4.a Invalid content was found starting with Elements or Complex types may be missing 1) This error occurs in conjunction with "cvc‐complex‐type.2.4.b: The content of element 'XXXXX' is not
element 'XXXXX'. One of or out of sequence. complete. One of '{"http://www.tea.state.tx.us/tsds":XXXXX}.'is expected."
'{"http://www.tea.state.tx.us/tsds":XXXXX
X}' is expected. 2) This error is occurring due to a mandatory element or complex type missing or out of sequence from
what is specified in TEDS.

In the sample error below, (E1059) TX‐AmericanIndianAlaskaNative element is missing.

<TX‐Race>
<TX‐Asian>#</TX‐Asian>
<TX‐BlackAfricanAmerican>#</TX‐BlackAfricanAmerican>
<TX‐NativeHawaiianPacificIslander>#</TX‐NativeHawaiianPacificIslander>
<TX‐White>#</TX‐White>
</TX‐Race>

3) TEDS Section 7.x or 8.7.x provides the mandatory elements and/or or complex types by interchange
for the collection.

4) To locate the errors in the XML file, process it in the TSDS Validation Tool. The Detail Errors will identify
which line(s) in the XML file are in error.

5) To correct the errors, please contact your vendor for support. To assist your vendor, print or export all
errors from the TSDS Validation Tool.

cvc‐complex‐type.2.4.b The content of element Elements or Complex types may be 1) This error is occurring due to mandatory elements or complex types being omitted.
'InterchangeStaffAssociation' is not missing.
complete. One of 2) The identified elements or complex types may be one or all of the items listed as being expected.
'{"http://www.tea.state.tx.us/tsds":StaffEd
ucationOrgEmploymentAssociation, In the sample error the InterchangeStaffAssociation' ‐ identifies where the omission occurred,
"http://www.tea.state.tx.us/tsds":Teacher StaffEducationOrgEmploymentAssociation ‐ is identified as a possible omitted mandatory element or
SectionAssociation, complex type, TeacherSectionAssociation ‐ is identified as a possible omitted mandatory element or
"http://www.tea.state.tx.us/tsds":Staff}' is complex type and Staff ‐ is identified as a possible omitted mandatory element or complex type.
expected.
Note: This error can occur when you are using two different source systems for HR and SIS for your
StaffAssociationExtension interchanges and the files were loaded out of sequence. Please refer to the
following for more information:
TSDSKB‐307 TSDS PEIMS: StaffAssociationExtension Interchange files when there are different HR and
SIS vendors.
TSDSKB‐267 studentGPS: StaffAssociationExtension Interchange files when there are different HR and
SIS vendors.

3) TEDS Section 7.x or 8.7.x provides the mandatory element and/or or complex types by interchange for
the collection.

4) To locate the errors in the XML file, process it in the TSDS Validation Tool. The Detail Errors will identify
which line(s) in the XML file are in error.

5) To correct the errors, please contact your vendor for support. To assist your vendor, print or export all
errors from the TSDS Validation Tool.

File Manager Errors 2 10/10/2018

 eDM Error Dictionary

ERROR IDENTIFIER SAMPLE eDM ERROR ERROR DESCRIPTION RESOLUTION STEPS REFERENCE
cvc‐complex‐type.2.4.d Invalid content was found starting with Elements not specified in TEDS for the 1) This error is due to data entered in the XML file not matching what is specified in TEDS.
element 'XXXXXXXXX'. No child element is collection were found in the XML.
expected at this point. 2) This error is occurring due to an unrequested element being added to the complex type.

In the sample error below, (E1078) PK‐PROGRAM‐TYPE‐CODE TX‐PKProgramTypeIndicator is NOT

collected for TSDS PEIMS Summer.

<EducationalOrgIdentity>
<StateOrganizationId>#########</StateOrganizationId>
</EducationalOrgIdentity>
</SchoolReference>
<TX‐GradeLevel>XX</TX‐GradeLevel>
<TX‐Attribution>##</TX‐Attribution>
<TX‐PKProgramTypeIndicator>##</TX‐PKProgramTypeIndicator>
</StudentSchoolAssociation>

3) TEDS Section 7.x or Section 8.7.x provides the mandatory and optional elements for the collection.

4) To locate the errors in the XML file, process it in the TSDS Validation Tool. The Detail Errors will identify
which line(s) in the XML file are in error.

5) To correct the errors, please contact your vendor for support. To assist your vendor, print or export all
errors from the TSDS Validation Tool.

cvc‐complex‐type.3.2.2 cvc‐complex‐type.3.2.2: Attribute Element can have an attribute but the 1) This error is due to the attribute entered in the XML file not matching what is specified for the element
'xsi:schemaLocation' is not allowed to attribute name is invalid. in TEDS.
appear in element
'InterchangeEducationOrganization'. 2)This error is occurring due to the attribute not meeting the case sensitivity requirements.

In the sample error below, attribute InterchangeEducationOrganization is case sensitive.

<Interchangeeducationorganization xsi:schemaLocation="http://www.tea.state.tx.us/tsds
InterchangeEducationOrganizationExtension.xsd" xmlns="http://www.tea.state.tx.us/tsds"
xmlns:xsi="http://www.w3.org/2001/XMLSchema‐instance">

Note: TEDS Section 1 or 8.1 contain the XML File Header Requirements.

3) To locate the errors in the XML file, process it in the TSDS Validation Tool. The Detail Errors will identify
which line(s) in the XML file are in error.

4) To correct the errors, please contact your vendor for support. To assist your vendor, print or export all
errors from the TSDS Validation Tool.

File Manager Errors 3 10/10/2018

 eDM Error Dictionary

ERROR IDENTIFIER SAMPLE eDM ERROR ERROR DESCRIPTION RESOLUTION STEPS REFERENCE
cvc‐complex‐type.4 Attribute 'TelephoneNumberType' must Element must have an attribute and the 1) This error is due to the format of the data entered in the XML file not matching what is specified for
appear on element 'Telephone'. attribute is missing. the element in TEDS.

2)This error is occurring due to the element requiring an attribute and the attribute is missing.

In the sample error below, (E1455) TELEPHONE‐NUMBER‐TYPE (a) TelephoneNumberType is defined as

an attribute.

<Telephone TelephoneNumberType="Home">
<TelephoneNumber>###‐###‐####</TelephoneNumber>
</Telephone>

Note: TEDS Section 7.x or 8.7.x contain a Legend identifying (a) = Attribute

3) To locate the errors in the XML file, process it in the TSDS Validation Tool. The Detail Errors will identify
which line(s) in the XML file are in error.

4) To correct the errors, please contact your vendor for support. To assist your vendor, print or export all
errors from the TSDS Validation Tool.

cvc‐datatype‐valid.1.2.1 ' is not a valid value for 'date'. The value is not the type which is defined 1)This error occurs in conjunction with error cvc‐type.3.1.3: The value '' of element 'XXXXXXXX' is not
for the element. For example a Numeric valid.
value is used when the type is defined as
Coded. 2)This error is occurring due to the element value not meeting what is defined in TEDS.

In the sample error, (E1069) STUDENT‐BEGIN‐DATE BeginDate has the following Data Specifications:

Length = 10
Data Type = Coded
Pattern = yyyy‐mm‐dd
Domain of Values
yyyy = 2016‐2017
mm = 01‐12
dd = 01‐31

However, a 'null' value was submitted.

<BeginDate></BeginDate>

3) To locate the errors in the XML file, process it in the TSDS Validation Tool. The Detail Errors will identify
which line(s) in the XML file are in error.

4) To correct the errors, please contact your vendor for support. To assist your vendor, print or export all
errors from the TSDS Validation Tool.

File Manager Errors 4 10/10/2018

 eDM Error Dictionary

ERROR IDENTIFIER SAMPLE eDM ERROR ERROR DESCRIPTION RESOLUTION STEPS REFERENCE
cvc‐elt.1.a Cannot find the declaration of element The validated file has a namespace which 1)This error is occurring due to the validated file having a namespace which doesn't match the target
'InterchangeStaffAssociation'. doesn't match the target namespace namespace ("targetNamespace") as defined by TEDS.
defined in the schema.
2)TEDS Section 1.0 or 8.1.0 provides XML File Header specifications.

In the sample error below, XML headers are shown.

Incorrect:
xml version="1.0" encoding="utf‐8"?>
<InterchangeStaffAssociation>

Correct:
<?xml version="1.0" encoding="UTF‐8"?>
<InterchangeStaffAssociation xmlns="http://www.tea.state.tx.us/tsds"
xmlns:xsi="http://www.w3.org/2001/XMLSchema‐instance"
xsi:schemaLocation="http://www.tea.state.tx.us/tsds InterchangeStaffAssociationExtension.xsd">
<Staff>

3) To correct the errors, have your vendor reference TEDS Section 1.0 or 8.1.0 for the XML File Header
Requirements. Once corrected reload the XML file.

cvc‐elt.4.3 cvc‐elt.4.3: Type 'GradingPeriod' is not The file has an element with a type that is 1) This error is occurring due to data entered in the XML file not matching what is specified in TEDS.
validly derived from the type definition, not extended (derived) from the base
'CalendarDate', of element 'CalendarDate'. datatype. The type submitted is not 2) In the sample error, the 'xsi:type=""GradingPeriod"" id=""GRDPRD_001Summer_Semester"' is not
defined as an extension for the element as defined as a type in the schema for the CalendarDateExtension complex type in the
defined in TEDS. EducationOrgCalendar interchange:

<CalendarDate xsi:type=""GradingPeriod"" id=""GRDPRD_001Summer_Semester"">

<GradingPeriod>Summer Semester</GradingPeriod>
<BeginDate>YYYY‐MM‐DD</BeginDate>
<EndDate>YYYY‐MM‐DD</EndDate>
<TotalInstrucƟonalDays>#</TotalInstrucƟonalDays>
<CalendarDateReference ref=""CD_###_####SUMMERBEGIN""/>
<CalendarDateReference ref=""CD_###_####SUMMEREND""/>
</CalendarDate>

3) To locate the errors in the XML file, process it in the TSDS Validation Tool. The Detail Errors will identify
which line(s) in the XML file are in error.

4) To correct the errors, please have you vendor refer to TEDS Section 7 or 8.7 for the TEDS Interchange
Schemas. To assist your vendor, print or export all errors from the TSDS Validation Tool.

File Manager Errors 5 10/10/2018

 eDM Error Dictionary

ERROR IDENTIFIER SAMPLE eDM ERROR ERROR DESCRIPTION RESOLUTION STEPS REFERENCE
cvc‐enumeration‐valid: Value '' is not facet‐valid with respect to The value given for the element is not in 1) This error occurs in conjunction with error "cvc‐type.3.1.3: The value '' of element 'XXXXXXXXX' is not
enumeration '[40*, 50*, 60*, 70*, 71*, 00, the Code Table for the element. valid.
01, 02, 08, 30, 31, 31*, 32, 32*, 34, 34*, 40,
41, 42, 43, 44, 45, 50, 60, 70, 71, 81, 82, 83, 2) This error is occurring due to the data element's value not being found in the specified code table in
84, 85, 86, 87, 88, 89, 91, 92, 93, 94, 95, 96, TEDS.
97, 98]'. It must be a value from the
enumeration. In the sample error, valid values for (E0173) INSTRUCTIONALSETTING‐CODE TX‐InstructionalSetting are
in Code Table C035.

<EducationalOrgIdentity>
<StateOrganizationId>######</StateOrganizationId>
</EducationalOrgIdentity>
</EducationOrganizationReference>
<TX‐CampusIdOfEnrollment>#########</TX‐CampusIdOfEnrollment>
<TX‐GradeLevel>XX</TX‐GradeLevel>
<TX‐InstructionalSetting></TX‐InstructionalSetting>
</StudentESYProgramAssociationExtension>

3) To locate the errors in the XML file, process it in the TSDS Validation Tool. The Detail Errors will identify
which line(s) in the XML file are in error.

4) To correct the errors, please contact your vendor for support. To assist your vendor, print or export all
errors from the TSDS Validation Tool.

cvc‐fractionDigits‐valid Value '#.##########' has ## fraction Element value has too many digits in the 1) This error occurs in conjunction with error ""cvc‐type.3.1.3: The value '' of element 'XXXXXX' is not
digits, but the number of fraction digits has fraction part. valid.""
been limited to 2.
2) This error is occurring due to the format of the data entered in the XML file not matching what is
specified for the element in TEDS.

In the sample error, (E1112) CREDIT Credit exceeded the number of decimal places identified in TEDS.

<CreditsAttempted>
<Credit>#.##########</Credit>
</CreditsAttempted>

3) To locate the errors in the XML file, process it in the TSDS Validation Tool. The Detail Errors will identify
which line(s) in the XML file are in error.

4) To correct the errors, please contact your vendor for support. To assist your vendor, print or export all
errors from the TSDS Validation Tool.

File Manager Errors 6 10/10/2018

 eDM Error Dictionary

ERROR IDENTIFIER SAMPLE eDM ERROR ERROR DESCRIPTION RESOLUTION STEPS REFERENCE
cvc‐id.1 There is no ID/IDREF binding for IDREF A corresponding attribute 'id' is not 1) This error is occurring because for every IDREF‐type element there must be a matching ID‐type
'CPER_00'. present for attribute 'ref'. element.

2) This error is occurring due to omitting a required 'id'.

In the sample error below, the ClassPeriod Complex Type is a Reference Type (a) id and the
corresponding Reference Type (a)ref ClassPeriodReference is located in the School Complex Type.

<ClassPeriod id="CPER_0">
<ClassPeriodName>##</ClassPeriodName>
</ClassPeriod>

<School id="SCOL_######‐###">
<StateOrganizationId>#########</StateOrganizationId>
<NameOfInstitution>XXXXXX</NameOfInstitution>
<OrganizationCategories>
<OrganizationCategory>School</OrganizationCategory>
</OrganizationCategories>
<SchoolCategories>
<SchoolCategory>XXXX XXXXXX</SchoolCategory>
</SchoolCategories>
<LocalEducationAgencyReference ref="LID_######"/>
<ClassPeriodReference ref="CPER_0"/>
</School>

3) TEDS Section 7.x or 8.7.x provides the mandatory element and/or complex types by interchange for
the collection.

4) To locate the errors in the XML file, process it in the TSDS Validation Tool. The Detail Errors will identify
which line(s) in the XML file are in error.

5) To correct the errors, please contact your vendor for support. To assist your vendor, print or export all
errors from the TSDS Validation Tool.

File Manager Errors 7 10/10/2018

 eDM Error Dictionary

ERROR IDENTIFIER SAMPLE eDM ERROR ERROR DESCRIPTION RESOLUTION STEPS REFERENCE
cvc‐id.2 There are multiple occurrences of ID value An ID value has been used more than once. 1) This error occurs in conjunction with error "cvc‐attribute.3: The value 'ID_#####' of attribute 'id' on
'ID_#####'. Each instance of reference type attribute element 'xxxxxx' is not valid with respect to its type, 'ID'.
'id' must be unique.
2) This error is occurring due to having duplicate reference IDs. The value for an ID must be a valid XML
name beginning with a letter and containing alphanumeric characters or the underscore character
without any whitespace. Each value must also must be unique.

In the sample error below, duplicates reference ID's are shown.

<DisciplineIncident id="ID_11111">
<IncidentIdentifier>111111</IncidentIdentifier>
<TX‐CampusIdOfEnrollment>#########</TX‐CampusIdOfEnrollment>
</DisciplineIncident>
<DisciplineIncident id="ID_11111">
<IncidentIdentifier>11112</IncidentIdentifier>
<TX‐CampusIdOfEnrollment>#########</TX‐CampusIdOfEnrollment>
</DisciplineIncident>

3) To locate the errors in the XML file, process it in the TSDS Validation Tool. The Detail Errors will identify
which line(s) in the XML file are in error.

4) To correct the errors, please contact your vendor for support. To assist your vendor, print or export all
errors from the TSDS Validation Tool.

cvc‐maxInclusive‐valid Value '###' is not facet‐valid with respect Value given for element is too big 1) This error is occurring due to the value of the element exceeding the maximum allowed as defined by
to maxInclusive '180' for type 'TX‐ compared to allowed maximum value TEDS.
NumberDaysTaught'. defined by TEDS. The value must be less
than or equal to this value. 2) The given value must be less than or equal to the defined maximum value.

In the sample error, the TEDS defined Domain of Values is 001 ‐ 180 for (E0935) NUMBER‐DAYS‐TAUGHT
TX‐NumberDaysTaught.

<TX‐NumberDaysTaught>###</TX‐NumberDaysTaught>

3) TEDS Section 3.x or 8.3.x provides the data specifications for each element.

4) To locate the errors in the XML file, process in the TSDS Validation Tool. The Detail Errors will identify
which line(s) is in the XML file are in error.

5) To correct the errors, please verify the value is correct in your source system, re‐extract the XML and
reload it.

File Manager Errors 8 10/10/2018

 eDM Error Dictionary

ERROR IDENTIFIER SAMPLE eDM ERROR ERROR DESCRIPTION RESOLUTION STEPS REFERENCE
cvc‐maxLength‐valid Value Length of the element value exceeds the 1)This error is occurring due to the length of the element value exceeding the maximum length which is
'XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX maximum length which is defined for the defined by TEDS.
XXXXXXXXXXXXXXXXXXXXXXX' with length element in TEDS.
= '##' is not facet‐valid with respect to 2) In TEDS, the String Length is 50 characters for (E1473) BEHAVIOR‐DESCRIPTOR‐SHORTDESCRIPTION
maxLength '##' for type 'ShortDescription'. ShortDescription.

In the sample error below, the value is not valid due to being 56 characters.

<ShortDescription>XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX</ShortDesc
ription>

3) TEDS Section 3.x or 8.3.x provides the data specifications required for each element.

4) To locate the errors in the XML file, process in the TSDS Validation Tool. The Detail Errors will identify
which line(s) is in the XML file are in error.

5) To correct the errors, please verify the value is correct in your source system, re‐extract the XML and
reload it.

File Manager Errors 9 10/10/2018

 eDM Error Dictionary

ERROR IDENTIFIER SAMPLE eDM ERROR ERROR DESCRIPTION RESOLUTION STEPS REFERENCE
cvc‐minInclusive‐valid Value '#' is not facet‐valid with respect to Element value is less than the allowed 1)This error is occurring due to the element value being less than the allowed minimum value defined by
minInclusive '1' for type 'TX‐ minimum value defined in TEDS. TEDS.
NumberDaysEmployed'.
2) In TEDS, the Domain of Values for (E0160) NUMBER‐DAYS‐EMPLOYED TX‐NumberDaysEmployed is 001
‐ 366.

In the sample error below, '0' is not valid.

<TX‐NumberDaysEmployed>0</TX‐NumberDaysEmployed>

3) TEDS Section 3.x or 8.3.x provides the data specifications required for each element.

4) To locate the errors in the XML file, process in the TSDS Validation Tool. The Detail Errors will identify
which line(s) is in the XML file are in error.

5) To correct the errors, please verify the value is correct in your source system, re‐extract the XML and
reload it.

cvc‐minLength‐valid Value '' with length = 'null' is not facet‐valid Length of the element value is less than 1)This error is occurring due to the length of the element value being less than the minimum length
with respect to minLength '1' for type the minimum length which is defined for defined by TEDS.
'TelephoneNumber'. the element in TEDS.
2) In TEDS, the Numeric Length is 14 characters for (E1269) TELEPHONE‐NUMBER TelephoneNumber

In the sample below the value is not valid due to being 'null' characters.

<Telephone TelephoneNumberType="XXXXX">
<TelephoneNumber></TelephoneNumber>
</Telephone>

3) TEDS Section 3.x or 8.3.x provides the data specifications required for each element.

4) To locate the errors in the XML file, process in the TSDS Validation Tool. The Detail Errors will identify
which line(s) is in the XML file are in error.

5) To correct the errors, please verify the value is correct in your source system, re‐extract the XML and
reload it.

File Manager Errors 10 10/10/2018

 eDM Error Dictionary

ERROR IDENTIFIER SAMPLE eDM ERROR ERROR DESCRIPTION RESOLUTION STEPS REFERENCE
cvc‐pattern‐valid Value '' is not facet‐valid with respect to The content of the element does not 1) This error occurs in conjunction with error "cvc‐type.3.1.3: The value '' of element 'XXXXXX' is not
pattern '[A‐Z0‐9]{1,9}' for type 'XXXXXX'. match the pattern which is defined for the valid."
element in TEDS.
2) This error occurring is due to the format of the data entered for the element not matching what is
specified in TEDS.

In the sample error below, (E0001) STUDENT‐ID IdentificationCode is the student's Social Security
number or a state‐approved alternative identification number and it cannot be blank.

<Student>
<StudentUniqueStateId>###########</StudentUniqueStateId>
<StudentIdentificationCode IdentificationSystem="State">
<IdentificationCode></IdentificationCode>
</StudentIdentificationCode>

3) TEDS Section 3.x or 8.3.x provides the data specifications required for each element.

4) To locate the errors in the XML file, process in the TSDS Validation Tool. The Detail Errors will identify
which line(s) is in the XML file are in error.

5) To correct the errors, please verify the value is correct in your source system, re‐extract the XML and
reload it.

cvc‐type.3.1.2 Element 'NameOfInstitution' is a simple Element contains other elements or 1) This error occurs in conjunction with error "cvc‐type.3.1.3: The value '' of element 'XXXXXX' is not
type, so it must have no element attributes. The schema definition says it valid".
information item [children]. must contain only text.
2) This error is occurring due to the format of the data entered for the element not matching what is
specified in TEDS.

In the sample error below, (E0213) DISTRICT‐NAME is shown containing other elements or attributes.
The schema definition says it must contain only text.

Incorrect:
<NameOfInstitution>
<NameOfInstitution>XXXXXXX</NameOfInstitution>
</NameOfInstitution>

Correct:
<NameOfInstitution>XXXXXXX</NameOfInstitution>

3) To locate the errors in the XML file, process it in the TSDS Validation Tool. The Detail Errors will identify
which line(s) in the XML file are in error.

4) To correct the errors, please contact your vendor for support. To assist your vendor, print or export all
errors from the TSDS Validation Tool.

File Manager Errors 11 10/10/2018

 eDM Error Dictionary

ERROR IDENTIFIER SAMPLE eDM ERROR ERROR DESCRIPTION RESOLUTION STEPS REFERENCE
cvc‐type.3.1.3 The value '' of element 'BeginDate' is not The content of the element does not 1) This error may occur in conjunction with cvc‐datatype‐valid.1.2.1, cvc‐enumeration‐valid, cvc‐
valid. match the element type definition or fractionDigits‐valid, cvc‐pattern‐valid, or cvc‐type.3.1.2 errors.
pattern defined in TEDS.
2) This error is occurring due to the content of the element not matching the element type definition or
pattern defined in TEDS.

In the sample error, (E1069) STUDENT‐BEGIN‐DATE BeginDate is defined as:

Length = 10
Data Type = Coded
Pattern = yyyy‐mm‐dd
Domain of Values:
yyyy = 2016‐2017
mm = 01‐12
dd = 01‐31

'Null' for a value is NOT valid:

<BeginDate></BeginDate>

3) To locate the errors in the XML file, process it in the TSDS Validation Tool. The Detail Errors will identify
which line(s) in the XML file are in error.

4) To correct the errors, please contact your vendor for support. To assist your vendor, print or export all
errors from the TSDS Validation Tool.

failed to validate for inputCode Interchange District Code Validation‐ The file has an element with a type that is 1) This error is occurring due to data entered in the XML file not matching what is specified in TEDS.
FileName not extended (derived) from the base
######_000_2018SUMR1_201801010000_ datatype. The element submitted is not 2) There may be either extra characters or invalid characters in the value.
InterchangeEducationOrganizationExtensio valid as defined in TEDS.
n.xml failed to validate for inputCode: In the sample error below, the E0212 DISTRICT‐ID has invalid characters:
#######
<LocalEducationAgency>
<StateOrganizaƟonId> #######</StateOrganizationId> (7 digits)
<LocaƟon>XXXXXXXXXX</LocaƟon>
<OrganizaƟonCategories>
<OrganizaƟonCategory>Local EducaƟon Agency</OrganizaƟonCategory>
</OrganizaƟonCategories>

3) To locate the errors in the XML file, process it in the File Manager.

4) To correct the errors, please contact your vendor for support.

File Manager Errors 12 10/10/2018