Excel Export from React Admin Dashboard Missing Sales Data in XLSX Report

Below are some troubleshooting steps and ideas to help pinpoint why the sales data isn’t appearing in the downloaded Excel report—even though your console logs show the data correctly:

---

1. Verify Data State at Export Time

Although your console logs show the sales data correctly, double‑check that the sales data (i.e. the state or prop that feeds salesData) is not empty at the exact time you call handleExcelDownload. For example, if the data is updated asynchronously or via an API call, it’s possible that the Excel export is triggered before the data is fully loaded.

Suggestion:
Add additional logging (or even a conditional check) to confirm that salesData is not empty when exporting:

JAVASCRIPTCopied
if (!salesData || salesData.length === 0) {
  console.warn("No sales data to export");
  return;
}

---

2. Validate Helper Functions Formatting Values

The helper function you use—formatIndianRupee—should return a string so that XLSX converts the cell values correctly. Verify that the function always returns a valid, non‑empty string.

Example check:

JAVASCRIPTCopied
console.log("Formatted amount:", formatIndianRupee(sale.amount));

---

3. Confirm Sales Data Mapping

Your mapping code for creating the sales rows looks correct. However, verify that the inner mapping for sale products is constructing a valid string. Sometimes issues occur if a product field is not defined.

Check Example:

JAVASCRIPTCopied
const salesRows = salesData.map(sale => {
  const productList = sale.products?.map(p => `${p.name} (${p.quantity})`).join(', ') || '';
  return [
    new Date(sale.date).toLocaleDateString(),
    sale.orderId,
    productList,
    sale.userName,
    formatIndianRupee(sale.amount),
    formatIndianRupee(sale.discount),
    sale.status
  ];
});

This also makes sure you’re handling missing fields gracefully.

---

4. Worksheet Object Structure

When you log the worksheet (salesWS) to the console, note that it is an object with keys for each cell (e.g., A1, B1, etc.) plus metadata (like !cols). Although console output might look confusing, check if the cell keys exist. You could do a quick scan for a known cell (e.g., “A2”) to see if the expected value shows up:

JAVASCRIPTCopied
console.log("Cell A2 Contents:", salesWS['A2'] && salesWS['A2'].v);

If the cells in the sales worksheet have valid values, they should appear in the generated Excel file.

---

5. File Generation and XLSX.writeFile Behavior

If the workbook’s SheetNames log shows both “Summary” and “Sales Details,” then XLSX.writeFile is likely writing the full workbook. Sometimes the library’s interpretation of the sheet data can be affected by cell formatting or the way data is set up. You might try generating the workbook using the binary approach with XLSX.write and creating a Blob for download. This helps rule out issues with XLSX.writeFile in your environment.

Alternative example:

JAVASCRIPTCopied
const wbout = XLSX.write(wb, { bookType: 'xlsx', type: 'binary' });
function s2ab(s) {
  const buf = new ArrayBuffer(s.length);
  const view = new Uint8Array(buf);
  for (let i = 0; i < s.length; i++) {
    view[i] = s.charCodeAt(i) & 0xFF;
  }
  return buf;
}
const blob = new Blob([s2ab(wbout)], { type: 'application/octet-stream' });
const url = URL.createObjectURL(blob);
const a = document.createElement('a');
a.href = url;
a.download = `sales_report_${new Date().toISOString().split('T')[0]}.xlsx`;
document.body.appendChild(a);
a.click();
document.body.removeChild(a);
URL.revokeObjectURL(url);

This lets you check if a different download approach resolves the issue.

---

6. Ensure React and XLSX Integration

Since you’re using React, make sure you’re not interfering with any state updates or rendering logic that might clear salesData before the export. Even if the initial logs are correct, a re-render or state update might affect the export if the function is called at an unexpected time.

---

Summary

• Confirm salesData is populated at the time of export.
• Validate that helper functions (like formatIndianRupee) return valid strings.
• Check that your mapping for salesRows is handling all data correctly.
• Inspect the worksheet object’s cell keys (for example, A1, A2) to confirm that the data appears as expected.
• Try an alternative download method using Blob and XLSX.write to see if that changes the behavior.

Working through these steps should help you narrow down whether the issue lies in the data preparation, the XLSX worksheet creation, or the file download process. If all logs and cell values appear correct but the file still doesn’t show the expected rows, consider creating a minimal reproduction case to isolate the problem further.