Datagrid2 Refresh - Difference between test and local

0
I am using a datagrid2 which retrieves a list of imported objects over association. The user has the option to change the options directly in line in the datagrid2. Whenever an object is changed, an on change gets called which triggers a refresh of that singular object. Now locally this works smoothly and as expected. On other environments, I can see the whole datagrid reloading and I go to the top of the page again. What is causing this difference and how can I resolve the issue?
asked
2 answers
1

Since you mentioned the grid is loaded over association, I would mainly check whether the on change logic is indirectly refreshing:

  • the parent/context object
  • the association owner object
  • or triggering a full datasource refresh


A few things I would verify:

  • same Mendix version in local and test
  • same Data Grid 2 widget version
  • whether the microflow commits objects with Refresh in client = Yes
  • whether the datasource object itself gets refreshed during the onchange logic


I would try:

  • avoiding unnecessary refreshes/commits
  • refreshing only the changed object
  • or using a nanoflow/client-side update if possible for inline editing scenarios.


answered
0

Hello,

Avoid refreshing the parent/SearchContext object unless absolutely necessary.

Refresh only the edited object.

If possible, set:

“Refresh in client” = No

and manually update values in the UI.

answered