Recently we had a case in customer support, ticket #CS0724010. The problem was that a user copied and pasted an unsupported character into a text box. This led to two problems:

1. The unsupported character was allowed to be entered and subsequently caused the report form to throw an error instead of printing (attachments 1, 2).

We propose either disallowing characters that would cause errors when printing or changing the unprintable character to some default character when printing, so that the report can still mostly be viewed.

2. The error reporting for this error changed from how errors have previously been reported, (printing the FEID of the field with the problem) and now reports the location of the error on the report form (Line and Position rather than FEID). We do not like this change- it is harder to track down these kinds of errors when the error summary reports this way (Attachments 1, 3).

We (NJDOT) spoke to Robert and Anup at our monthly meeting about the error reporting, and we're collectively not sure if this change affects all errors or just errors of this type. At Robert's direction we reposted a summary here.