We have an issue with the export to Excel function, it happens only on the client machines and we are completely unable to reproduce on our side. It's probably also difficult for you to reproduce but, with your in-depth knowledge on how those exports are done internally by the components, maybe you have some ideas.
files included in the zip
- export1.xlsx : generated on my machine (ExportType.WYSIWYG) -> OK
- export2.xlsx : generated on my machine (ExportType.DataAware) -> OK
- export3.xlsx : generated on the client machine (ExportType.WYSIWYG) -> numbers in column 'C' are strings in excel
- export4.xlsx : generated on the client machine (ExportType.DataAware) -> numbers in column 'C' are strings in excel
If you examine the files you will notice the the 'C' column is correctly represented as numeric in files 1 and 2, but they are 'as text' in files 3 and 4. Same problem happens for the date column (B). The 4 exports were made using the same application so it's not like we can change something in the code because it works fine everywhere except for a specific client. We also tried 'playing' with the regional settings of the client's PC but no matter what we do it's always exported as string.
Do you maybe have an idea or some hints that would give us some investigation clues to resolve this annoying issue ? It would be of a great help.
As promised a little update, we finally found out that our client had a very specific option enabled in our application and that was triggering the export to be 'as text' (TextExportMode.Text).
So nothing was wrong with the components or the PC settings, everything works as expected, we just completely forgot about that option and its impact on the 'export to Excel' function.
thanks for the support !