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 ( ), 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 post is part of the Microsoft Dynamics GP Fall 2020 Release New Features series where I am going to echo the posts from the Dynamics GP Support and Services Blog, while adding some commentary, on the new features introduced in the Microsoft Dynamics GP Fall 2020 Release which is now available.
This post is on the Enable Self Service user type to access User Preferences System enhancement.
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)
I did some research and found there was a recent post on the Dynamics GP Support and Services Blog where they covered this same issue. The blog post was only four days ago and they acknowledge the issue is ongoing and offer the workaround of downgrading Microsoft Office to work around the issue (I did this recently when sending emails using MAPI caused Dynamics GP to crash).
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.
The table was the Posting Definitions Master History (SY30500); I’ve obviously never written a query which used this table as the name dones;t look familiar, but once I had the tale, it was a simple task to concatenate the fields together to make the WfBusObjKey and pass it to my function which returns the Workflow Approval Status.
I’ve used the SQL query to create a view so that it could easily be hooked into SmartList Builder, Refreshable Excel or other reports::
— drop view if it exists
IF OBJECT_ID(N’uv_AZRCRV_GeneralLegderBatchApprovalStatus’, N’V’) IS NOT NULL
DROP VIEW uv_AZRCRV_GeneralLegderBatchApprovalStatus
— create view
CREATE VIEW uv_AZRCRV_GeneralLegderBatchApprovalStatus AS
[‘Year-to-Date Transaction Open’].OPENYEAR AS ‘Open Year’
,[‘Year-to-Date Transaction Open’].JRNENTRY AS ‘Journal Entry’
,[‘Year-to-Date Transaction Open’].SEQNUMBR AS ‘Sequence Number’
‘General Ledger Batch Approval’
,CAST(RTRIM([‘Posting Definitions Master History’].BACHNUMB) AS VARCHAR(15))
+ ‘~’ + RTRIM([‘Posting Definitions Master History’].BCHSOURC)
+ ‘~’ + FORMAT([‘Posting Definitions Master History’].CREATDDT, ‘yyyy/M/d’)
+ ‘~’ + FORMAT([‘Posting Definitions Master History’].TIME1 ,‘HH:mm:ss’)
) AS ‘Wordflow Approval Status’
GL20000 AS [‘Year-to-Date Transaction Open’] WITH (NOLOCK)
SY30500 AS [‘Posting Definitions Master History’] WITH (NOLOCK)
[‘Posting Definitions Master History’].TRXSORCE = [‘Year-to-Date Transaction Open’].TRXSORCE
GRANT SELECT ON uv_AZRCRV_GeneralLegderBatchApprovalStatus TO DYNGRP
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 ( ).
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:
Continue reading “Incorrect Microsoft Dynamics GP Purchase Orders Workflow Status”
Since Microsoft Dynamics GP 2013 R2 saw the introduction of a new Workflow module for approval of documents, almost every version of Dynamics GP since then has introduced new functionality to workflow; sometimes in the form of new approval types or integration with other modules such as Document Attachment.
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.
Fortunately, the company for which I work, ISC Software, are both a VAR and an ISV with a number of products and services available.
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.
The Microsoft Dynamics GP Web Client was introduced in Dynamics GP 2013 R2 allowing users to access most of the functionality via the web browser. In Dynamics GP 2016 it was upgraded to HTML5 which lead to it being faster and more responsive.
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.
As well as introducing the web client, Microsoft Dynamics GP 2013 R2 saw the introduction of a new Workflow module for approval of documents. Almost every version of Dynamics GP since then has introduced new functionality; sometimes new approval types or integration with other modules such as Document Attachment:
Continue reading “Working remotely with Microsoft Dynamics GP”
I’ve done a lot of work with the Microsoft Dynamics GP Workflow module over the years since it was first released and it still seems to be growing in popularity with clients. Depending on the workflow type being created, the GL account string can be used in conditions to determine the routing for the approver.
However, commonly clients want to check the value for a single segment rather than the full account string. You can, to an extend, accomplish this using filters such as contains or begins with, but sometimes this isn’t feasible. You can get round this problem be using the
_ wildcard in your condition.
For example, if I was setting up a purchase requisition workflow and wanted to configure a routing for all advertising expense codes, which is the codes where the Account segment start 66, to the Marketing Director, I could set up a condition where the account string is
Workflow Condition example with wildcards in the account string
This would use this workflow step for all Divisions (segment 1) for department 00, where the Account (segment 2) starts with 66 and ends with 0. The wildcard character allows an account string with any value in the characters replaced with an underscore to be selected.
I was recently talking to a client who was looking at creating a SQL script which they could run for the auditors which shows the assigned approvers to the steps of a Microsoft Dynamics GP Workflow process.
I’d written similar code for others before so I was able to provide them with this view:
CREATE VIEW uv_AZRCRV_GetWorkflowSetupStepAssignment AS
Created by Ian Grieve of azurecurve|Ramblings of a Dynamics GP Consultant (http://www.azurecurve.co.uk)
This code is licensed under the Creative Commons Attribution-NonCommercial-ShareAlike 4.0 International (CC BY-NC-SA 4.0 Int).
,CASE WHEN [‘Workflow Master’].ACTIVE = 1 THEN ‘Yes’ ELSE ‘No’ END AS ACTIVE
,[‘Workflow Step Instance Table’].WF_Step_Predecessor
,[‘Workflow Step Instance Table’].Workflow_Step_Name
,[‘Workflow Step Instance Table’].WF_Step_Description
,[‘Workflow Step Instance Table’].EmailMessageID
WF100002 AS [‘Workflow Master’]
WF100003 AS [‘Workflow Step Instance Table’]
[‘Workflow Step Instance Table’].Workflow_Name= [‘Workflow Master’].Workflow_Name
WF40200 AS [‘Workflow Users’]
[‘Workflow Step Instance Table’].Workflow_Step_Assign_To = [‘Workflow Users’].UsersListGuid
This can be deployed to a company database and a SmartList object created using either SmartList Designer or SmartList Builder.
Updated 27/2/2020 to add Active column