To install the Web Resource Cache start the setup utility from the download media and, under the Additional Products header click on GP Web Resource Cache:
I occasionally post suggestions from MS Connect and ask people to read the suggestion and cast their votes. Well, today I don’t have a single suggestion, or even two, but three suggestions for you to vote upon.
One Click Access to SmartList in Web Client
In the desktop client you can access SmartList from the area page, from the Microsoft Dynamics GP menu or via a toolbar icon. However, in the web client, only the first of these options are available and most users of Dynamics GP do not generally know of ways othet than the Microsoft Dynamics GP menu to start SmartList. This suggestion is to make SmartList available via one click in the web client.
Chris Dobkins submitted the suggestion and asked if SmartList can be made available by an icon next to the User Date in the web client; I don’t actually mind where the icon is, but agree that a single click method is required to make SmartList more accessible.
Hide Business Analyzer in Navigation Lists for All Users and All Lists
Business Analyzer can be a good way of seeing infromation from Dynamcis GP, but I have never liked BA being added to the navigation lists in Dynamics GP. This is why I added a recipe to the Microsoft Dynamics GP 2013 Cookbook which allowed it to be switched off globally with a SQL trigger. A Chris says, it would be better to have this functionality available via the GP client itself and allow users to switch it on when wanted.
End a corrupted Web Client Session
This is the third suggestion, suggested by Chris.
From time to time, a web client session will become corrupt. When this happens, you can reconnect to the session, but GP does not work (you may just gets lots of errors pop up in the status spinner, for example). When this happens, the user needs the ability to end the session from the screen that lists your active sessions and the tenants to which you have access to create new sessions. Users have the ability to remove their login from the activity table, and have had for many versions. Ending a hung web client session is the web client version of removing your user from the activity table so that you can log back into GP.
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:
The second of the wizards which pops up after the web client has been installed is the Web Components Help.
On the Welcome step click on Install to begin the installation:
Once the installation of the web client is complete, two wizards will be started. The first of these is the Microsoft Dynamics GP Web Components Configuration Wizard.
On the Welcome step click on Next:
To install the web client, launch the setup utility from the downloaded installation media. Under Additional Products click on Web Client:
As I am working on a small number of servers in my demo environment (a Domain Controller, a SQL Server and a Web Client Server) I will be doing a single-machine deployment with the sessions central and session host services on a single machine.
To do this I have the Microsoft Dynamics GP desktop client installed on the Web Client: this is the only machine with a client installed.
To do this, I need to add the Web Client Runtime feature to the installation of the desktop client. To do this open the Programs and Features applet in Control Panel, select Microsoft Dynamics GP 2016 and click the Change button:.
One of the new features introduced in Microsoft Dynamics GP 2016 R1 was an OData service which provides a new way to report off Microsoft Dynamics GP. Before OData can be used, the service ust be installed from the Dynamics GP installation media.
Load the setup utility from the installation media and, under Additional Products, click on :
Microsoft Dynamics GP PowerShell has a number of cmdlets which can be used to administer Microsoft Dynamics GP. Before you can use them GP PowerShell needs to be installed.
The following command can be used to return all available cmdlets for Dynamics GP PowerShell:
Get-Command = module GP2016
The following example shows how GP PowerShell can be used to create a new company:
Add-CompanyDatabase -GPClientDirectory "C:\Program Files (x86)\Microsoft Dynamics\GP2016" -SqlAdmin "sa" -SqlAdminPassword "password" -SqlServerName "2016R1-SQL\GP" -CompanyName "azurecurve Publishing" -CompanyDbName "A16R1"-SqlMdfFilePath "C:\SQL Server\Data\" -SqlMdfFileName "GPSA16R1Dat.mdf" -SqlLdfFilePath "C:\SQL Server\Data\" -SqlLdfFileName "GPSA16R1Dat.ldf"
The supplied parameters and their values are:
- -GPClientDirectory “C:\Program Files (x86)\Microsoft Dynamics\GP2016”
- -SqlAdmin “sa”
- -SqlAdminPassword “password”
- -SqlServerName “2016R1-SQL\GP”
- -CompanyName “azurecurve Publishing”
- -CompanyDbName “A16R1”
- -SqlMdfFilePath “C:\SQLServer\Data\”
- -SqlMdfFileName “GPSA16R1Dat.mdf”
- -SqlLdfFilePath “C:\SQLServer\Data\”
- -SqlLdfFileName “GPSA16R1Dat.ldf”/li>
You would replace the text between the quotation marks with the values you want to use to create the company.
Enter the cmdlet and parameters into GP PowerShell and hit return and the cmdlet will launch GP Utilities and create the new company; if you have any missing parameters or errors the launch will fail (usually with a less than helpful message).