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”
With the release of Microsoft Dynamics GP 2016 R2 it’s time for a series of “hands on” posts where I go through the installation of all of it’s components; the index for this series can be found here.
I’ve encountered this particular issue around the prerequisites so rarely, that I usually forget to mention it.
When installing the Web Services for Microsoft Dynamics GP there is a step where the SQL Server Connection Information is entered. This is the server where the Dynamics Security data will be stored.
You will receive the following message when clicking Next if the Windows user account you’re logged in as, is not a SQL Server sysadmin:
Invalid SQL Information
The current user must be a member of the sysadmin SQL role.
Continue reading “Hands On With Microsoft Dynamics GP 2016 R2: Web Services Runtime SQL Server Prerequisite”
Following the announcement by Microsoft back in June last year of a partnership with Jet Reports, the future of Management Reporter has been a topic of conversation amongst the community with rumours constantly swirling that Management Reporter would disappear from the Microsoft Dynamics GP space.
On the Inside Microsoft Dynamics GP team blog, Pam Misialek has posted a Management Reporter Fact Check:
- Management Reporter is available and fully supported by Microsoft. It is still included in the Starter Pack and will continue to be.
- Management Reporter will ship with GP Next later this calendar year and will ship in future releases as well.
- Microsoft are looking for any feature enhancements ideas which can be added to the product.
- HTTP support was added for Microsoft Dynamics GP 2016 R2
- Management Reporter will not go fully to the cloud in a multi-tenant environment. It can be used in the cloud, with a RDP connection.
Management Reporter is technically a separate product because it works across all Dynamics products. So what? Who cares? It works great at creating financial statements.
I’ve just found a page on CustomerSource called the Microsoft Dynamics GP Directory and it looks like it has been in existence for quite a while as it has links to information on Microsoft Dynamics GP 2010 through to 2016 R2.
The links include Top Reasons to Buy Microsoft Dynamics GP, Top Reasons to Upgrade as well as links to the Feature Blog Series, System Requirements, Service Pack, Hotfix and Compliance Update Patch Releases and much more.
I got to the page from the Dynamics GP Support and Services Blog post on the which I got to through David Musgrave’s post on Microsoft Dynamics GP 2016 R2 New Features .
Just shows it is worth reading around the blogs on Dynamics GP.