Now that we have the first client installed, we can deploy the system database. By default the system database is called DYNAMCIS, but i have chosen to use one called D16R1. To deploy the system database, hit the Windows start button, search for and launch GP Utilities.
While I do try to minimise the use of the sa account as it is the SQL Server system administrator account, the initial implementation of Dynamics GP does require its use. So, on the Welcome to Microsoft Dynamics GP Utilities window enter sa in the User ID field and enter the relevant password.
Once done, click OK:
Once you have downloaded the installation media, the first step is to install a client. Typically, I will install a client on the SQL Server itself as this can avoid a number of problems, but this time round I did not and instead installed it on the server which will be my terminal server.
Before starting the install from the media, ensure .NET 3.5 has been installed; this can be done via Programs and Features in the Control Panel. If you have an Internet connection, the relevant files will be downloaded or you will need to specify the location of the files (Windows Server or Windows Client.
To install the desktop client, unzip the media and double click on the setup.exe. This will launch the bootstrapper which will install the remaining prerequisites:
Yeah, not so much. Microsoft promised the software would be generally available on 1st May, but I checked late last night UK time and nothing was there.
I checked again this morning and still nothing.
Until I checked David Musgrave’s blog and found he had been supplied a direct link by someone at Microsoft.
While Dynamics GP 2016 R1 was downloading, I did a little investigating and I think the reason it doesn’t show up for me is that PartnerSource presents itself as UK for me, whereas the link supplied to David was a northamerican one.
Thinking back I had similar problems when Dynamics GP 2015 came out and I couldn’t find the link on PartnerSource or CustomerSource. That time around I amended the 2013 in the link to 2015 and it worked; this time changing it to 2016 did not work.
Hopefully, Microsoft will get this sorted out to so the downloads for Dynamics GP 2016 are available via the UK sites.
Microsoft Dynamics GP 2016 RTM can be downloaded here.
|Hands On With Microsoft Dynamics GP 2016 R1|
|Downloading The Media|
|Deploy System Database|
I plan to follow the installation posts with ones looking at some of the new features, so keep checking back for new posts.
The previous feature of the day introduced the OData Service installation. This one gives a brief overview of how the service works:
The main features of the OData service are:
- Ability to define end points for the service
- View GP data with any tool that supports OData feeds
Microsoft Dynamics GP 2016 R1 is seeing the introduction of a new complimentary product: an OData service which will allow reports on Dynamics GP data using any reporting tool (such as PoweBI) to be created:
The main features of are:
- Separate install under Additional Products
- Use GP Security to control access to data
- Supports tables, views and stored procs as data sources
In February 2014 Microsoft launched PowerBI for Office 265 and are now bringing it to the Microsoft Dynamics GP 2016 R1 home page (but only the home page of the desktop client):
The main features of are:
- New part on Home Page to display Power BI Reports.
- Click on the report to take you out to your Power BI site.
I’m not entirely sure how to feel about the addition of PowerBI to Dynamics GP; it almost feels like a scatter gun approach is being used for reporting with Dynamics GP. There are standard reports, Metrics, Excel Reports, SSRS Reports (which for most clients replace the Metrics to the extent I had to lookup the name of Metrics), Management Reporter (with an unknown roadmap/future) reports and now PowerBI reports.
I was a little surprised to see Microsoft announce Display Duplicate G/L Accounts on Budget Exception Report as a separate feature of the day as it looks to be part of the Budget Import Exception Report which is a new feature in Dynamics GP 2016 R1 itself:
The original feature of showing accounts the budget which don’t exist in Dynamics GP is going to be fabulously well received; this one is a very good addition which I think may not be fully understood by some.
I have had to explain to a few clients that having the same account on the file more than once will result in only the final value ending up in Dynamics GP as it will overwrite the previous entries. If you want to load values in multiple times and have the cumulative values, you need to load multiple budgets and then use the Consolidate Budgets feature.
Document Attachment was introduced in Microsoft Dynamics GP 2013 R1, was improved in subsequent versions and is being improved again in Dynamics GP 2016 R1 to allow attachments to be managed after they have flowed down to the transaction:
The main features are:
- Edit attachment information that flowed from master record.
- Enable Flow and email checkboxes for flow attachment options.
There are some feature of the days which I look at and think “so what?”. And then there are others I look at and know they are going to be very popular.
This feature is very much one of the latter (I have one client who would be willing to upgrade to just top get this one feature). It is the ability to have Cash Receipts automatically posted in Bank Reconciliation:.
The main features of are:
- When Automatically Post Cash Deposits is marked and you post a batch with cash receipts in it, one deposit will be created for all cash receipts in the batch.
- If you transaction level post, each transaction will create a separate deposit.
There is one downside to this feature; if you want your deposits to show as individual deposits in bank you have to post them separately in Receivables Management. Doing one transaction per batch (transaction level posting would result in manual posting being required of the resulting GL batches) will not be as time consuming as doing all of the deposits manually, but is moving an element of the work from one part of Dynamics GP to another (and possibly from one team to another).
The client I references at the start of this post runs a number of visitor centres so will have a lot of cash receipt transactions being imported into the system, but the majority of them would hit the bank as a single deposit. I’m onsite with them soon to help integrate their new EPOS system into GP so can work with them to make sure transactions are brought into Dynamics GP in the way necessary for them to benefit most from this feature.