[data grid] apiRef restoreState and exportState does not support the density

[vakha30]

Duplicates

• I have searched the existing issues

Latest version

• I have tested the latest version

Current behavior 😯

The density state is not saved. All other state is saved correctly

Expected behavior 🤔

No response

Steps to reproduce 🕹

Steps:

Context 🔦

No response

Your environment 🌎

`npx @mui/envinfo`

  Don't forget to mention which browser you used.
  Output from `npx @mui/envinfo` goes here.

Order ID 💳 (optional)

No response

[flaviendelangle]

Do you mean it is not saved when using apiRef.current.exportState ?
If so, yes we did not add it yet

[vakha30]

Yes, I meant it. Thanks

[github-actions]

Since the issue is missing key information, and has been inactive for 7 days, it has been automatically closed.
If you wish to see the issue reopened, please provide the missing information.

[flaviendelangle]

Oops forgot to remove the label

[ithrforu]

Hello, @flaviendelangle, i have the same problem. Do you know when density will be supported in apiRef.current.exportState? Thank you :)

[vaclav-slavik]

Hello, @flaviendelangle, i have the same problem. Do you know when density will be supported in apiRef.current.exportState? Thank you :)

Plus one. At the meantime, I'm using workaround (storing the user selected density separate from the rest of the datagrid state), but it would be great to have the support for it in the exportState and restoreState.

[flaviendelangle]

@joserodolfofreitas @m4theushw, I'm the only one notified so I'm adding you to the loop

---

I'm not working on the DataGrid anymore, but the team will have a look 👍

[rubenprodev]

Hi there, is there any news about it? An onDensityChange added to the catalog of events would be awesome!

[LironKiloma]

Hey, I'm joining to the support of density save in the state, would be great to have it

[ArmandRedgate]

Hello all,

This issue is causing us pain at the moment, as our customers expect us to save their DataGrid preferences, but there is no way to do so with density specifically.

Our order ID is 65425.

In the end, we had to do the following ugly workaround:

• Write and maintain our own version of the GridToolbarDensitySelector that uses externally managed state (getter and setter)
• Detect user changes to that dropdown
• Save those values to local storage separately from the rest of our GridInitialState data
• Update via the density prop in DataGridPro

We've spent hours looking for another way of doing this, but it was our only option.

Like everyone else, we'd like to see density be properly supported in initialState, apiRef.current.exportState and apiRef.current.restoreState.

[flaviendelangle]

cc @cherniavskii
Adding it to your backlog

[jmcpeak]

Hello all,

This issue is causing us pain at the moment, as our customers expect us to save their DataGrid preferences, but there is no way to do so with density specifically.

In the end, we had to do the following ugly workaround:

• Write and maintain our own version of the GridToolbarDensitySelector that uses externally managed state (getter and setter)
• Detect user changes to that dropdown
• Save those values to local storage separately from the rest of our GridInitialState data
• Update via the density prop in DataGridPro

We've spent hours looking for another way of doing this, but it was our only option.

Like everyone else, we'd like to see density be properly supported in initialState, apiRef.current.exportState and apiRef.current.restoreState.

We are in the exact same boat. We did purchase 4 licenses of data-grid-pro. Anything else you need from me to help move it to the top of the backlog?

[brendonrapp]

Running into this limitation now as well. The idea of doubling the number of saved states that we're managing so that each table can have a separate density state maintained is unappealing. Feels like a weird omission in an otherwise uniform and easily-managed table state system.

[jmcpeak]

I'll try and get a PR out with a fix on Monday

[github-actions]

⚠️ This issue has been closed. If you have a similar problem but not exactly the same, please open a new issue.
Now, if you have additional information related to this issue or things that could help future readers, feel free to leave a comment.

@vakha30: How did we do? Your experience with our support team matters to us. If you have a moment, please share your thoughts in this short Support Satisfaction survey.