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.
As well as having the US Payroll updates there are updates to the following which would be of benefit to clients in the UK:
- VAT Daybook Summary reports may not show correct data in boxes 1, 6 and 7 if you voided a transaction.
- VAT detail report may show incorrect figures if you have 2 or more tax codes on a transaction.
- The Excel copy and paste function may not calculate the credit/debit column correctly when using an allocation account.
Fixed Asset Management
- Tax values may not update properly if a user marks to create multiple fixed assets in the Fixed Asset Purchase Order additional information window.
- You may experience performance issues with the Checkbook Register Inquiry window after you install GP 2016 R2.
- Ability to change line distributions for time and material projects in revenue recognition.
- Fee Accounts not available in line distributions button.
- Purchase Receiving’s not reflecting WIP account edits from Purchase Order for non-inventory items.
- Fixed issues with Uncollated printing.
The hotfixes for Dynamics GP 2013 R2 and 2015 R2 only contain US Payroll fixes.
The post from the Dynamics GP Support and Services blog contains the download links.
When you do a fresh install of Microsoft Dynamics GP, all of the required security roles and tasks are created. However, when Dynamics GP is upgraded, the new security roles and tasks are not automatically added. Microsoft do supply a set of scripts each time which can be run to add the roles and tasks.
This comes up every time we upgrade a client and I am tired of having to hunt out the posts from Microsoft, so I’m bringing together a list of the last few scripts and will add new ones here as each version is released.
The versions I could find again are listed below
- Microsoft Dynamics GP 2013 R2
- Microsoft Dynamics GP 2015 RTM
- Microsoft Dynamics GP 2015 R2
- Microsoft Dynamics GP 2016 RTM
- Microsoft Dynamics GP 2016 R2
One of the major new features in Microsoft Dynamics GP 2016 R1 is the HTML5 web client; this replaces the Silverlight web client released in Microsoft Dynamics GP 2013 R2.
The new features of the web client are:
- Support for Multi-browser (IE, Chrome, Safari, Edge)
- Support for Multi-device (Windows, iOS, Android)
- New controls created for HTML client
- UI changes
- Window Search
- Office “banner”
- Navigation, color, etc.
While the Silverlight web client was quite good, it was hobbled by dint of being Silverlight. There are quite a lot of iOS and Android devices out there which were unable to be used with the web client. Making the web client HTML5 not only makes it available cross browser, but it should also make it more flexible in terms of the size of device on which it can be used (Steve Endow at Dynamics GP Land posted his views on the “hamburger” menu used as a space saver back in September).
I’m fairly relaxed about this type of menu as I have seen them used on quite a few sites now and have largely adapted to their use. If that is the trade off for HTML5 then I’ll be happy.
This particular client uses the eConnect incoming queue to integrate journals and payables invoices into Dynamics GP from a housing management system.
After installing eConnect and configuring the incoming queue I set about doing a test to ensure it was working.
Unfortunately, it didn’t.
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.
Dynamics GP includes a variety of tools and modules to assist in controlling processes and data; one of the major modules for this was the Dynamics Workflow module. However, this module had major flaws which very much limited its usefulness; it was slow, clunky and difficult to install, configure and maintain.
However, my most recent problem with Integration Manager did actually produce a useful error message:
Integration 'Invoices' is not ready to run due to the following problems:
- The destination could not be initialized due to the following problem:
Cannot create ActiveX component.
I did a search and found a most useful KB article from Microsoft which detailed the problem (Microsoft Dynamics GP hadn’t been written to the registry correctly) and also the solution.
I read the whole article and decided to try a shortcut of starting with step 3 of re-registering the Dynamics.exe. To do this open a Run or Command Prompt and type the following (this particular problem was encountered with Microsoft Dynamics GP 20103 R2):
"C:\Program Files (x86)\Microsoft Dynamics\GP2013\Dynamics.exe" /regsrver
When I retried the integration, it ran through without further problems.
I had an oddity reported by a client just after an upgrade from Microsoft Dynamics GP 10 to Dynamics GP 2013 R2. After opening Enter/Match Invoice, entering the header information and clicking Auto-Invoice they received the following error:
Microsoft Dynamics GP
You must close the Select Purchase Order Items window before continuing.
I connected to their system and attempted to reproduce the error. My first few attempts failed and everything worked as expected. However, the problem did finally occur and I was able to see the problem happen a few times although it took a few minutes for me to realise the pattern.
The error message appeared when the cursor was in the lines scrolling window; if the cursor was still in a header field the error was not produced.
I have tested this on some of my test systems and the error appears to have been introduced between Dynamics GP 2013 SP2 and Dynamics GP 2013 R2.
The workaround is to make sure the cursor is not within the lines of the scrolling window and this message won’t appear.
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: