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).
Microsoft Dynamics GP 2015 RTM introduced PowerShell which can be used for a number of administrative purposes. To use the supplied cmdlets, Microsoft Dynamics GP PowerShell needs to be installed from the downloaded media.
Once you have the media downloaded, run the setup utility and, under Additional Tools, select GP PowerShell:
Microsoft Dynamics GP supports the use of cross-platform companion applications (such as the Business Analyzer app).
Run the Microsoft Dynamics GP setup utility and, under Additional Tools select Companion Application Services:
The first check, is to make sure that the Windows service is running; check this by opening the Services Control Panel applet (easiest to do by hitting Win+R and typing services.msc; scroll down and find Microsoft Dynamics GP Service Host. Ensure it is running and set to Automatic:
Overall I think it is a great device although it overheats when playing 1080p video (only since I upgraded it to Windows 10). It is a very capable machine for working on; I have written two books on it which included running a Hyper-V VM with SQL Server and Microsoft Dynamics GP running.
Until now, the only bug bear I have had with it is the lack of a Print Screen button (apart from the crashing on videos which I didn’t do very often anyway). But this morning when I got up the Surface was displaying the splash screen. The Surface had been left on last night and set to go to sleep.
I hit the power button and held it down to switch it off and came back this evening figuring I would see what the problem was.
Well, unfortunately, the problem was a persistent one. When I switched it back on again it got as far as the Surface splash and stayed there. I switched it off again by holding down the power button and restarted it, but the problem persisted.
The solution to the problem is as follows:
- Press and hold down the power button for at least 30 seconds and then release it.
- Press and hold down the power and volume up buttons and hold both down for at least 15 seconds; the screen may flash between showing nothing, the Surface splash screen and a boot menu. Release both buttons at the same time.
- Click Exit on the boot up menu which displays.
Your Surface should now boot.
With the Web Services for Microsoft Dynamics GP installed, it is time to do the configuration. The final step of the installation allows you to open the Web Services Configuration Wizard automatically, or it can be launched from the Windows start menu:
Since the introduction of Workflow 2.0 in Microsoft Dynamics GP 2013 R2, I have been doing a lot more installs of the web services. There are one or two gotchas (more at the configuration stage than the installation stage though) which I will highlight as we go through these next few posts.
Start the setup utility on the installation media. As web serices are likely to be installed on a server which does not already have any Dynamics GP components installed you will see the Bootstrapper Setup; click Install to install the required components:
If you have a number of clients to install then the best way of doing this is to create an installation package. Do this by launching the setup utility and, under Install click Create Installation Package:
Once Integration Manager has been installed there is a final admin step which is required. Before it can be used, it needs to be run as an admin (to prevent errors) and the registration keys entered.
Find Integration Manager on the Windows start menu, right click and Run as Administrator: