[data grid] We are encountering an issue with filtering in Data Grid Premium

[JimmySVENSSON]

The problem in depth

We are encountering an issue with filtering in Data Grid Premium.

Context:
Our setup includes a mix of hardcoded and dynamically generated columns.
We use the following code to allow filtering only with the ‘contains’ operator:
const filterOperators = getGridStringOperators().filter(
(operator) => operator.value === 'contains'
);

Problem:

• When filtering on dynamically generated columns, the Data Grid does not display any rows, despite receiving the correct data from the backend.
• If I remove the filter, I briefly see the correct rows before the grid resets to its initial state.
• This issue does not occur with hardcoded columns; filtering works as expected there.

Observations:

• If I change the operator to 'doesNotContain', the filtering works perfectly even for dynamically generated columns.
• The backend request is identical for both operators (contains and doesNotContain).
• This behavior seems to point to a possible timing or synchronization issue.

Questions:

• Is there a known bug with filtering dynamically created columns?
• Could this issue be related to the timing of dynamically creating columns during an API call?
• As a workaround, using doesNotContain works for now. Is this a safe and supported approach?

Your environment

`npx @mui/envinfo`

``` this gives me 1000 rows of code and then error messege code: 2147749902, stdout: '', stderr: 'ERROR:\r\r\nDescription = Invalid namespace\r\r\n', failed: true, signal: null, cmd: 'wmic os get Caption', timedOut: false

but im using:
"@mui/x-data-grid-premium": "^7.23.1",
"@emotion/react": "^11.14.0",
"@emotion/styled": "^11.14.0",
"@mui/icons-material": "^6.2.0",
"@mui/material": "^6.2.0",
"@mui/styles": "^6.1.1",
"@mui/system": "^6.2.0",

Windows 10 and windows 11
Node.js v18.19.0

we have tested in Chorme 131.0.6778.86 and in OperaGX

</details>


**Search keywords**: Data Grid premium, filtering, server-side
**Order ID**: 101282

[michelengelen]

To help us diagnose the issue efficiently, could you provide a stripped-down reproduction test case using the latest version? A live example would be fantastic! ✨

For your convenience, our documentation offers templates and guides on creating targeted examples: Support - Bug reproduction

Just a friendly reminder: clean, functional code with minimal dependencies is most helpful. Complex code can make it tougher to pinpoint the exact issue. Sometimes, simply going through the process of creating a minimal reproduction can even clarify the problem itself!

Thanks for your understanding! 🙇🏼