Microsoft Dynamics GP 2015 R2 was released at the end of May. As I mentioned at the time, I was away from home for work and rather busy otherwise so this series of posts has been somewhat delayed.
However, I am now getting my hands on GP 2015 R2 and thought I would do my usual set of posts on the installation of the various components and also the usage of the new functionality. This is going to be quite a long series of posts, so keep checking back regularly.
When using the Word Templates to replace the standard reports for printing reports such as invoices, remittances or purchase orders you can do changes to the format or layout using the standard functionality of Microsoft Word.
However, if you want to add additional fields then you need to install the Microsoft Dynamics GP Add-in for Microsoft Word. Do this by launching the Microsoft Dynamics GP setup utility from the downloaded installation media and, under Additional Products, click on Microsoft Dynamics GP Add-in for Microsoft Word:
We had a peculiarity the other day when updating a Word template for a client. We added some new fields via Report Writer and then created a new Word Template; when then modifying the Word template the fields usually show in the XML schema, but this time we found they weren’t.
After a couple of fruitless minutes checking the modified report and creating a new version of the Word template without success I started wondering about already open applications. In particular MS Word itself was already running with an unrelated document open.
I closed down all open Word documents and, in Template Maintenance (Administration » Reports » Template Maintenance), clicked the Modify button; when the Word template opened the new fields were showing in the XML schema.
This is something I have experienced before without being able to pin down why which caused..shall we say…a certain level of frustration. I’m not sure why having Word open caused the XML schema not to be refreshed when creating a new document, I am pleased that at least I can void the problem by making sure all open instances of Word are closed before starting.
I recently assisted a client with an upgrade of Microsoft Dynamics GP 10 to GP 2013 R2. As part of the upgrade we assisted the client to create some Word Template versions of sales invoice, purchase order, and cheque remittance (or check remittance to the American readers).
Everything appeared fine during development and initial testing. Fine that is until we tried producing a batch of twenty remittances which produced the following two error messages:
Microsoft Word – The file Check Remittance~2 cannot be opened because there are problems with the contents.
One of the very useful additions in Microsoft Dynamics GP 2010 was the ability to create invoice, remittance and other types of documents in a Word Template rather than having to do it all in Report Writer (although Report Writer is still needed if you want to create a custom field or make other fields available to the Word Template). While much of the editing and changing of formatting can be done using Word as is, if you want to add any new fields then the Microsoft Dynamics GP Add-in for Microsoft Word is required on any machine which will be used for doing this.
To install the Microsoft Dynamics GP Add-in for Microsoft Word open the setup.exe from the Microsoft Dynamics GP 2015 installation media and, under Additional Products, select Microsoft Dynamics GP Add-in for Microsoft Word:
The Microsoft Dynamics GP web client is as functional as the desktop one, even to the extend to which it integrates with Microsoft Office. However, whenever a user wants to integrate with Office on their machine, they first need to install a new component which allows the Silverlight web client to interact i the user’s installation of Microsoft Office.
To do this click on the padlock/globe/page icon next to the blue help icon in the bottom right of the window and then click on the Install Trusted Configuration link:
Now that Microsoft Dynamics GP 2015 RTM is available, I thought I could follow my usual pattern of posting a series of posts o how to install and configure both Dynamics GP, but also the additional products which ship with it. You can find the series index for these posts here. I am assuming you already have your server built with Windows and SQL Server for this series.
In this second post, I am going to take a look at the server install where the system database is created. To do this, run GP Utilities from the Start screen and log in using the sa account:
The stand out items for me is that support has been dropped for several older versions of Windows, SQL Server and Office:
Windows XP all editions
Windows Vista all editions
Windows Server 2003 all editions
2008 all editions (including R2)
The only surprise on the above list is that some of the software listed as no longer supported was also listed as no longer supported with Dynamics GP 2013; in fact only SQL Server 2008 is new to the list.
Apart from the above retired software, the recommendations look pretty much the same as Dynamics GP 2013; Windows 8.1 and SQL Server 2014 have been added as supported.
I have a number of clients who have been using Microsoft Dynamics GP for a number of years and who we are now upgrading again. A few of them continued using FRx when they upgraded to Microsoft Dynamics GP 2010, but now they are upgrading to Microsoft Dynamics GP 2013 they also need to switch to Management Reporter 2012 as FRx is not supported with the latest versions of Microsoft Dynamics GP.
Most of these migrations proceed without a problem, but I did have one client where the Migration Wizard ran through and returned a successfully completed message. However, when I logged into the Report Designer to check the migrated building blocks, I found that there was nothing there.
As a double-check, I re-ran the Migration Wizard to the same effects so I started to do some investigation. I eventually took a look in the FRx database and found a number of corrupt rows in the Catalog table like the one below: