This does mean that if you are on any version of Dynamics GP 2018 or on the 2019 Release, you will need to apply the 2020 Release update; a fix for Dynamics GP 2016 will also be released, but the method of approach is still being determined.
Recently, when performing an upgrade of a clients system to Microsoft Dynamics GP 23018 R2, the deployment of the reports went fine, but we encountered a problem while testing the deployed reports:
The client had a licenced version of SQL Server 2018 Web Edition which worked in all other respects; the SSRS service was running locally on the SQL Server which was hosting the databases for both SSRS and Microsoft Dynamics GP itself.
This wasn’t something I’ve encountered before, but, fortunately, a colleague had. The problem is not with the Web Edition itself, but rather with the data connection deployed by Microsoft Dynamics GP for the reports. When the data connections are deployed, there is a space created preceding the Data Source name:
The fix is to go through all of the datab connections and remove the space after the equals sign, so that, in the example above,
Data Source= IG-SQL2017-01\GP... becomes
Prior versions of Dynamics GP had this setting set to
FALSE; at the time he posed, Steve wasn’t sure if the setting was always set to
TRUE or only if the Web Client Runtime was installed. Well, I can confirm that it is always set to
I haven’t been that bothered by Dynamics GP always starting full screen, but after a client upgrade I was asked by them about it.
To stop Dynamics GP always starting full screen you need to change the Dex.ini file setting to false; this needs to be done on every client. If you are a GP Power Tools user you can use the Dex.ini Configuration tool to change all clients, otherwise you will need to manually update all clients.
I had decided to name the system database D18R2U and Fabrikam sample company as U18R2 as this demo VM was to be in US English. However, I named the system database U18R2.
I’ve never changed the system database used by a client before, but I remembered seeing a setting in the Dex.ini file:
This hands on new feature is, as far as I am aware, an unannounced one which I stumbled across when testing the partial purchase a purchase requisition new feature. When you click the Generate button on the Purchase Order Preview from Purchase Requisition Entry window, a prompt Skip displaying the new purchase orders? will be displayed:
This is a change of behaviour from the new functionality introduced in Microsoft Dynamics GP 2018 RTM; the purpose of this original new feature was to improve visibility of the created purchase orders.
This was, and remains, a laudable goal, but unfortunately the implementation was somewhat lacking. The new purchase orders were displayed by opening a navigation list, which could be ver slow to open (especially if the Reporting Services Reports had been deployed and the fact pane visible.
The 2018 R2 new feature, to hide Business Analyser for all users would go some way to mitigate this issue, by hiding the fact pane, but this new feature of prompting the user to decide if they want to see the navigation list will go the majority of the remaining way (a global option to disable would have gone all the way).
The twenty-third new feature is Email POP PO Other Form. This feature makes the Purhcase Order Other Form available for email.
My hands on with the feature was somewhat abbreviated when I discovered that there was no default Word Template available. While technically allowing a PO to be emailed using the Other Form, the lack of a default Word Templates means that there is a large amount of effort involved to make it available.
To create a new Word Template, you need to use the Word Template Generator to create a Word Template from the Report Writer XML and then format the resulting template; this is a long, complex and difficult to process to do in order not to break the template so email, or even the Word Template itself, doesn’t get broken.
The twenty-second new feature is Purchase Requisition Partial Purchase. You’ve always been able to increase the quatity to purchase, but you were not able to reduce the quantity. This new feature, allows a smaller quantity to purchase to be specified in order to partial purchase the requisition; the remaining quantity will be cancelled:
The flexibility this offers should be a good thing, but I have concerns around users being able to change the purchasing quantity here if an approval workflow is being used. That said, I already had these concerns about users being able to increase the quantity post approval.
The twenty-first new feature is Ship To Address Retained by Customer Combiner. This feature will retain the ship to address when customers are merged using the Customer Combiner tool:
I’ve tested this feature and compared it to the functionality in 2018 RTM, and I can’t tell the difference. The Ship To address of the destination customer, does not change in either version and the ship to address from both the source and destination customers are both available after the combine.
The twentieth new feature is New Sort Options in Sales Order Processing Item Inquiry Window. The Sales Order Processing Item Inquiry window has a new Sort By option available; this lets users quickly find the information they are looking for because now they can sort, either ascending or descending, by the following fields:
- Document Number
- Document Type
- Item Number
- Document Date
- Customer ID
This feature builds on the new sort options introduced to Payables and Receivables, by making the aame options available in the Sales Order Processing Item Inquiry window. This is a good addition as users are often asking the ability to sort by date; I hope to see it introduced in additional windows in future versions.