A couple of days ago, I posted about the updated Microsoft Dynamics GP roadmap which goes through 2028. One item which is worth noting, is that Microsoft Dynamics GP 2016 RTM and 2016 R2 are both out of mainstream support as of yesterday and those versions are now in extended support.
This means that critical security issues found will be fixed, but no feature enhancements or other bugs will be added or fixed. This does of course include changes to the VAT Daybook module which are very important to users in the UK with the ever changing requirements from HMRC for MTD.
If you are using Dynamics GP 2016, I would recommend contacting your partner to discuss an upgrade to a version under mainstream support. If you are in the UK it is important you do this as you will only get updates to the MTD functionality if you are on the latest build of Microsoft Dynamics GP and under the Modern Lifecycle policy.
For those clients with MTD requirements, but who, for whatever reason cannot upgrade at the moment, ISC have an add-on available for all versions of Microsoft Dynamics GP which will support the MTD submissions to HMRC. If you’d like to discuss requirements in this area, please use the contact form below.
Terry Heley on the Dynamics GP Support and Services Blog posted an article on Friday on the exciting future of Microsoft Dynamics GP and giving a Lifecycle Update. As part of the article she inked to the published Lifecycle (Roadmap) for Microsoft Dynamics GP which extends to 2028 and beyond for Microsoft Dynamics GP.
The published roadmap also shows the end of mainstream and extended support for versions older versions of the product which predate the Modern Lifecycle:
- 2013 and 2013 R2 are out of mainstream support and in extended support until 11/4/2023.
- 2015 and 2015 R2 are out of mainstream support and in extended support until 14/4/2025.
- 2016 and 2016 R2 are out of mainstream support on 13/7/2021 and in extended support until 7/4/2026.
- 2018 and 2018 R2 in mainstream support until 10/1/2023 and in extended support until 7/4/2026.
Microsoft Dynamics GP is now under the Modern Lifecycle and has the same commitment from Microsoft as Dynamics 365. The Modern Lifecycle means there should be more frequent updates to Microsoft Dynamics GP with at least three updates a year in January, June/July and October.
Microsoft will continue to keep adding new features and improving it based on direct feedback from users. The best way to make sure you continue to benefit from the improvements is to keep up-to-date on upgrades and use the latest version of Microsoft Dynamics GP.
The key takeaway from the published Lifecycle is that Microsoft Dynamics GP is not going anywhere and development will continue under the Modern Lifecycle policy with multiple releases each year.
The recent problem with opening Word templates generated from Microsoft Dynamics GP, which was already fixed in Microsoft Dynamics GP Fall 2020 Release, has just had a fix released for Microsoft Dynamics GP 2016.
The fix can be downloaded from the patch releases page on CustomerSource in the U.S. 2020 Year-end Update in Dynamics GP which is available for Dynamics GP and Dynamics GP 2016.
It’s important to note that Dynamics GP 2016 is out of mainstream support in July 2021 so that version will not receive any further year-end updates for regulatory changes, so you will need to organise an upgrade to the latest version next year.
Early last week, the Dynamics GP Support and Services Blog posted about a problem whereby Microsoft Dynamics GP will crash when emailing after the latest Microsoft Office update.
This officially effects all versions from Microsoft Dynamics GP 2013 RTM onward, but one comment on the above blog post says it also effects Dynamics GP 2010.
The Microsoft Office update which causes the problem is:
- Office 365 – Version 1811 (Build 11029.20079) – Standard
- Office 365 – Version 1811 (Build 11029.20045) – Insider Edition
- Office 2019 – Version 1811 (Build 11029.20079)
To check your version of Office, launch Microsoft Outlook, click File then Office Account; on the right hand side of the screen is a section for About Outlook:
There are two options to resolve the issue (you should only have to apply one of them):
- Revert/Rollback Microsoft Office to the last build.
- Rename Dynamics GP Code folder and run a Repair (this will remove 3rd Parties).
Instructions for both options are available on the Dynamics GP Support and Services Blog.
We’ve found that for clients with the problem, rolling back the version of Microsoft Office fixes the issue.
We’ve had two separate clients recently log calls where Integration Manager was crashing while performing an integration.
The first client was doing an Inventory Items integration on Microsoft Dynamics GP 2015 R2 and the other was doing a Sales Transaction integration on Microsoft Dynamics GP 2016 R2.
Both of the integrations had been running fine for quite a long period of time before starting to crash; no changes had been made to either system and I’ve not been able to determine why Integration Manager (IM) has started crashing.
However, by the use of two ini file switches, we were able to determine what error was being encountered by IM resulted in a crash.
The two switches are already present in the ini file (C:\Program Files (x86)\Microsoft Dynamics\Integration Manager nn/Microsoft.Dynamics.GP.IntegrationManager.ini by default) where the False value needs to be changed to True:
When these switches are set to True, the Microsoft Dynamics GP windows are not hidden when the integration runs.
We found that for the Inventory Items integration, accounts either didn’t exist, didn’t allow account entry or were inactive; for the Sales Transaction integration, Analytical Accounting (AA) had been enabled for one of the accounts and the integration didn’t handle AA.
I created a VB script for the Inventory Items integration to check the accounts in the Before Document script and cancel the document if the account was going to be a problem.
Cancelling a purchase order line which came from a purchase requisition should, one would think, be a simple task. However, prior to Microsoft Dynamics GP 2016 R2, this was not necessarily the case.
This recently came back to mind when a client, who has recently implemented Purchase Order Processing with Workflow approvals on the requisitions (PO Entry window has been customised to lock a lot of the fields) raised an issue with me about not being able to cancel a line on the PO. After writing and demoing the functionality of Dynamics GP 2016 R2 a few times recently, it took a few minutes to identify a workaround for them as the client was running Dynamics GP 2015 R2 (14.00.1016).
The problem, is that you cannot cancel the link to the requisition in the same way you would a Sales commitment. If you try to cancel by entering a Qty Canceled, you get this error:
Microsoft Dynamics GP
The purchase order commitment can't be deleted; an attached sales line item is in use or is in history. Line items that weren't in use or in history are no longer committed to a purchase order.
Continue reading “Cancelling a PO Line Created From a Purchase Requisition”
The Dynamics GP Support and Services Blog blog announced the availability of the Microsoft Dynamics GP July Hotfix – 2017 Mid Year Tax Update towards the end of June.
This hotfix is available for Microsoft Dynamics GP 2013 R2, 2015 r2 and 2016 R2.
While all of them have updates for the US and Canadian Payroll systems, there were three changes in the 2016 version which caught my eye:
You may not be able to view any document attachment for any OPEN Payables Document.
- Invoice Receipt Date field addedÂ for UK installs, click here for details.
- Scan functionality may not function with document attach
The fixes to Document Attachment are good to see, but the Invoice Receipt Date was especially interesting as it results from new legislation which came into effect on April 1st for businesses of a certain size in the UK with a duty to report on their payment practices, policies and performance. This new requirement was introduced to protect smaller businesses that suffer from late payments, which can adversely affect their cash flow and jeopardize their ability to trade.
The new Invoice Receipt Date field is available on Payables Transaction Entry ( ), Receivings Transaction Entry ( ) and Purchasing Invoice Entry ( ).
The Doc Attach changes only effect 2016, but the new field is available in 2013, 2015 and 2016.
When reviewing some dashboards with a client a while ago we encountered an error launching the Financial Dashboard:
We found a problem with some content in 'T16R2 Financial Dashboard.xlsx'. Do you want us to try to recover as much as we can? If you trust the source of this workbook, click Yes.
Continue reading “Microsoft Dynamics GP 2016 R2 Financial Dashboard Error”
I’ve posted a few times about errors in Workflow requiring the wfDeployCLRAssemblies stored procedure to be run again (1 2 3), but the Dynamics GP Support and Services Blog has posted an article about how this is sometimes not sufficient to resolve the problem and the procedures, functions and assemblies deployed by the wfDeployCLRAssemblies stored procedure need to be deleted.
To this end, the blog post contains a series of scripts which need to be run before thew wfDeployCLRAssemblies stored procedure is executed. There are versions of the script for Microsoft Dynamics 2013 R2, 2015 (including 2015 R2) and 2016 (including 2016 R2).
If your problem still isn’t fixed, then a support case would need to be raised.
I’ve been doing some work recently on upgrading some Dexterity code to work with Microsoft Dynamics GP 2016 (both the RTM and R2). After compiling the new dictionary, I started Microsoft Dynamics GP and as the home page was loading got the following error:
Unhandled script exception:
SCRIPTS - data area
Continue reading “Dexterity Development ‘Unhandled script exception’ on data area”