- Knowledgebase
- XML Schema
- Content
-
Glossary
-
XML / ISO 20022 Standard
-
ISO 20022 Messages
-
XML Schema
- Miscellaneous
- Attribute
- Closing Tag
- Comment
- Content
- Cvc-complex-type
- Cvc-elt
- Cvc-id
- Cvc-identity-constraint
- Cvc-minexclusive-valid
- Cvc-mininclusive-valid
- Cvc-type
- Cvc-totaldigits-valid
- Cvc-attribute
- Cvc-datatype-valid
- Maximum Length
- Cvc-enumeration-valid
- Cvc-fractiondigits-valid
- Cvc-length-valid
- Cvc-maxexclusive-valid
- Cvc-maxinclusive-valid
- Cvc-maxlength-valid
- Cvc-minlength-valid
- Cvc-pattern-valid
- Element Value
- Encoding
- Length
- Mandatory element
- Missing
- Missing Tag
- Missing Child Element
- MIXD
- Root
- Unsupported Characters
- UTF-8
- Value
- Wrong Declaration
-
EPC SEPA
-
CGI-MP
-
US ACH (Nacha)
-
SWIFT MT
-
Finvoice
-
Bank-Specific
-
XMLdation Service Guides
-
Studio Guide
-
Simulator
1843
There are at least two causes for this error: 1: The XML document has content outside of tags and it is defined by the schema that only elements are allowed. 2: Value is given inside complex type element
Notice! This page describes the nature of the error using a hypothetical example and not the erroneous data of the input test file. You should however be able to apply this information to your error case.
Error description:
There are at least two causes for this error:
1: The XML document has content outside of tags and it is defined by the schema that only elements are allowed.
2: Value is given inside complex type element
Example of case 1:
<email>
Hello Mr. <to>Andersson</to>
How is your <system>Matrix</system> doing?
Sincerely Yours, <from>Agent Smith</from>
</email>
would produce this error. (It is possible to use XML this way and even validate it by XML schemas by setting complextype attribute mixed="true" but bank materials do not support this.)
You can add extra content to files by using comments. For example:
<!-- Here is an email -->
<email>
<to>user'at'mail.eu</to> <!-- email address here -->
<subject>Hello</subject> <!-- remember to use describing subject -->
</email>
Example of case 2:
For example
Correct way in this case would be to give the value inside <Id> element instead of giving it directly inside the <Othr> element.
Screenshot of schema for reference:
Explanation of the error message given by the validator:
"Element 'elem1': Character content other than whitespace is not allowed because the content type is 'element-only'."
Where elem1 is the element which has content outside of tags and produces the error.