Troubleshooting Document Templates
Issue |
Resolution |
---|---|
Error when viewing XML file in Internet Explorer: Only one top level element is allowed in an XML document. |
Make sure that the |
Error when viewing XML file in Internet Explorer: A string literal was expected, but no opening quote character was found. |
Search and replace the following string with double quotes in your XML file. Replace \'94 with " |
Error when viewing XML file in Internet Explorer: Reference to undeclared namespace prefix: 'tc'. Error processing resource. |
You have not provided the |
The web browser displays an error saying that the opening tag does not match the close tag. For example, |
If you created your original document in Microsoft Word, it might be because the first tag on the very first line of your document was stored in the Title.
|
When generating the document I get an error message similar to: [*Error in Contact*] |
When converting your document to XML, there may have been some issues that caused extra white space in the file. Review your XML file and make sure the Document Generator tags do not have any spaces or carriage returns inside them. Example #1: Example #2: To resolve this issue find <tc and check for any spaces or carriage returns inside the tag. Remove the spaces that were added while converting to XML so that it is on one line. |
When generating the document I get an error message similar to: [*Error in DetailField: CONT_EMPL/ HireDate*] [*Error in numberString*] |
|
When generating the document I get an error message similar to: No data provided for letter content. |
There is probably a typographical error in your tc:document tag. Make sure the entire tag is typed correctly. For example, make sure that the xmlns attribute value is correct. This message also appears when there are errors in other tags. Make sure that all of your tags are typed correctly. |
When I opened the generated document, tags were replaced by empty data and there were no errors, although there is data that should have been included. What is causing the problem? |
|
I uploaded the template, but when I try to test it by clicking on the Document Generator button, the template is not there. |
|
When I test my document template using Document Generator, the data from custom fields is not being inserted into the document. |
|
How do you find the tree position for custom and system lookup tables? For example tree position for address. |
Each table found in the Lookup Tables screen has its own unique code.
|
When I open the generated document, the RTF source code appears instead of the actual document content. |
This occurs when there is a line return or space after the opening |
When I test my document template using Document Generator, I get a format error similar to: [*Error in format: MMMMM-dd-YY*] |
There is an error in the format that you have provided for a date field. For example, in this error, the Y's for the year are capitalized. Remember that the |
When I test my document template using Document Generator, there is a huge chunk of code directly in the generated document where I used a tag to retrieve data. |
You may have a tc:data tag that is trying to retrieve a data item of the data type "object." An object is not a valid type of data to retrieve in a document template. You may need to continue to navigate, for example, to the name attribute of the object. In Object Model: Read This First or in the reference tables it points to, locate the object attribute and find its data type in the Data Type column. If it is of type "object," then you cannot retrieve it using a tc:data tag. Refer to the object table to which that object attribute links to find the data that you need to retrieve in the document template. |
When I test my document template using Document Generator, I get an error similar to one of the following: [*Error in numberString*] [*Error in parent*] [*Error in name*] |
Notice that all of these errors specify an object attribute. The Document Generator is not recognizing them because the first letter is not capitalized. Make sure that every time you specify an object attribute in a tag, the first letter is capitalized. |
A document is not generated correctly, and other means of troubleshooting fail. |
If the debug level is activated, error information is written to the debug log. You may check this file for details on the problem. |
The document template is generated successfully, but the letter generator hangs after selecting a document template. |
At least one XML template is not well formed.
Here is the syntax and example for end-tag mapping:
|
The XML template is generated successfully and the XML template is well formed, but launching Document Generator results in java.lang.StringIndexOutOfBoundExce ption. |
Open the XML template and check whether element <BASE_TREEPOSITION> or <TREEPOSITION> exists. If either one of them exists in the XML, replace the corresponding <BASE_TREEPOSITION> or <TREEPOSITION> with the appropriate TeamConnect Object Definition unique code or category tree position in the XML template. If you replace the unique code / tree position in the DM file, please use either Data Mapping Tool or EasyDocs Template Generator to regenerate the XML template. If the XML template does not contain either <BASE_TREEPOSITION> or <TREEPOSITION>, please report this issue to TeamConnect support for further assistance. |
Additional Errors and Workarounds
If a line break is encountered in an XML file, in the middle of a token, it may cause an error message to be displayed. To fix the problems you must edit the XML file, removing the incorrect line breaks.
If the token is a merge field name, as shown below:
...then the resulting error message will look like this:
If the token containing the line break is a keyword instead, as shown below:
...then a different set of error messages will be displayed, as shown below: