Skip to main content
Member
Sep 22, 2026 2:38 AM UTC
Solved

Dynamic Grid dropdown columns show stale values after horizontal scroll

We're seeing a repeatable UI issue on a Dynamic Grid component with several ParameterName-bound dropdown columns (Member List type), and I wanted to check whether this is a known issue or something we're missing in our configuration.

Repro steps:

  1. Edit a dropdown-bound cell in one row (e.g. select a new value from the dropdown).
  2. Scroll the grid horizontally so that column is off-screen.
  3. Scroll back to bring the column back into view.
  4. Every row now shows the same value in that column — the one just selected — regardless of what each row's actual data is.
  5. Clicking Save immediately corrects the display back to the correct per-row values.

What we've ruled out:

  • This only happens on columns bound via ParameterName (dropdown editors). Plain text columns on the same grid, edited and scrolled the same way, never show this behavior.
  • It's not a data/save issue — the underlying saved data is correct; this is purely a display problem that self-corrects on the next full grid refresh (i.e. after Save).
  • It doesn't appear to be related to row primary keys — we have one dropdown column that's part of the grid's primary key and two that aren't, and all three show the identical symptom.

Given the trigger condition (horizontal scroll causing off-screen columns to re-render), this looks like it could be related to column virtualization in the underlying Kendo Grid component — recycled DOM cells not being cleanly rebound to the correct row's data when scrolled back into view. Has anyone else run into this specifically with Dynamic Grid dropdown columns? Is there a way to disable column virtualization on Dynamic Grid, or is there a known workaround/fix version for this?

Happy to provide more detail on our exact component configuration if useful.

Employee - Sage
Oct 1, 2026 1:52 PM UTC

 

Transcript:
Thanks for the question, Mohan, about the dynamic grid parameter issue. To me, this sounds like a case for support. So probably something that you should talk with them about. Open a request in ServiceNow.

If possible, provide a little test case for them so they can reproduce the issue quickly on arbitrary environments. And then I'm sure they will follow up with the product guys and, and solve it for you. So the best, best way to go about this is, as I mentioned, try and create a little proof of concept that shows the issue. Open a service request and then go from there.

1 reply

Employee - Sage
Oct 1, 2026 1:52 PM UTC

 

Transcript:
Thanks for the question, Mohan, about the dynamic grid parameter issue. To me, this sounds like a case for support. So probably something that you should talk with them about. Open a request in ServiceNow.

If possible, provide a little test case for them so they can reproduce the issue quickly on arbitrary environments. And then I'm sure they will follow up with the product guys and, and solve it for you. So the best, best way to go about this is, as I mentioned, try and create a little proof of concept that shows the issue. Open a service request and then go from there.