Tag: HTML5

The web client was a god addition to Microsoft Dynamics GP and I do like the HTML 5 version introduced in Microsoft Dynamics GP 2016 RTM. While we have a few clients using it, and some only use the web client, we’ve not had any clients using both the web client and Account Level Security.

MVP Jen Kuntz is different; she’s currently looking at the web client for the company she works with and has come across an interesting problem.

The short version is printing the standard report version of the Trial Balance doesn’t work in the web client when Account Level Security is enabled:

Related to this problem, is another problem whereby user’s don’t have access to any accounts and so can’t do anything around transaction entry, enquiries or reports.

As Jen notes, both of these issues have written up as outstanding quality issues:

Bug #1 is Trial Balance report does not work when signing into Web Client with Windows Authentication if Account Security is enabled.

Bug #2 is Web Client users not able to post if Account Security is turned on. The user receives the error “Access denied/Account Missing”

The bad news is there is no timeline for fixing them, and from the sounds of it, it’ because there aren’t a lot of customers reporting this issue back to Microsoft. A “product suggestion” has been added to the new Ideas site for this which Jen encourages you to vote for:

In the last post, I showed the new HTML5 web client, but didn’t really give an opinion on how well I thought it worked.

Not having to install SilverLight on each PC or laptop which will run the web client is a definite plus; likewise it being cross platform and supported on Chrome, Safari and Firefox is another plus.

The HTML5 web client is also, in my opinion, quicker than the old SilverLight one.

However, there is one large negative which escaped me when doing initial testing and which Belinda Allen pointed out, although not on her blog, you can only have one open at a time; when you open a window the area pages are disabled, preventing you from opening another:

You can still drill down to other windows so you can for example drill from the Account Summary Inquiry to the Detailed Summary Inquiry or from Vendor Maintenance to Country Code Maintenance:

When you do open one window from a drill down the original window is then disabled. To toggle between them you need to use the Search for a Form or Report window:

This situation has created a bit of an outcry at Microsoft asking that they do further work to allow multiple window to be open at the same time. There is a post on the Microsoft Connect site where you can vote on this issue and impress upon Microsoft the importance that a resolution is found for this issue. You can vote here.

One of the main issues with the approach Microsoft have taken is that some ISV products rely on having more than one window open at the same time; another is it can seriously interrupt your workflow by being restricted to one window. Imagine, you’re half-way through creating a new vendor card when a customer rings up with an invoice query; you’d need to close the Vendor Maintenance window to open the Transactions by Debtor one.

With the web client installed and configured, it is now time to log in for the first time. With previous versions of the web client, this meant installing SilverLight, but the new web client is HTML5 based.

When you navigate to the GP app on the web server there is no apparent difference between the Microsoft Dynamics GP 2016 web client and the previous version; in both cases you need to login using your Domain Account:

One of the major new features in Microsoft Dynamics GP 2016 R1 is the HTML5 web client; this replaces the Silverlight web client released in Microsoft Dynamics GP 2013 R2.

The new features of the web client are:

Support for Multi-browser (IE, Chrome, Safari, Edge)

Support for Multi-device (Windows, iOS, Android)

New controls created for HTML client

UI changes

Window Search

Office “banner”

Navigation, color, etc.

While the Silverlight web client was quite good, it was hobbled by dint of being Silverlight. There are quite a lot of iOS and Android devices out there which were unable to be used with the web client. Making the web client HTML5 not only makes it available cross browser, but it should also make it more flexible in terms of the size of device on which it can be used (Steve Endow at Dynamics GP Land posted his views on the “hamburger” menu used as a space saver back in September).

I’m fairly relaxed about this type of menu as I have seen them used on quite a few sites now and have largely adapted to their use. If that is the trade off for HTML5 then I’ll be happy.

Dynamics GP Community

Login

Map of Visits

Disclaimer

This blog is a personal project; all opinions are my own and do not necessarily reflect those of my employer.

This blog and its content is provided "AS IS" with no warranty of any kind, either expressed or implied, made in relation to the accuracy, reliability or content of the information herein. The author shall not be liable for any direct, indirect, incidental or consequential damages arising out of the use of, or inability to use, information or opinions expressed in this site and confers no rights.

The links in this blog may lead to third-party Web sites to provide access to third-party resources to assist you in finding other services and/or technical support resources. Information at these sites may change without notice and azurecurve is not responsible for the content at any third-party Web sites and does not guarantee the accuracy of third-party information.

By continuing to use the site (by scrolling or navigating), you agree to the use of cookies. more information

The cookie settings on this website are set to "allow cookies" to give you the best browsing experience possible. If you continue to use this website without changing your cookie settings or you click "Accept" below then you are consenting to this.