From the Microsoft Dynamics GP Blogs: Workflow bug; RM payment number; Multilingual installs; AR records; GP on Azure SQL PaaS

This week in Microsoft Dynamics GP blog roundup:

• Bug with Microsoft Dynamics GP 2018 RTM workflow step copy function
• Get next Dynamics GP RM payment number using SQL
• Multilingual installs in Microsoft Dynamics GP - what you need to know
• Move AR records from history to open - reversing apply (after paid transactions removal)
• Deploying GP on an Azure SQL Managed Instance

Bug with Microsoft Dynamics GP 2018 RTM workflow step copy function

On his Azurecurve blog, Ian Grieve wrote that the Copy Workflow Step feature was one of the new features introduced with Microsoft Dynamics GP 2018 RTM.

Some of clients who were using workflow had to manually configure every step, he explained, which could be very time consuming. However, being able to copy and amend the conditions would save a lot of time, according to Grieve.

When the new feature came out, Grieve went hands on with it, but only as far as copying a step. He didn't amend the conditions. If he had, he said that he would have found that there was a bug in this new functionality. One of his customers actually discovered the bug when they were adding some steps to a workflow.

You can read more about the bug here.

Get next Dynamics GP RM payment number using SQL

On the GP Land blog, Steve Endow said that when importing transactions into Dynamics GP, you often have to get the next transaction number or document number from Dynamics GP.

Sometimes, you can just leave the document number field blank and let eConnect get the next ...