The second session was on Troubleshooting Workflow and was run by current Microsoftie, Dan Peltier. Dan’s name is one which has shown up a few times when we have logged calls so it was good to meet him.
Dan’s session was spoilt a little bit by virtual machine issues which meant he lost his pre-created examples just before the session started. He did get through everything on the agenda. I’ll be honest on this one; I know workflow well enough (having implemented workflow a few times for clients and written a book about it; which I am currently updating for Dynamics GP 2016) that I half expected not to learn anything new, and if I am honest that was the case.
That said, some of Dan’s explanations were clearer (especially around the and/or clauses of step conditions) than the ones which I have given in the past and which I had included in the first edition of my Workflow 2.0 book; I will need to roll some of these into the second edition of the Microsoft Dynamics GP Workflow 2.0 book which I am currently writing (hoping to publish by end of October.
The final session of the day I attended, was on Custom Workflow Creation. I was interested in this session, as we need to create some new Workflow Types. One which is needed, is a Workflow Type of EFT Bank.
The Vendor Change Workflow Approval is good, but does not do anything when the EFT Bank Details are changed and this is a major requirement for many of our clients in the UK.
The session showed how the new Workflow Type is created, tables updated, buttons added to windows and I took the opportunity to discuss wider requirements such as the need to update code elsewhere to respect the new Workflow Types created.
The changes for new Workflow 2.0 Types must be done in Dexterity.
There is a lot of scope for creating new Workflow Types in addition to EFT Bank Details such as SOP Transactions, Bill of Materials, and there my mind goes blank. Been in this airport too long.
The session on custom workflow creation was one of my favourites due to my interest in Workflow 2.0 (did I mention I am doing a second edition of my Workflow 2.0 book?).
[Microsoft][SQL Server Native Client 11.0][SQL Server][A .NET Framework error occurred during execution of user-defined routine or aggregate "Get "GetAssignedUsers". System.IO.FileLoadException: Could not load file or assembly 'System.DirectoryServices, Vers[
To remedy this, Terry Heley on the Dynamics GP Support and Services Blog has shared some macros, for Dynamics GP 2016, which add sample data into the Fabrikam sample data.
The new sample data focuses on a few modules:
- Advanced Human Resources
- Analytical Accounting
- Workflow for HRP
- Project Accounting Time and Expense
- PTO Manager
- Employee Self Service
Terry points out that this is a run at your own risk macro built on GP 2016, although it would probably be usable on Dynamics GP 2015 as well.
There are instruction documents with each macro as macros can crash based on the menu bar selected in user Preferences.
Also note that there is no support for these macros so no cases can be logged if issues are found.
The download link is available at the end of the post.
The first is on Working with Excel, Power BI and Dynamics and is being presented by MVP Belinda Allen:
The second is on Workflow 2.0 and is being presented by yours truly:
If you want to attend training, you will need to select one of the two available courses (unfortunately, you can’t sign up to both) when registering for reIMAGINE.
Workflow 2.0 has been enhanced to allow email notifications to be sent when a Workflow is reassigned:
Email notifications can be sent to the new approver for:
- Alternate Approval
This looks like it should be a useful addition to Workflow 2.0 although when configuring email notifications you do need to make sure people aren’t going to be swamped with emails.
As mentioned in the last post, more functionality has been added to the base Workflow 2.0 module, adding more flexibility. This second enhancement has seen the addition of new workflow conditions:
Two new options for what happens when step conditions are not met:
- Continue to next step
While it’s nice to see new features being added to Workflow 2.0, I’m not entirely sure of the use case for this addition, although it might become clear once I can get hands on with it.
My initial thought is if the condition isn’t met why would I want to continue to the next step? If I wanted that to happen then, surely, I would have had different conditions in the first place?
This has come up from a couple of different clients in the last few weeks. It would be good if approval workflows could be added to Receivings Transaction Entry and also the Enter/Match Invoices windows.
While there is workflow on the PO, a PO might not be fully received/invoiced so it would be good to have approval of the receivings document or the invoice.
The MS Connect suggestion can be found here.
Please take a look and cast your vote.
From now until the 5th January 2016 the ebook versions of Implementing the Microsoft Dynamics GP Web Client and Microsoft Dynamics GP Workflow 2.0 can each be bought for the discounted price of $9.99 using coupon code NEWYEAR2016.
Make sure you enter the coupon code NEWYEAR2016 at the checkout to get the discount.
Part of the reason I wrote Microsoft Dynamics GP Workflow 2.0 was that I expected the module to be very popular with clients, and so it has proven. It seems a robust and easy to use solution which is a vast improvement on the old SharePoint based Workflow module.
Recently, after upgrading a client to Microsoft Dynamics GP 2015, I was doing a training session with people from their IT and finance departments, or at least I was trying to. However, when trying to select a manager for the Workflow Type we received the following error:
Microsoft Dynamics GP
[Microsoft][SQL Server Native Client 11.0][SQL Server]A .NET Framework error occurred during execution of user-defined routine or aggregate "GetAssignedUsers": System.IO.FileLoadException: Could not load file or assembly...
I switched to the demo system on my laptop to continue the training until we took a short break when I did some investigation. I couldn’t see anything apparent on the client’s system so I did a quick online search.
I quickly found this post where someone had the same error and Microsoftie Jonathan Fear recommended running the following SQL:
Once I had run this in SQL Server Management Studio, the error in Workflow Maintenance went away and we were able to complete the training on the clients system.