You are viewing limited content. For full access, please sign in.

Question

Question

Laserfiche Forms xlsx report erroring with an XML error

asked on March 19

I have a very large report with a significant amount of user data entry. Exports to csv ok, which means we have something to work with, however my users prefer the xlsx exports. When the report is exported it to xlsx, the export opens with the following error.

When you click yes, the following pops up

All strings have been removed from the report with the repair.  I figure the most likely reason is some not supported character has been entered on the form.   I was wondering if I could get a list of characters that aren't supported by the xlsx export process that might cause this error?  Other ideas are appreciated as well.

I tried a different Windows OS, a different version of Excel, different browsers, none made a difference. 

(Modern) Forms Layout Designer, Laserfiche Forms Professional Version 11.0.2311.50553,Microsoft® Excel® for Microsoft 365 MSO (Version 2410 Build 16.0.18129.20200) 32-bit

Thanks!

0 0

Answer

SELECTED ANSWER
replied on March 19

If you wanted to find out what the problematic character is, you can look at that sharedStrings.xml file and check. An xlsx file is actually a zip file containing xml files, so if you open it with a zip tool you can extract the file it's complaining about and see what's in it. There are not a lot of characters that are illegal, at least according to the spec (https://www.w3.org/TR/xml11/#charsets). My guess is that message is referring to a more specific context - i.e. not that the character is totally illegal, just that it's not allowed where it is. Either way, while an xml document has rules about its grammar, it also defines ways of representing characters that can't literally appear in a given context. For instance, you might have seen the escape sequence "&lt;" used to represent the character "<", since "<" has another meaning. So you may have found a bug where some value is being written without being properly encoded. I'd suggest you work with your reseller to open a support case and we can take a closer look.

0 0
replied on March 20

Thank you so much, this tip pointed me the right direction.  The error was in the Strings.xml file and was due to user input.    Ended up being an STX character ( U+0002) from copying text from an Adobe PDF file. 

Has a much larger impact on the form than expected as the variable can't be read past that character.  The form's values can't be edited from the application and the data beyond that character is not shown. 

 

1 0

Replies

replied on March 20

A bug has been filed for this issue  (#582496). Sorry for the inconvenience.

1 0
You are not allowed to follow up in this post.

Sign in to reply to this post.