A report fails when you run it over an older date range

Summary: A report that works for recent dates but errors over an older or wider range is usually tripping on one incomplete shipment in that range. Find that record, void it, and the report runs.

Problem

A shipment report runs fine for recent dates, but when you extend the date range further back it errors and will not return results.

Cause

One shipment record in the older part of the range is incomplete: it has no ship-to address and no package weight or dimensions. This is usually an order that was started but never finished or voided. The report cannot build that row, so it errors for the whole range. Removing that one record clears the error.

Fix

Narrow the date range a little at a time to find the smaller range that triggers the error. The boundary date tells you about when the bad record was created.
In that range, find the shipment record that has no ship-to address and no weight or dimensions.
Void that record.
Run the report again for the full date range. It should now finish.
If you cannot find or void the record, email support@shipstore.com with the date range that errors.

What you should see

After you void the incomplete record, the report runs for the full date range without an error, and that record no longer appears in the output.

Build a shipment report: station filter, LTL counts, blank ship-to
A CSV report has no column headers

Knowledge Base