Missing data in csv file after export data from JSON response #3273
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
3 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: sheetjs/sheetjs#3273
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?
NOTE: This is a bug in the Chromium engine (powering Chrome and Edge). SheetJS team members have reported the issue to the Chromium project: https://issues.chromium.org/issues/390568195 . It will take time for the browser vendors to roll out a patch. Some mitigation strategies have been mentioned in this issue thread and in the SheetJS Chat
Hi everyone,
Currently I am having missing data issue after I export the json data into the csv file.
This is the first time it happens. Please refer to picture below:

And the JSON response looks like below:
{"response":"Success","message":[{"HERO_CASE_ID":"H-2501156207","CUST_NAME":"Khairul Fahmi Bin Mohd Faudzi","DESCRIPTION":"Caution Report: br>Issue To Report: Cable Sagging br> br>------Location Information------ br> br>State: Johor br>GPS Latitude: 2.0220670909450544 br>GPS Longitude: 103.3060880871612 br> br>------Problem(s) reported------ br> br>Tegangkan kabel kendur. Jalan tengku mariam kluang. ","HERO_LOGGER":"KHAIRUL FAHMI BIN MOHD FAUDZI","HERO_LOGGER_ID":"TM37246","HERO_STATE":"Johor","AREA_LOCATION":"Johor","CASE_STATUS":"IN-PROGRESS","CASE_TYPE":"Caution Report","VIP":null,"PACKAGE_NAME":"","PRODUCT":"Others","SEGMENT":null,"CASE_OWNER":null,"GROUP_":"CSM HQ","SR_NUM":"1-26653341432","TT_NUM":"1-26653341432","UPDATE_REMARKS":null,"CLOSURE_TYPE":null,"CREATED_DATE":"2025-01-15T15:11:15.000Z","MONTH_YEAR":"January 2025","AGING_CLOSED":null,"CLOSED_DATE":null,"AGING_UNASSIGNED":1,"DATE_UNASSIGNED":"2025-01-16T00:44:50.000Z","AGING_ASSIGNED":0,"ASSIGNED_DATE":"2025-01-16T00:44:50.000Z","AGING_INPROGRESS":0,"INPROGRESS_DATE":"2025-01-16T02:57:14.000Z","AGING_CANCELLED":null,"CANCELLED_DATE":null,"AGING":1,"RATING":0,"FLAG":"COMPLAINT","CKC":"N","CKC_NUM":"","EXT_SYS_REF":"","STAKEHOLDER_REF":"PRODUCT"},{"HERO_CASE_ID":"H-2501151185","CUST_NAME":"Khairul Fahmi Bin Mohd Faudzi","DESCRIPTION":"Caution Report: br>Issue To Report: Cable Sagging br> br>------Location Information------ br> br>State: Johor br>GPS Latitude: 2.04460423390855 br>GPS Longitude: 103.35164082829212 br> br>------Problem(s) reported------ br> br>Tegangkan kabel kendur. Kem batu 3 jalan mersing. ","HERO_LOGGER":"KHAIRUL FAHMI BIN MOHD FAUDZI","HERO_LOGGER_ID":"TM37246","HERO_STATE":"Johor","AREA_LOCATION":"Johor","CASE_STATUS":"IN-PROGRESS","CASE_TYPE":"Caution Report","VIP":null,"PACKAGE_NAME":"","PRODUCT":"Others","SEGMENT":null,"CASE_OWNER":null,"GROUP_":"CSM HQ","SR_NUM":"1-26653468021","TT_NUM":"1-26653468021","UPDATE_REMARKS":null,"CLOSURE_TYPE":null,"CREATED_DATE":"2025-01-15T15:09:54.000Z","MONTH_YEAR":"January 2025","AGING_CLOSED":null,"CLOSED_DATE":null,"AGING_UNASSIGNED":1,"DATE_UNASSIGNED":"2025-01-16T00:22:24.000Z","AGING_ASSIGNED":0,"ASSIGNED_DATE":"2025-01-16T00:22:24.000Z","AGING_INPROGRESS":0,"INPROGRESS_DATE":"2025-01-16T01:06:34.000Z","AGING_CANCELLED":null,"CANCELLED_DATE":null,"AGING":1,"RATING":0,"FLAG":"COMPLAINT","CKC":"N","CKC_NUM":"","EXT_SYS_REF":"","STAKEHOLDER_REF":"PRODUCT"}]
My logic looks like below:
JSON - Excel data mapping and manipulation:
UI Logic
`const getReport = async (type) => {
await DashboardService.dailyReport(enqueueSnackbar, closeSnackbar, token, type).then(res => {
console.log(res.data.message);
Please not that this logic is in React JS project.
@Aiman1017 we have exeactly the same problem, also with exporting to xlsx workbooks. Is it also for you that this error is only happening since a few days/ hours?
Here is a simple smoke test using your data which seems to work correctly (it generates 2 data rows and the header row): https://jsfiddle.net/6v08fyz7/
Code (click to show)
To be sure,
data.message.length
is 2 so the expected number of rows is 3. The actual output is shown below:Result (click to show)
@Aiman1017 @patriksimms At this point, we need more details to determine if there is an issue on the SheetJS side. Please join the SheetJS Chat
@Aiman1017 are you using macOS & chromium based browser by any chance? weirdly it works for us in Safari/ Firefox and also chromium based on linux
@patriksimms Please join the SheetJS Chat and we can try to dig into the details
Thank you for joining the chat and helping diagnose the issue!
This is a Chromium bug.
Reproduction:
This issue seems to be sensitive to the number of properties in the object
We will reopen this issue and re-close once Google fixes the bug.
This issue has been reported to Chromium: https://issues.chromium.org/issues/390568195
In the interim, force dense-mode worksheets by passing
dense: true
tojson_to_sheet
orread
or other methods.Hello there Sheetjs Team,
Noted but I have solved the issue by moving the logic from Front-end portal to the Back-end server to resolved this issue as a temporary workaround.
When I am free, I'll try to add the "dense" property in my testing.