Microsoft Dynamics GP 2013 came out of mainstream support and into extended support as of 1oth April 2018; end of mainstream support means you will no longer get statutory updates such as the addition of the Invoice Receipt Date in the January 2017 hotfix which applied to the UK or year-end tax updates for the US and Canada.
I always recommend to client to look to upgrade every two to three years; the last few years have seen many improvements and additional new functionality added to Microsoft Dynamics GP (2013, 2013 R2, 2015, 2015 R2, 2016, 2016 R2 and 2018) as well as bug fixes.
By not upgrading regularly, you not only miss out on all of these fixes and new functionality, but you also make your eventual upgrade longer and more complex due to the number of versions which need to be upgraded through.
You can review the product lifecycle on the Microsoft Lifecycle Policy – Microsoft Dynamics GP page.
Microsoft Dynamics GP 2013 was released back on 12th March 2013; mainstream support is available for versions of Dynamics GP for approximately five years from the release date. Therefore mainstream support for Dynamics GP 2013 ends on 10th April 2018, after which it will go into extended support.
My recommendation to clients is to try to remain on a mainstream supported version of the product so that you can still receive hot fixes to major issues (or for US or Canadian users receive payroll updates).
With the frequency of releases of Dynamics GP, an upgrade every five years is going to mean an upgrade between five versions which is quite a jump (that’s going forward; for a while recently new versions were twice a year); I generally advise clients to upgrade every 2-3 versions to minimise the length of time an upgrade will take and how many intermediate versions need to be upgraded through (we have one client who does the ideal and upgrades once per year, but they largely do their own upgrades with only a small amount of input from myself).
Upgrading often means you have most of the bug fixes and regularly get access to the new functionality.
You can see the launch dates as well as the mainstream and extended support dates on the Microsoft Product Lifecycle page.
My recommendation is, if you are on Microsoft Dynamics GP 2013, and haven’t already started planning your upgrade, to start now.
Terry Heley announced the availability of the January 2018 Hotfix for Microsoft Dynamics GP the other day on the Dynamics GP Support and Services Blog. This hotfix is available for the following version of Microsoft Dynamics GP;
- 2013 – this will be the last hotfix for GP 2013, so you should really start planning your upgrade to a supported version.
While you don’t need to install every hotfix for Microsoft Dynamics GP, I would always recommend reviewing the fix list to determine if you need to upgrade.
I am not listing all of the fixes here, just the ones which seem important or relevant to my clients:
- These fixes are for 2018 only:
- You may experience slow performance when you click Inquiry>>Purchasing>>Transaction By Document.
- You are unable to make changes to copied workflow steps when created using the Copy Workflow Step feature.
- These fixes are for both 2016 and 2018:
- PM Payables Transaction Workflow A get/change operation on table ‘PM_Transcation_WORK’ failed.
- Upgrade error CO00104 set BusObjKey = replace(BusObjKey,’0\PM\Payables Transaction History’,’0\PM\Payables Transaction’) where BusObjKey.
- When two users simultaneously submit a document into a workflow with multiple approvers at the same time, one of the workflows will either go to the workflow manager or only be assigned to a portion of the approvers (this is an issue I logged with Microsoft which was causing issues for a couple of clients, so nice to see the fix available).
- You may notice duplicate payments with simultaneous use of the payables select checks window, warning was added to the user.
- You are unable to add new columns to existing Analytical Accounting SmartLists in Dynamics GP 2016 R2 or later & columns with special characters result in “excel found unreadable content” error when list is exported to excel.
- Posting a GL reversing entry to a historical year with P&L account, where it reverses in the new year has incorrect SEQNUMBR in the GL20000 and incorrect ACTINDX in AAG30001 on reversing ‘GJ’ entry and 0% in AAG3000.
For the full fix list, check Terry’s blog post
Microsoft Dynamics GP 2013 saw the introduction of the ability to reprint the check remittance report. This feature was a very nice one to see, as numerous clients, if not all of them, had been asking for.
At some point after this, and I am not sure in which version, the ability to email the reprinted remittance was introduced:
Continue reading “Report Used for the Reprint Check Remittance”
Winthrop DC has now officially launched the GP Power Tools and which are available to purchase from Winthrop DC’s partner Mekorma.
The GP Power Tools includes all of the functionality of the old Support Debugging Tool that they replace, but have new functionality, enhancements and bug fixes.
There is a special introductory annual subscription price of US$365 (one free day every four years!).
More information can be found on the GP Power Tools here.
If you were a Support Debugging Tool user on Microsoft Dynamics GP 2010 or 2013 then absolutely nothing
needs to change. SUpport Debugging Tool will not expire.
That said, you should consider upgrading to GP Power Tools for one major benefit: GP Power Tools is fully supported by Winthrop DC.
While this may not sound like much, the old Support Debugging Tool, which was offered by Microsoft, was not supported at all (not even by Microsoft).
I am slightly behind the times with this post as this news is a few weeks old, but I have been busy and am now trying to ctahc up. When David Musgrave was working for Microsoft he wrote the Support Debugging Tool which contained some very useful functions. I did wonder what the future held for it when he left Microsoft last year, but he posted a while ago that he had negotiated an exclusive agreement with Microsoft which allows him to continue work on and release the tool.
There will be some changed to the Support Debugging Tool under this agreement. Most noticeable is the fact that it will now be called GP Power Tools.
GP Power Tools will be initially released for the following Microsoft Dynamics GP versions:
- v11.0: Microsoft Dynamics GP 2010
- v12.0: Microsoft Dynamics GP 2013 and GP 2013 R2
- v14.0: Microsoft Dynamics GP 2015
There is going to be some changes to the functionality when GP Power Tools is launched:
- New simpler Navigation with menus and area page
- Database Validation, to ensure that your upgrades work
- Numerous enhancements and the odd bug fix
- And lots more….
Another change is that GP Power Tools will now be available via an annual subscription for each customer site at the special introductory price of US$365.00. That’s a dollar a day, and every four years you will get a day for free.
For now continue to use the free Support Debugging Tool for Microsoft Dynamics GP 2010 and GP 2013 (inc. GP 2013 R2) which is available from http://winthropdc.com/SDT.
Stay tuned here or to the WInthrop DC blog for more information on when to upgrade to GP Power Tools for continued support and improved functionality.
Those of you on Microsoft Dynamics GP 2015 will need to be patient for a while longer and wait for the release of GP Power Tools.
A recent install of eConnect ran into a small issue; after the installation was complete, the eConnect service wouldn’t start. In the Windows Event Log there were two errors shown:
Continue reading “Error Installing eConnect”
We had a user recently who wanted to quickly see which users had access to which companies and the Security Roles which had been granted. While Dynamics GP does have a number of security reports, they are the standard ones which, while readable in the usual screen or printer output, cannot easily be exported to Excel. However, the client is on Microsoft Dynamics GP 2013 R2 and therefore has access to SmartList Designer.
While I could have done this entirely as a SmartList Designer report, I already had the majority of the SQL needed to generate this as a SQL View which SmartList Designer can access:
CREATE VIEW uv_PI_UserAccessAndGrantedSecurityRoles AS
['User Master'].USERID AS 'User ID'
,['User Master'].USERNAME AS 'Username'
,['User Master'].USRCLASS AS 'User Class'
,ISNULL(['Class Master'].DSCRIPTN, '') AS 'User Class Description'
,ISNULL(['Company Master'].INTERID, '') AS 'Intercompany ID'
,ISNULL(['Company Master'].CMPNYNAM, '') AS 'Company Name'
,ISNULL(['Security Assignment User Role'].SECURITYROLEID, '') AS 'Security Role ID'
,ISNULL(['Security Roles Master'].SECURITYROLENAME, '') AS 'Security Role Name'
SY01400 AS ['User Master']
SY40400 AS ['Class Master']
ON ['Class Master'].USRCLASS = ['User Master'].USRCLASS
SY60100 AS ['User-Company Access']
ON ['User-Company Access'].USERID = ['User Master'].USERID
SY10500 AS ['Security Assignment User Role']
ON ['Security Assignment User Role'].CMPANYID = ['User-Company Access'].CMPANYID
AND ['Security Assignment User Role'].USERID = ['User-Company Access'].USERID
SY09100 AS ['Security Roles Master']
ON ['Security Roles Master'].SECURITYROLEID = ['Security Assignment User Role'].SECURITYROLEID
SY01500 AS ['Company Master']
ON ['Company Master'].CMPANYID = ['User-Company Access'].CMPANYID
Of course, the other reason I used the SQL rather than recreating entirely in SmartList Designer is that I can use this SQL in future, but a SmartList Designer is only usable on the system on which it is created as there is no import/export functionality.
I was working onsite with a client during an upgrade of Microsoft Dynamics GP from version 10 to 2013 recently, and after doing some work on a client we started receiving an error when trying to log out..
The error we received was the following:
Microsoft Dynamics GP – Unknown error 0 – 800AC351 occurred saving the project file
After a little testing to see if we could easily determine the problem, I did a quick online search and came up with this post from Vaidy Mohan which was the same error, but for a different VBA project.
The steps I tried and found to be successful were slightly shorter and easier than those Vaidy needed:
- Launch GP and open the Visual Basic Editor
- Opened modified report in the Microsoft Dynamics GP VBA project
- Added and removed a space from the end of one line
- Compiled the entire project to check for errors
- Save VBA project
- Log off from GP
To verify the problem was resolved we closed and reopened Dynamics GP and didn’t see the error when closing it again.
In this series of posts I have taken a look at the Config AD product from Fastpath which adds single sign-on to the Dynamics GP desktop client; you can find my series index here.
Over the course of the series I have run through the installation and configuration of several parts of Config AD, but there is still a lot of functionality that I haven’t covered.
For example, I have shown how to associate a GP user with a Windows AD account, but not how to disassociate them. I also didn’t show how SSRS security could also be assigned to users in Config AD; largely because I didn’t have SSRS installed and configured on my test box.
The main reason I haven’t covered even more than I have is that I enjoy playing around with different software and want to move onto something else. I’ve enjoyed the opportunity to have a go with Config AD which I found easy to install, easy to configure and that it provides a lot of functionality which brings together the security setup of Dynamics GP into one location.
Something I find very annoying in Dynamics GP is that to create a user, grant company access and assign roles you need to enter the System Password at least three times (unless you’re just copying security from another user wholesale), but Config AD allows you to configure all of this after logging into it once.
If you’re looking for an add-on which will both simplify the maintenance of Dynamics GP security (and I assume the effect would be the same for the other Dynamics products it integrates with) and allow for single sign on, then Config AD is definitely worth considering.