About four lines will be output, and the data at the bottom will be lost. I don't know if it's Chinese. How should I solve it? #2521
Labels
No Label
DBF
Dates
Defined Names
Features
Formula
HTML
Images
Infrastructure
Integration
International
ODS
Operations
Performance
PivotTables
Pro
Protection
Read Bug
SSF
SYLK
Style
Write Bug
good first issue
No Milestone
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: sheetjs/sheetjs#2521
Loading…
Reference in New Issue
Block a user
No description provided.
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
About four lines will be output, and the data at the bottom will be lost. I don't know if it's chinese. How should I solve it?
I don't think it's the code problem. Maybe the problem is in chinese. How can we solve it
its my code
Can you share a more detailed example? Here's a simple demo that appears to export everything: https://jsfiddle.net/5rze96q2/
In case you can't pull it up, it uses https://unpkg.com/xlsx/dist/xlsx.full.min.js (the
dist/xlsx.full.min.js
script) with the following JS code:Sample run: bookmarks.xlsx
i use xlsx.full.min.js in my demo, but still.
like this
Do you have rows that have partial data?
json_to_sheet
will generate a row even if the full data is not available. In your JS code, log the data before converting and be sure the data set is good.i log my data..
data is complete,but even lost two complete data after output.
It's hard to say what is happening, since the generated file actually opens in Excel. Do you see the same problem if you write to
"bookmarks.xls"
or"bookmarks.xlsb"
or"bookmarks.csv"
?xls is fine
That is very weird indeed. Can you share the dataset / XLSX / XLS directly to the org email address (hello@sheetjs.com)?
If not, can you try saving the XLS file, then reading and saving as XLSX:
oh sorry, the data is private. But thank you very much for your help. Thank you.
If you can share the specific row causing issues, or at least some way we can reproduce the issue, it can be reopened.
We pushed an update (0.18.2) which should resolve the issue. Please verify, and sincere apologies for the issue in the first place.