Share
Report
17Hi, we have just enabled the new modern look and feel for D365 and Model Driven Apps. And with it, it has brought a new Grid View which has infinite scroll, and things like that.
We we have found when setting a filter on the Priority column (lookup type), and using the equals operator where you type in a partial value, its taking 5 seconds (5000ms) just to display the Priority options in the dropdown. Which you then select and it filters the table. Where on the older grid view it took 440ms.
I can see the that fetchXML which is used on the new grid is doing a get 5000 records of the Work Order table where Priority field is "like" whatever you put in the search box. Which means its scanning the whole table using the "like" operator on the Priority field. Which is very inefficient.
Where the fetchXML used on the old grid is first doing a get top 100 from the Priority table (takes 40ms), to then display those in the filter dropdown, you then select what options you want from the look up, which then results in a 2nd query to the Work Order table to say, where Priority equals X. And this takes 400ms. Resulting in an total of 440ms to perform a filter of Work Orders based on the Priority field.
So with the same user behavior, the technical implementation and resulting user experience is pretty bad.
Is this the right forum to provide this information to MS as feedback to try to drive improvements to the new grid view?
I appreciate that this is very wordy. If it's need I can provide images or even a video to show how I have investigate this
All responses (
Answers (
