Share
ReportConsidering 14.x Windows Client, and earlier, it is quite easy to check / uncheck e.g. “Reserve” field in Order Planning worksheet page within the UI. See below a typical example
Users just go and check, check, check, uncheck, etc. Easy as we speak.
What about Web Client?
Dynamics 365 Business Central 2019 Spring release (version 14.x) and earlier
Within 14.x Web Client, if a user would like to perform assignments on “Reserve” field, he/she has to first select the line. Only after selecting the line, it is possible to check or uncheck that field.
Conclusions: It is surely less productive than Windows Client but, in the end, it works.
Dynamics 365 Business Central 2020 Wave 1 (version 16.x) and higher
Starting from September 2021 SaaS update and the equivalent on-premises Cumulative Update (CU), client runtime team has partially modified how server and client interacts considering this behavior.
Within these builds, for versions 16.x, 17.x and 18.x, it would be possible to check / uncheck “Reserve” field without the need of selecting the entire row.
There are still some caveats.
- To check / uncheck “Reserve”, it is needed first to click the field, outside the check square. This action will enable the entire row. After that it is possible to assign the value.
- When performing this action several time, you might end up with a list made of a mix of editable and non-editable rows checked (or unchecked). It is just a visual defect.
- Scrolling down lines, at certain point you might see that all lines suddenly are shown as editable. That is another visual defect.
Conclusions: It is surely more productive than 14.x Web Client but less attractive and good-looking than Windows client.
Dynamics 365 Business Central 2021 Wave 2 (19.x)
If you are a partner and subscribe to MS Collaborate, you should be able to download insider builds for what is called vNext. Within vNext, product group has resolved all remaining minor issues reported within earlier versions within this scenario.
NOTE: this is the result of a refactoring how client and server interact considering the scenario just exposed. These changes are declared by product group as too risky to be backported in version 14.x. They have been partially back ported to 16.x onwards starting from September 2021 with the pros and cons exposed in this blog.
Conclusions: productivity (and usability) gap from Windows and Web client, considering this scenario, could be considered as resolved starting from the next major version (19.x).
All responses (
757
