XML Messages
The following table lists compliance errors for XML-specific messages:
| Message Number | Message Type | Message Generated |
|---|---|---|
| 610 | Error | XMLParticleORGroupError |
| 690 | Error | XMLParserError |
| 691 | Error | XMLElementUnknown |
| 692 | Error | XMLPcDataUnknown |
| 693 | Error | XMLAttributeUnknown |
| 10060 | Information | PublicId |
| 10061 | Information | SystemId |
| 10062 | Information | LineNumber |
| 10063 | Information | ColumnNumber |
| 10064 | Information | Message |
| 10065 | Information | XMLTagName |
| 10066 | Information | XMLNamespaceURI |
The cerror function can also be used with SWIFTNet to allow it to be called with only a code and description string (instead of code, field reference, option description string). You typically specify this function as an action to be performed if a condition is false. This function is valid on the input side of a map only. There is also an optional third parameter you can supply—a string which is written to the translator report as part of the entry for the compliance error you are raising.
Syntax 1
cerror(code,$GROUPNAME[0][1][1].#FIELDNAME, "Optional string with error
information can be supplied here");
Example 1
An example of this function in this syntax follows:
cerror(100,$GROUPNAME[0][1][1].#FIELDNAME);
//This raises compliance error 100 on the FIELDNAME field of the
//specified instance of the GROUPNAME group. There is no optional error text
//given.
Syntax 2
cerror(code, "String with error information supplied here");
Example 2
An example of this function in this syntax follows:
cerror(100, “Number not valid”);
//This raises compliance error 100 with error text “Number not valid” in the
//translator report.