Any increase in the maximum length of passwords is to be welcomed, but, seeing as this change required a database schema change to increase the SQL field length from 15 to 21, I am a little surprised that the new length is only 21 characters.

While the Fabrikam sample company is very US-centric, it is still somewhat useful to use as it has data spread across lots of different modules. The sample data hasn’t been updated for years and so still has the UK VAT rate set at 17.5%; VAT was raised to 20% in the 2010 budget and came into force in January 2011.

I created a script a while ago which could be used to create VAT rates for use in both Purchasing and Sales.

In Sales only a Standard 20% rate is created, but for purchasing rates are created for the Standard 20%, reduced 5%, Exempt and Zero Rated.

The ninth feature of the day is the ability to copy workflow steps. This is one of those features which is a very good enhancement; in fact, it is one which I requested from Microsoft on the old Microsoft Connect website.

Microsoft took my suggestion, of being able to copy workflow steps, added this functionality, but then extended it further than I had asked for, by including the ability to copy the child steps too.

This makes the function even more useful than I envisaged.

If you’re a regular reader, you will be aware by now that I am very involved with Workflow and a big advocate of using the module. One of the issues we had in the past, was when building a large workflow process, the branches are often similar to each other with, perhaps, only the amount, cost centre or site in the conditions being different between the different branches.

In prior versions, all of these steps had to be manually created; when there were multiple conditios in a first level step this could means lot of duplicated effort. This new cipy function does away with that effort as you can now create a single branch and then copy this entire branch and sdimply change the relevant values in the condition. So much less effort and therefore time required.

To copy a workflow step, open the step in the Workflow Maintenance window (Administration area page >> Setup >> Company >> Workflow >> Workflow Maintenance) and click the Copy button on the action pane:

I am working with a client at the moment on a large scale roll-out of Purchase Order Processing with a large, complex Workflow approval process. The project started towards the end of the last financial year and into the current one. While users were performing UAT, an issue suddenly arose where a goods receipt notes could not be entered in Receivings Transaction Entry (test). When the user tried, they received the following error:

A client reported a problem with their PO Approval Workflow process failing whenever a PO was submitted for approval. As soon as the Submit button was pressed, the document was rejected, but did not show a user:

Pretty much every client we have of Microsoft Dynamics GP uses the EFT Payment Register Report; a number of the save the file instead of printing it as the report has been customised to generate the EFT payment file for upload to the bank.

The clients who do this are either those whose installations of Microsoft Dynamics GP predate version 10 when the EFT for Payables Management module was made available to the UK market or they implemented before the EFT File Format was enhanced to allow a CSV output.

While some clients have created or amended a file format since the above, not all of them have been willing to spend the time (or money) to make the change.

As such, when they copy live to test they need to amend the path to which the report is being output, to ensure that a live file is not accidentally overwritten.

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 and also look at the new functionality introduced; the index for this series can be found here.

This feature will be popular with some of our clients who deal with non-recoeverable VAT (VAT is a UK sales tax charged at a standard rate of 20%) as non-rec VAT means they would need to depreciate the gross value of the asset including VAT where in previous versions the asset would be created net and need to be amended.

To use this feature, the Include Tax in Acquisition Cost checkbox on the Fixed Assets Company Setup window (Financial >> Setup >> Fixed Assets >> Company) under the Purchasing Options:

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 and also look at the new functionality introduced; the index for this series can be found here.

To test this feature, I created a new Tax Detail in Tax Detail Maintenance (Administration >> Setup >> Company >> Tax Details) for a Sales series Standard Rated UK VAT at 20% and created a related Tax Schedule:

A bit like Integration Manager, Management Reporter often presents highly generic meaningless error messages to users. The error message below was provided to me by a client a while ago (but I have just stumbled across the screenshots again), which I was then able to reproduce just be ruunning the report:

Management Reporter

The operation could not be completed due to a problem in the data provider framework.

Configuring Nolan’s Advanced Bank Reconciliation (ABR) to automatically extract transactions when reconciling a bank account is not complicated, but I keep on forgetting where the option is located. That gets a little embarrassing when you tell a client, “yes, you can do that” and then have to spend five minutes looking for the option.

So by writing it down here, I am hoping to be able to commit it to memory.

this option is per bank account and is located on the Bank Account Setup window (Financial >> Setup >> Advanced Bank Reconciliation >> Bank Setup).

Dynamics GP Community

Login

Map of Visits

Disclaimer

This blog is a personal project; all opinions are my own and do not necessarily reflect those of my employer.

This blog and its content is provided "AS IS" with no warranty of any kind, either expressed or implied, made in relation to the accuracy, reliability or content of the information herein. The author shall not be liable for any direct, indirect, incidental or consequential damages arising out of the use of, or inability to use, information or opinions expressed in this site and confers no rights.

The links in this blog may lead to third-party Web sites to provide access to third-party resources to assist you in finding other services and/or technical support resources. Information at these sites may change without notice and azurecurve is not responsible for the content at any third-party Web sites and does not guarantee the accuracy of third-party information.