An Exported Spreadsheet Was Missing Rows or Columns: Why, and the Fix

A grid export in EDGEBIC is a snapshot of the grid exactly as displayed, not a dump of the full underlying record set, so a hidden column, an active filter, or a collapsed group carries straight into the file and shows up as missing rows or columns. EDGEBIC by User Solutions exports what you are looking at, which means the fix is to make the grid complete before you press export.

This post is part of the EDGEBIC troubleshooting guide and pairs with how to export a report to Excel and the wider question of what is production scheduling.

What You Are Seeing

You exported a grid to Excel or CSV (the Job View, a work center report, a schedule grid), opened the file, and found it short. Columns your planner relies on are absent, or whole blocks of rows are missing. On screen the data looked right, but the file does not match. The export appears to have dropped part of the data on the way out.

Why It Happens

The export copies the grid, not the database behind it, and the grid is whatever you have arranged.

• It is a snapshot as displayed. A grid export produces the grid as it appears at the moment you export: the columns shown, in their current order and widths, and the rows currently visible. It is deliberately not a full extract of every field on every record.
• Hidden columns are absent. Any column you hid, or that another user hid in a shared layout, is not in the file. Columns folded into a group header rather than shown as real columns also do not appear as their own columns.
• Filtered rows are absent. An active filter removes rows from the display, and the export mirrors the display, so those rows are absent from the file too. Filter to one status and export, and only that status lands.
• Collapsed groups hide their rows. If the grid is grouped and some groups are collapsed, the rows inside them are not shown, so they do not export.

None of this is the export malfunctioning. It is the export faithfully reproducing a grid that was showing less than the whole set.

How to Fix It

Make the grid show everything you want, then export.

1. Clear the filter. Remove any active filter so all rows are visible. If you meant to export only a subset, leave the filter and know that the file will match that subset.
2. Unhide the columns you need. Bring back any hidden columns and confirm the ones you want are shown as real columns, not tucked into a grouping row.
3. Expand collapsed groups. If the grid is grouped, expand the groups so their rows are displayed and therefore exported.
4. Export and verify. Run the export and open the file. Row and column counts should match the on-screen grid. If they still do not, a filter or a hidden column is still in place.

How to Prevent It

• Set the grid before you export, every time. Treat clearing filters and unhiding columns as the step before export, so the file always reflects the full set you intend to share.
• Agree on a shared layout for recurring exports. When several people export the same grid, save and share one layout so everyone's file has the same columns. Grid layouts persist per control, so a shared arrangement stays put.
• Decide filtered or full on purpose. Sometimes you want exactly the subset on screen, and the snapshot behavior is a feature. Just be deliberate about whether a filter is meant to be there.
• Check counts against the screen. A quick glance that the exported row and column counts match the grid catches a stray filter before the file leaves your hands.

For sending a committed plan onward to another system, the mask-based path is described in exporting the EDGEBIC schedule back to your ERP, which is a different route from a grid snapshot. If instead a saved grid layout keeps reverting, that is covered in a saved grid layout will not persist.