EDGEBIC Grid Layout Persistence Explained: Your Columns, Remembered

EDGEBIC by User Solutions saves each user's column layout on every data grid, the visible columns, their order, their widths, and the sorting, automatically restoring it the next time you open that grid, while still surfacing any column added in a later version. It is the kind of feature nobody notices when it works and everybody resents when it does not. Arranging a grid for your job and finding it exactly as you left it, every time, is a small thing that compounds across a plant of daily users into real trust in the software.

This is plumbing that runs under every tabular surface, from the schedule grids to the reports catalog. Understanding how it behaves, and the two traps it deliberately avoids, explains why the screens feel stable rather than fighting you.

What Gets Saved, and When

On any grid, EDGEBIC remembers the arrangement: which columns are showing, the order they sit in, how wide each one is, and the sort you applied. That layout is written automatically at the natural boundaries, when you navigate away from the grid and when you close the program, so you never have to think about saving it. Open the grid again and your arrangement is back.

Two scoping rules keep it sane. The layout is per user, so the way you arrange a grid does not overwrite how a colleague arranged theirs. And it is per grid, so the columns you set on the schedule do not bleed into the columns on a report. Your setup is yours, and each screen keeps its own.

Layout, Not Data

A crucial distinction: only the layout is persisted, never the numbers. Every grid and report queries the database fresh when it opens, and the layout is drawn over today's data. Restoring a saved arrangement brings back your columns, not a stale snapshot of yesterday's figures.

This is why layout persistence and the point-in-time nature of the reports coexist cleanly. The reports are always current; your view of them is always yours. The reports overview covers the point-in-time behavior; layout persistence is the reason your customized view of each report survives the refresh.

The Trap It Avoids: Hiding New Columns

The obvious way to build this feature is also wrong, and worth understanding because avoiding it is most of the value. If a saved layout were simply restored wholesale over the current grid, then a column added in a later version would be governed by an old saved layout that never mentioned it, and so it would be hidden. The users who never customized would see the new column; the users who did, your most engaged people, would not. New capabilities would reach exactly the wrong audience.

EDGEBIC reconciles instead of replacing. When it restores your layout, it matches your saved arrangement against the current set of columns: a column you rearranged keeps your width and position, and a column that is genuinely new still appears. You keep your customization and you get the new feature. There is no choice to make between the two.

The Other Trap: Colliding Grids

The second failure mode is subtler. Every grid needs a unique key under which its layout is stored. If two different grids accidentally shared a key, one would silently overwrite the other, and the symptom, a grid showing the wrong columns, would appear nowhere near the cause. EDGEBIC keeps a unique key per grid precisely so that never happens, which is why you never see one screen's layout leak onto another.

These two traps are why a feature that looks trivial is built with care. The difference between a plant that trusts its screens and one that fights them often comes down to exactly this kind of invisible correctness.

Where It Helps Most

Layout persistence pays off wherever a user returns to the same grid daily with a specific job in mind. A planner who works the schedule grid arranges it once for their workflow and never re-does it. A supervisor who lives in a work center schedule view keeps their columns. A cost analyst who reads earned value pins the columns that matter to them. Each person shapes the software to their role, once, and the software holds the shape.

For a stable everyday arrangement it is ideal. For occasional different lenses, the reports carry their own filters and export, so a special pull becomes a PDF you keep rather than a layout you have to juggle.

Where It Fits

This is a usability layer under the whole product rather than a feature you open. You experience it as the absence of friction: grids that stay arranged, new columns that still arrive, no cross-contamination between screens. For the wider system it quietly supports, the complete EDGEBIC guide is the map, and the self-explaining reports show a related idea, that every column also carries its own definition so a remembered column is also an explained one.

The Point of Remembering

Software that forgets your setup taxes you every session and teaches you not to bother customizing it, which means it never fits your work. Software that remembers, and that keeps remembering correctly as it grows new columns, earns the small daily trust that makes people actually use it. Layout persistence is a modest feature carrying an outsized share of that trust.

Want to see the grids arrange themselves to your team's roles? Bring an export to a demo and set one up your way.