Is anyone else finding issues with Grids being buggy and slower since the upgrade to 2024.1? E.g.
Scrolling through landing pages - the grids white out with each scroll and take 4-5 seconds to show data again. (Even when using the button to preload results).
Grid filters not working in some landing pages. Filters are not remembered when opening a record and going back to the landing page.
Grids are timing out and failing to load data - browser tab refresh usually sorts this.
I have raised cases with Support, but not getting very far, so Iām trying to understand if this is specific to our environment or to the base software.
Itās strange, as we originally saw improvements in 2023.1 and .2 to the grid issues, per the below post, but some of them seem to have been re-introduced.
Not seeing this, once the progressive load is turned off
It depends on the app. Some are remembered even when leaving the app entirely, some arenāt remembered when just going into the detail and back. Extremely inconsistent and frustrating.
Iāve seen this a couple of times but not consistently, chalk it up to network noise.
I havenāt played around too much in 2024.1 beyond verifying our customizations came through intact. Not a lot of deep dive navigating.
So, just playing around now to give you another data-point.
Scrolling through landing pagesā¦ grids seem to update in 1 - 2 seconds.
Grid Personalizationsā¦ column changes (placement) DO save with āSave Layoutāā¦ but filters do not (consistently). Example: If I set the Boolean on Open orders to trueā¦ it will filter and it will save that personalization for next time. But if I put in a CustID in a filter and save layout, that one doesnāt stick.
Gah, so disappointing that this is still present when itās been an ongoing issue for so long
Does anyone know if the āprogressive loadā can be disabled, so that the grid automatically returns a set number of records? Iād rather the page load was a couple seconds longer if it resulted in an easier user experience when using the grids.
Modern web apps are sure learning the biggest lesson of all time. I donāt know why they insist on being like this. I did a test capture in my browser and started scrolling for 3 seconds, it was 75% Javascript function calls within that time. The entire container being 392MB in memory.
This gives former web designer self a headache when sites do this. This is the amount of embedded child elements it takes to get from the start of the page to a clickable link inside of a grid layout:
