No longer able to use the scroll bar or mouse wheel to scroll since the introduction of the new grid controls

(0) Share

Report

Posted on by Community Member

Since the introduction of the new grid controls my organisation has struggled with UI issues in particular scrolling through grid screens. We are currently using Finance and Operations 10.0.14 (10.0.605.20012) platform update 38. We had previously had the new grid controls enabled in feature management when they were still in public preview with less issues, but after upgrading to 10.0.14 we started receiving the unexpected client error pop virtually every time you are trying to navigate around a grid screen.

unexpected-client-error-2021_2D00_01_2D00_08-092902.png

So we had to take the decision to disable the new grid control feature in feature management. The problem is that the scrolling user experiencing with the new grid control disabled is poor. By this I mean using the scroll bar or mouse scroll wheel will only load 2 pages of rows to the grids screen. If you want to page through a general journal with many rows you have to use the keyboard page down and page up keys, or short cut keys ctrl +end or ctrl +home to jump to the bottom or top of the grid rows. The scrolling with page up and page down is also very slow. We typically use chrome but the issue is the same in Edge and Firefox.

If it was not for the unexpected client errors in every grid screen I could resolve this issues by enabling the new grid control in feature management. I will be upgrading to 10.0.16 once available later this month but it only appears to have 1 KB article for unexpected client errors in the project invoice grid which we do not use.

If any one else is having the same issue and/or has some better solutions or workarounds they will be gratefully received.

Best regards

Simon

I have the same question (0)

All responses (5)

Answers (0)

Suggested answer

Christoph Thaler 5,442 on at

Like (0)

Report

Hi Simon,

We have the same issue with unexpected client error in 10.0.14. In our case it is not related with the mouse scroll event. For every single form with this error we create a support ticket in LCS (currently 2 scenarios where we have this issue). After some analysis of logs by Microsoft we got information to update to 10.0.15. currently we will test if this solves the issue. Maybe you can check if your issue is solved in 10.0.15 as well, we are currently testing it.

Was this reply helpful? Yes No
Suggested answer

Sheela Ningappa on at

Like (0)

Report

Hi Simon,

As Christoph mentioned, we had many similar issues reported and The hotfix will be available starting from 10.0.15 version.

Below you can find the LCS link and click on notify me and you will be notified when the fix gets released:

fix.lcs.dynamics.com/.../Details

when you disabled new feature “New grid control”, you do not get this error message.

Regards,

Sheela

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report

Hi Christoph

Thanks for your reply. I am planning on upgrading our UAT environment to 10.0.15 or waiting for 10.0.16 later in January and will see if that helps. I have not been able to isolate the the unexpected client errors to specific forms it seems to happen in the majority of grid screens and particularly those used all the time like general journals. Hopefully 10.0.15 or 10.0.16 will resolve this.

Best regards

Simon

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report

Hi Sheela

thanks for this information I will use the link you sent to be notified of the fix. Yes we tested disabling the new grid controls in UAT to see if this was the cause of the unexpected client errors and it did resolve the problem. As soon as this is reenabled the unexpected client errors reappear. So we took the decision to disable in Production until their is a fix available. Unfortunately an expected side effect of this is the poor scrolling experiencing in all the grid screens (at least all those we use).

Best regards

Simon

Was this reply helpful? Yes No
Suggested answer

Community Member on at

Like (0)

Report

I have got rid of the issue by launching folder windows in a separate process. thegeekpage.com/.../

Was this reply helpful? Yes No