In our most recent webinar, we took a look at Automation in Microsoft Dynamics GP. In this webinar, we covered how automation can be used in Microsoft Dynamics GP to improve efficiencies and accuracy of data. If you want to catch up on this, or any other, webinar, you can do so here.
In this blog post, I am going to recap the webinar and cover the highlights of how automation can be used in Microsoft Dynamics GP to improve efficiencies and improve data accuracy:
Where possible in this webinar I highlighted standard, or Microsoft supplied, features or additional products where they are available. However, in many cases the standard functionality does not allow for full automation. This is an intentional design choice made when Microsoft Dynamics GP was first created back in the md-90s. The company who created Great Plains, the original name of Dynamics GP, was intended from the very beginning to be extensible with the intention that there be a thriving third-party marketplace for add-ons.
This is the current situation; the core Dynamics GP system has strong core financials and distribution modules, but wider functionality is provided by third party (Independent Software Vendors (ISVs) who have a variety of add-ons and complimentary products which provide the functionality required or automating processes. In each of the areas, there are usually a number of products available from several vendors, but I have selected one in each area. usually an add-on which I have used with several clients across a number of years and which has received positive reviews.
Before implementing one of the solutions, I’d recommend reviewing the functionality it includes, the functionality of competing products and making your own decision about which will best fit your requirements.
As I mentioned in my last post, I’m in the process of doing upgrades for a couple of clients to the Dynamics GP Fall 2020 Release. Before I started on a clients system, I thought I would upgrade my own demo/test system to the latest version. The upgrade started fine, but then in one of the companies, the upgrade crashed with two errors:
Microsoft Dynamics GP Utilities
The stored procedure SynchronizeTableData() of form duSQLAccountSynch : 27Pass Through SQL returned the following results: DBMS: 2601, Microsoft Dynamics GP: 0.
Microsoft Dynamics GP Utilities
Microsoft Dynamics GP Utilities install/upgrade failed.
I’ve been doing some work with a client to implement the Workflow module of Microsoft Dynamics GP for approvals of Payables Transactions and encountered an oddity; when the user creates a transactions and hits Submit, nothing happens, but was not able to reproduce this on any of my demo or test systems.
There was a customised window in use on the client system, so I removed this and tried with the standard window and got exactly the same result. Some more testing showed that when the action pane was disabled and the old style toolbar being used, the Submit button was missing.
I had tried a 2018 RTM versaion and not been able to reproduce, but this was becuase I had one setting diferent. In Payables Management Setup (Purchasing area page » Setup » Payables Management), my systems were all set to allow the voucher number to be overridden, but the client had disabled this option.
When we changed this setting in their test company, the workflow submit worked correctly.
I did some further checking and was able to confirm that this is a bug in the Dynamics GP 2018 version which was resolved in the R2 version; the workaround is to allow the voucher number to be overridden and the solution is to upgrade.
Fortunately, we are already talking to this client about upgrading Microsoft Dynamics GP to the latest version; in the short-term they’ll allow override in test while the build and test of the workflows are complete and the deploy to live should tie in with the upgrade project.
This feature means Self Service users will now have access to the Workflow Delegation window within User Preferences, allowing them to set their own delegations up when they know they will be unavailable:
This is a nice addition which will make it a lot easier for clients to properly manage delegations.
A client reported a problem with workflow approvers opening the batch edit list on a Microsoft Dynamics GP General Ledger Batch Approval workflow action email this morning; only a few users are having problems while everyone else is working without problem. The users with the problem are getting this error when trying to open the Transaction Edit List report on the email:
Word experienced an error trying to open the file. Try these suggestions. * Check the file permissions for the document or drive. * Make sure there is sufficient free memory and disk space. * Open the file with the Text recovery converter. (C:...transaction Edit List.docx)
The problem does not just affect the Word template reports from Workflow Batch Approval emails, but also the Word templates used for sending purchase or sales orders, remittances and so on. For the non workflow Word templates, you could reconfigure the templates to use PDF, or one of the other formats, instead of Word, but, unfortunately, this option is not available for the batch edit lists.
Following the initial report, we’ve had a number of other clients report the issue, so it may be worth preempting problems and block Office updates for Dynamics GP users until a fix is in place from Microsoft.
I recently deal with a support call for a client where they were having problems creating a report which showed the approval status of GL batches. Building the WfBusObjKey was more complicated than I expected as it requires the date and time from the batch; for an unposted journal this can easily be retrieved from the PA Report Posting Definitions Master (SY00500) table, but for posted batches I had to do some exploring to find where the data was stored.
A client has recently been working on a project to implement approval workflows in a few modules of Microsoft Dynamics GP, but had an issue with the Payables Transaction Approvals notification emails not always including the Word template which all of the steps are marked to include.
There appeared to be no pattern on which approval emails either did or did not include the Word template; a user would receive the Word template on to emails, then not on the third, but again receive it on the fourth.
Doing some searching online found a post by Rob Klaproth of Armanino where he had the same issue and confirmed that there is a known issue logged with Microsoft whereby when the user submits a document for approval, and clicks submit on the comment box before the Word template has finished generating the email will not include the Word template.
The workaround for this issue is to make sure that users wait until the Word template has finished processing, as shown by the Template processing message at the bottom of the main Microsoft Dynamics GP window. If they wait until this processing has completed before hitting submit, the Word template will be included on the notification email.
This issue affects all of the edit list Word template attachments through all of the Workflow approval types.
I recently had an error reported to me in Microsoft Dynamics GP where some final approved purchase orders were not working correctly when opened in the Purchase Order Entry window (Purchasing area page » Transactions » Purchase Order Entry).
The PO is shown as not submitted in the workflow status bar, but the button on the tool is a Recall button rather than a Submit one showing that the document has been submitted:
This diagram shows the available workflow types, colour-coded by version introduced:
If you are looking to implement workflow, I have a book which can guide you though configuring the Microsoft Dynamics GP Workfow module from the basics of designing your workflow process, through building it and the ways that users can interact with the workflow for approvals.
The Workflow module is quite popular and becoming much more so with so many clients working in a distributed manner. There is one problem on the horizon and that is the retirement of TLS 1.0 and 1.1 which the Web Services for Microsoft Dynamics GP rely on. We are waiting for confirmation as to when a fix for this will be available, but I am expecting the fix to require an upgrade of Microsoft Dynamics GP which isn’t always quickly possible.
One of those products is PurchaseHQ which provides an Azure hosted web portal through which users can log on to do their purchasing series approvals. It fully integrates with the Workflow module in Microsoft Dynamics GP (blog and video) for document approvals (blog and video). The portal is quite a popular approach for organisations with a lot of approvals which need to be done as approvers have a web page they can logon to to see all of their approvals for all companies in one list, rather than receiving one email per approval.
With the recent growth in people working remotely, or “distributed working” which seems to be the en vogue expression, I’ve fielded a number of questions from people about how Microsoft Dynamics GP can help facilitate this.
Many clients already have remote access to their systems via a VPN or Citrix connection which allows users to connect to a server running the Microsoft Dynamics GP desktop client, but even these users don’t always have the capacity to put all of their users onto Dynamics GP in this way. However, this isn’t the only type of client available for Microsoft Dynamics GP.
In the current web client, all functionality from the desktop is supported including SmartList and Word templates for distribution of invoices, statements, remittances, purchase orders and more. The web client is lighter to operate than the full desktop client allowing more users to be server hosted on one server and can be accessed from the web browser, protected by an SSL certificate, removing the need for a VPN.
I have a book available on Implementing the Microsoft Dynamics GP Web Client; this is the Second Edition and has only recently been released (use code WEBCLIENT2ND for 25% off until end 15th May 2020) which will guide you through the process of installing using the web client from logging in to differences with the desktop client.