SelfServ (Troubleshooting)
      Back to home
      1. ParsePort - Knowledge Base
      2. SelfServ (Troubleshooting)

      Error: Conversion Errors (linked to TextSearch - Areas)

      • Error location 

      This error message is located in Conversion Errors:


      The Conversion Errors also triggers:

      • Import Errors Warning 
      • Taxonomypackage Check errors
      • xHTML Check errors 

      Fixing the Conversion Errors first will clear the rest of the errors connected to them.

      • Error explanation

      This type of error comes from an issue in your TextSearch Areas setup.

      If the first error message in the Conversion Errors list starts with one of your Area names (e.g. All Notes, Note 1, Note 4.1, …) then one (or more) of the Areas you set up in the Areas tab of the Excel file is not found by the system. 

      Additionally, all Note tagging elements associated with this Area/s will also cause error and warning messages. 

      For this reason, you should always fix the Areas first, starting from the top of the Conversion error list. 

      Note: If the first error message in the Conversion Errors list starts with an element name (e.g. Disclosure of … / Description of..), then the issue comes from the Notes sheet of the Excel file - please refer to this article. 

      • How to solve it

      Find which Area is causing the issue - if there are more than one areas in your Conversion Errors list, start with the first one. Fixing one issue will often resolve most of the subsequent issues, so always start with the first one!



      Here are four possible solutions: 

      a) The Excel file and the PDF/EPUB should match 100%

      Make sure that the Area name in the Excel file matches the PDF/EPUB 100%. Be careful of typos, accents/special characters,... 


      In the example below, there is an additional “s” in the Excel file - removing the “s” will solve the issue.

      b) There might be graphical issues in your PDF

      If your Excel file and the PDF match 100%, but you are still experiencing this error, there might be some characters that are not recognised during conversion. 

      If you also have the warning below, please refer to this article and solve these graphical issues first. 


      c) The start and end text is not included in the 'IN' area - 'Note 4' in this example

      The text used to define Note 4.1 is not present in Note 4. Make sure your Areas are defined correctly. If you are unsure on how to do this, please refer to the TextSearch Tagging Method article.


      d) The area tags (area://text) are not set up correctly in the PDF

      Make sure that Area tags (area://text links) have been correctly set up in the PDF.


      Additional tips:

      1. All text included in the Areas sheet should be covered by the link area://text in the PDF. 
      2. Area tags should be applied in the order of human reading, especially if the layout of your report is in columns.
      3. Do not include non-taggable information such as headers/footers/page numbers in the Area tags.
      4. Do not include repeated titles - e.g. 2. Accounting Policies (cont’d) in the Area tags.