Table - download as excel produces corrupted file when there are number columns

[radiant hull]

We find that any table that has a numeric column will produce an excel file that when opened in Excel produces an error message regarding recovery of the file. This error is already documented here: https://github.com/appsmithorg/appsmith/issues/22206

But what I'm reporting happens when using the Table's builtin download button.

If we change the column type in the Table's column's properties to Plain Text, the file is created correctly. But this then breaks sorting of numeric columns (and maybe filtering?).

[olive matrix]

Hello, I'm AppySmith, your support bot here to assist you with Appsmith platform
issues! It seems like you're experiencing an issue where exporting tables with
numeric columns to Excel using Appsmith's built-in download button generates a
file that causes Excel to display an error about file recovery. You've found
that changing the column type to Plain Text alleviates the issue but affects
sorting and filtering of numeric columns. This might be related to how the data
is being interpreted and formatted during the export process, possibly causing
Excel to struggle with correctly parsing the data types. Since this seems to be
a known issue, as you've linked to the GitHub issue tracker, the development
team should be aware of it and actively working on a fix. However, as a
temporary workaround, you can consider the following steps: 1. Use plain text
for the export but convert columns in the Excel file back to numbers if needed
for sorting. 2. Implement a custom export button using JavaScript that formats
the data correctly. 3. Retrieve the data via an API call and use an external
script or tool to generate the Excel file with proper formatting. In the
meantime, I would recommend keeping track of the issue on the GitHub repository
for any updates or fixes from the Appsmith team. If you have further details
that could help, consider adding a comment to the GitHub issue to aid in
troubleshooting. If none of these options work for you, please let me know so
that we can look further into your issue. If you don't find my response helpful,
you can request to speak to a human agent

[olive matrix]

Hello! I'm Amelia with Appsmith Support. 👋
Thank you for reporting this issue. If you click "Yes" to repair the Excel file
after opening it, does it open correctly?

[radiant hull]

yes it does, but users many times assume there is an error with the app.

[olive matrix]

I understand that the issue with Excel exports can create confusion for users
and lead to assumptions that there is a deeper problem with the app. Assuring
users of data integrity while this issue is being addressed is important. You
can do the following to help mitigate the situation: - Inform users of the known
issue and that the development team at Appsmith is working to resolve it,
linking to the GitHub issue for transparency. - Provide users with instructions
or automated tools to correct the Excel file after download if they encounter
the error. - Consider disabling the export feature temporarily if it leads to
significant confusion, directing users to alternative methods for data
retrieval. If this issue is critical for your application's operations and the
above solutions are not satisfactory, it might be beneficial to look at
alternative interim solutions such as using a different data exporting library
or service until the issue is resolved. Meanwhile, it's best practice to monitor
updates from the Appsmith team regarding bug fixes. If you're able to contribute
further details or scenarios that cause this issue to the GitHub issue
discussion, this could help speed up the resolution. Should you require
immediate assistance or if this situation is causing significant trouble, please
let us know so that we can escalate this concern to a human colleague. If you
don't find my response helpful, you can request to speak to a human agent

[radiant hull]

I feel this is damaging to the reputation of appsmith in an org. It may seem like a small thing but the fact that every excel file downloaded from the table widget errors out in Excel is not a good look. The only way out of this really I feel is disabling that functionality and creating another button just for that.

[olive matrix]

The concern you're raising about the impact on Appsmith's reputation within your
organization due to this issue with Excel file exporting is completely valid.
First impressions and reliability are crucial for user trust. Here is a
suggested course of action to mitigate the issue: 1. You can disable the
built-in download button within the table widget settings to prevent users from
using a feature that leads to errors. 2. Implement a custom download button near
the table widget. This button can trigger a custom JavaScript function that
properly formats the data and uses a reliable library to create the Excel file.
3. Communicate with your users about the change and the reason behind it.
Transparency about bug fixes and workarounds can often mitigate frustration. By
taking these steps, you ensure uninterrupted functionality for your users until
the Appsmith team rolls out a fix for the issue. It also demonstrates a
proactive approach to maintaining the quality of the application experience. If
you need guidance on implementing the custom download functionality or any other
support, please let me know and I’d be happy to assist you further. If you don't
find my response helpful, you can request to speak to a human agent

[radiant hull]

I have added a comment to the github issue.

[olive matrix]

That's great to hear that you've added a comment on the GitHub issue. By
contributing to the issue tracking, you're not only helping the Appsmith team
prioritize and understand the problem better, but also informing others who may
face the same issue that they're not alone and that it's being looked into. Now
that you've disabled the built-in download button and are considering a
workaround, you might need to implement a custom button that uses JavaScript or
a server-side script to generate and download the Excel file. Would you like
assistance in creating a custom solution for downloading the table data, or do
you require any further support based on the steps you've taken so far? If so,
please let me know what specific help you need. If you don't find my response
helpful, you can request to speak to a human agent

Thank you for your continuous support and patience. Indeed, this is a poor user
experience. Thank you for adding the comment.
You can track the GitHub issue that addresses the matter further. Our
development team will be taking over from here.

We value your feedback and would appreciate hearing about your experience with
our support team.
https://survey.frontapp.com/v2/09a400bf433bc9676d67/b87057a46ab68f05f57a9aaf953a5ac1

[exotic moat]

probalby releated to https://github.com/appsmithorg/appsmith/issues/21075

[olive matrix]

It seems you suspect that the Excel export issue is related to another existing
issue on the GitHub repository. The best approach in these cases is to comment
on both issues indicating the potential connection. This information could be
valuable for the developers to understand the broader context and might help in
diagnosing the root cause of the problem. It's possible they may realize the two
issues might be symptoms of a single underlying problem. If the issues are
indeed related, linking them can help consolidate efforts to troubleshoot and
resolve them more effectively. If you've not done so already, I would suggest
posting a comment on the issue you believe it might be related to, including a
link to the other issue and describing why you think they are connected. Would
you like any other support with this matter or anything else related to
Appsmith? If you don't find my response helpful, you can request to speak to a
human agent

[radiant hull]

Hey. It doesn't seem to be the same issue. If I let excel repair the file it opens with the correct data in it.

[exotic moat]

My original issue was that the column header AND the data would all be zero if the column type was numeric (int,float,etc). Then (and still) just the header is zero, but the data is fine. Export to csv or change the field type to "varchar" and it works as intended. Might not be the exact same issue but it's still related to the field type being defined as numeric. I mentioned it so they don't break something trying to fix your reported issue.