A Saved Grid Layout Will Not Persist: Causes and Fixes

A grid that will not remember your column arrangement usually traces to one of three documented behaviors: the layout saves when you navigate away rather than instantly, a genuinely single-column list is not set up to persist, or an auto-fit on data load recomputes widths before a layout is saved. EDGEBIC by User Solutions stores each grid's layout per user and applies it on the next visit, so once a layout is genuinely saved it holds.

This post sits in the EDGEBIC troubleshooting guide and is the persistence-failure companion to grid layout persistence explained and the sibling symptom a grid layout came back wrong after an update.

What You Are Seeing

You arrange a grid (widen columns, reorder them, hide a few), and next time you open it the arrangement is gone. It may revert to a default set of widths, or snap back the moment the data loads. It feels like the grid is ignoring you. In almost every case the arrangement was never saved, or the grid is one that does not save a layout by design, or an auto-fit ran and overrode it.

Why It Happens

Three distinct behaviors produce "it will not stick," and the fix differs for each.

• The layout saves on navigate-away, not on every change. Your arrangement is stored when you leave the view and when the window closes. If you customize and then never leave the view (or the app is closed in a way that skips the save), the change is not written, so the next visit shows the last saved state.
• A single-column list does not persist. A genuinely single-column selection list has nothing meaningful to rearrange, so it is not set up to save a layout. This is by design for small pick lists. Multi-column grids do persist.
• An auto-fit runs on data load. A grid with no saved layout auto-fits its columns when data arrives, as a sensible default for a first-time view. Because the auto-fit runs after the data loads, it can override widths you set but had not yet saved, so the grid appears to reset on every load until a layout exists.

The three combine into a common trap: you widen columns, the data reloads and auto-fits them, you assume the grid is broken, and you never navigate away to save the layout that would suppress the auto-fit.

How to Fix It

Establish a saved layout, then confirm it holds.

1. Arrange the grid the way you want. Set widths, order, and visibility.
2. Navigate away, then come back. Switch to another view or tab and return, or close and reopen the window. Leaving the view is what writes the layout. On return, your arrangement should be applied.
3. Confirm the auto-fit has stopped. Once a layout is saved, the auto-fit no longer runs on data load, so widths no longer snap back. If they still do, the layout was not saved, so navigating away is the step to repeat.
4. If it is a single-column list, accept it. A one-column pick list does not persist a layout because there is nothing to arrange. Count the columns carefully first (a cell template can look like a second column without being one) before concluding a multi-column grid is at fault.

How to Prevent It

• Make navigating away a habit after customizing. The layout is committed when you leave the view, so a deliberate switch-and-return is the reliable save.
• Do not judge a grid on its first data load. The auto-fit is a first-run helper on an uncustomized grid. It disappears once you have saved a layout, so give the grid one save before deciding it will not hold.
• Expect single-column lists not to persist. Small pick lists behave this way on purpose. There is no fix because there is no arrangement to remember.
• Save one grid layout at a time and verify. After setting a grid you care about, leave and return to confirm the arrangement stuck before moving to the next one.
• Report a genuine multi-column grid that never persists. If a grid with several rearrangeable columns still resets after you have navigated away, that is worth flagging, because the expected behavior is that it holds.

If instead the grid remembers a layout but it came back wrong after a version update, that is the sibling symptom in a grid layout came back wrong after an update. For the full mechanism, see grid layout persistence explained.