Back to the FAQ

We are running into an error about XML files containing invalid (hexadecimal) characters. What can we do about this? (NAV)

By pasting invalid data in the old Microsoft Dynamics NAV Windows client, it is possible to paste unprintable characters which should not be there. When fields containing these invalid characters are used in reports, then this might raise the following error during XML validation of the dataset:

A call to DocumentCreator.<MethodName> failed with this message: hexadecimal value <character>, is an invalid character. Line: <line no.>, position: <position no.>

You need to clean up the data in the table fields that contain invalid, unprintable characters, to prevent further issues in external systems and APIs that use these fields. By checking the contents of the XML dataset file on the specified position, you can pin down which field(s) contain(s) the error.

FAQ categories

Narrow down your search
  1. Show all
  2. Custom Fields
  3. Document Archive
  4. Document Creator
  5. Document Mail Queue
  6. General
  7. Inventory Availability Indicators
  8. Licensing/Subscriptions
  9. PDF Merge
  10. Price and Item Management

Related questions

We run into an error that says “A task was canceled.”. What can we do about this? (On-Premise) The designer does not start anymore after reconfiguring my PC. What can I do to resolve this? How can we add Item pictures to our document layouts? Can we put Document Creator report layouts under source control? How to add the “Work Description” field as text to my layout?
Copyright © 2024 Apportunix | Terms & Conditions | Privacy