- Home
- Blog
- EDGEBIC How-To
- How to Group a Report Grid by a Column in EDGEBIC
Grouping a report grid in EDGEBIC by User Solutions reorganizes the same rows under collapsible headers with a subtotal per group, turning a long flat list into a summary you can read in one pass. Right-click a column header and choose Group By This Column. Everything else in this task is about choosing the right column and knowing what happens on export.
Every task in this library is mapped on the EDGEBIC how-to hub. To pick the report to group in the first place, start with how to run the work center utilization report.
Before You Start
- The report is open and has returned rows. Grouping an empty grid does nothing visible.
- You know what question you are answering. The right grouping column is the dimension you are about to make a decision about, not the one that happens to be first.
- Nothing else is required. Grouping never changes data, so there is no risk in trying it.
Step 1: Pick the Grouping Column
Ask what the decision is organized around.
| Decision | Group by |
|---|---|
| Which stations are overloaded | Work center |
| Which customers are being let down | Customer |
| Which days went badly | Date |
| Which products keep slipping | Product |
| Which jobs to work first | Status |
Step 2: Group
Right-click the column header and choose Group By This Column.
The grid collapses. Each distinct value becomes a header row with a subtotal, and the detail rows sit underneath. Click a header to expand it.
Step 3: Read the Summary Before the Detail
This is the point of grouping. With everything collapsed you are looking at one line per station, or per customer, or per day, with a subtotal on each. Read that first and find the two or three lines that look wrong.
Then expand only those. Expanding everything immediately puts you back where you started, which is a long flat list.
Step 4: Add a Second Level if You Need It
Drag another column header into the group-by panel above the grid. It becomes the inner level.
Customer then work center gives you a customer summary with a station breakdown inside each customer. Work center then date gives you a station summary with a daily breakdown inside each station.
The order in the panel is the nesting order. Drag the headers around inside the panel to re-nest without rebuilding.
Two levels is usually the practical limit. Three levels of nesting takes as long to read as the flat list it replaced.
Step 5: Combine With Sorting and Filtering
Grouping composes with the grid's other tools.
- Sort inside groups by clicking a detail column header. The groups stay, the rows inside them reorder.
- Filter first, then group when you want a subset summarized. Method in how to filter a report with the filter editor.
Step 6: Decide Before You Export
Exports carry the grouping and the collapsed state. That is useful when you meant it and confusing when you did not.
- Want a summary document? Collapse the groups and export. See how to export a report to PDF.
- Want the detail? Expand before exporting.
- Want a flat table for someone else's analysis? Remove the grouping first, then export to Excel. A grouped spreadsheet is not a data extract.
How to Check It Worked
- Group count matches reality. If grouping by work center produces 30 groups and you have 14 stations, the column carries free text with inconsistent spelling rather than a clean value.
- Subtotals add up. Expand one group and check its rows sum to the header. A mismatch usually means a filter is hiding rows inside the group.
- The total row count is unchanged. Grouping never removes rows. If the count dropped, something else did it.
Common Mistakes
- Grouping on a nearly unique column. Grouping by job number on a job report gives one group per row and no summary at all.
- Expanding everything straight away. The value is in the collapsed read. Expand exceptions only.
- Three or more grouping levels. Nesting that deep is harder to read than the flat list.
- Exporting grouped and calling it a data extract. If the recipient wants to pivot it, send them flat.
See what EDGEBIC reports across a whole plant on the EDGEBIC product page.
Expert Q&A: Deep Dive
Q: The utilization report gives me one row per work center per day and it is 400 rows. How do I make it usable?
A: Group by work center and collapse everything. You go from 400 rows to one line per station with a subtotal, which is the view that actually answers the question you opened the report to ask: which stations are hot. From there expand only the two or three stations that look wrong and read their daily detail. This is the general pattern for every long report in the catalog. Group on the dimension you are making a decision about, collapse, read the summary, then expand the exceptions. Reading 400 rows top to bottom finds the same answer in twenty times the time.
Q: I grouped a report, exported it to Excel, and the recipient says it looks broken. What happened?
A: The export carried the grouping, including the collapsed state, so what landed on their machine is a summary with group header rows rather than the flat table they expected. Two fixes, depending on what they actually need. If they want the summary, tell them it is grouped and to expand it, or use Ungroup All in their spreadsheet to flatten it. If they want the raw table for their own pivot, remove the grouping in the report before exporting and send them a flat file. Deciding that before you export saves a round trip, and it is worth asking, because a summary and a data extract are genuinely different documents.
Frequently Asked Questions
Ready to Transform Your Production Scheduling?
User Solutions has been helping manufacturers optimize their production schedules for over 35 years. One-time license, 5-day implementation.

User Solutions Team
Manufacturing Software Experts
User Solutions has been developing production planning and scheduling software for manufacturers since 1991. Our team combines 35+ years of manufacturing software expertise with deep industry knowledge to help factories optimize their operations.
Share this article
Related Articles
How to Create a Watched-File Integration in EDGEBIC
Create a watched-file integration in EDGEBIC: point it at the file your ERP drops, pick the target entity and import mask, set the debounce, and let a new file trigger the run.
How to Rehearse an Integration With the EDGEBIC Simulator
Use the built-in Simulator to provision demo data, watch real integration runs happen, and prove the mechanism before you point anything at a live ERP. Includes the tear-down rule.
How to Run an Integration Now and Pause All Schedules in EDGEBIC
Force one integration to run with Run Now, cancel a run in progress, disable a single definition, or tick Pause all schedules to stop every automatic sync for the session.
