Gigasheet buying guide: Exclude test runs before finding machines over the downtime limit
Separate excluded records from the threshold applied per machine so several short stops are not missed.
Gigasheet suits teams that interactively inspect large tables and revisit details by category. Its official example distinguishes filtering raw rows from filtering grouped totals. Its aggregation guide says rows removed by a row filter are excluded from totals. To find accumulated short stops, not one unusually long stop, do not swap the two rules.
Five rows are enough to check both rules
At a fictional print shop, machine A has production stops of 5 and 4 minutes and a test-run stop of 20. B has a production stop of 8. C has only a test-run stop of 12. We want machines with total production downtime strictly greater than 8. Exclude test runs and sum by machine. A has 9, B has 8 and C has no eligible rows, so only A passes.
On paper, the report must show A’s 9 minutes and trace them to the 5- and 4-minute rows. Filtering raw rows for more than 8 drops both short stops. Including test runs in totals lets C through. Using greater than or equal includes B incorrectly. Check all three, not just the final list.
When not to migrate
For a small table with stable definitions and a pivot table that preserves details, keep your current tool. For auditable handoffs, record the row conditions, grouping field, aggregation and cutoff separately. Do not transfer real production records before checking the environment and access policy.
Content note:This article is based on publicly available information and is intended as a reference for evaluating tools. Features, pricing, and related policies may change at any time; please refer to the latest official information.
Original source:www.gigasheet.com