Feature Explained: Invoice Receipt Date

Microsoft Dynamics GPBack in 2017, regulations in the UK changed so that business of a certain minimum size, had to start recording the date an invoice was received. To support this new regulation, Microsoft introduced a new Invoice Receipt Date field to a number of windows in the Purchasing series. This new field was introduced in the July 2017 hotfix.

The presence of this field does not seem especially well-known, so I figured I do a quick post covering where it is and how it would be used.

The Invoice Receipt Date has been added to the Date Entry windows for the three types of transaction:

  • Payables Transaction Entry (Purchasing area page » Transactions » Transaction Entry)
  • Receivings Transaction Entry (Purchasing area page » Transactions » Receivings Transaction Entry)
  • Purchasing Invoice Entry (Purchasing area page » Transactions » Enter/Match Invoice)

Taking Payables Transaction Entry as an example, to access the Payables Date Entry field, click the expansion arrow next to the Doc. Date field:

Payables Transaction Entry

Continue reading “Feature Explained: Invoice Receipt Date”

Making Tax Digital Now Available in Dynamics GP 2016 and 2018

Microsoft Dynamics GPMicrosoft’s Jodi Christiansen has, on the Inside Microsoft Dynamics GP blog, announced the release of the January hotfix which includes the Making Tax Digital (MTD) updates required for VAT submissions to HMRC from April.

The Microsoft Docs site has been updated with setup instructions; I need to get it downloaded and installed to confirm the functionality, as all of the setup is around the VAT 100 and not VAT Daybook. Clients with more complex VAT often need VAT Daybook which allows them to define which tax codes appear in which boxes on the VAT Return. We’ve previously been assured by Microsoft that the MTD update would include both VAT 100 and VAT Daybook so I need to check that this is in fact the case.

The hotfix can be downloaded from CustomerSource (login required):

  1. Microsoft Dynamics GP 2016 lock
  2. Microsoft Dynamics GP 2018 lock

The MTD changes are only available for Microsoft Dynamics GP 2016 and 2018; applying the hotfix will update you to the latest version of the R2 release of these versions. If you’re on a prior version you will need to either upgrade to 2016 or 2018 or source an alternative way of submitting to MTD, such as ISC Software’s Making Tax Digital add-in.

Payables Management Batch Posting Date Disabled When Workflow Active

Microsoft Dynamics GPA client recently logged an issue whereby the Posting Date on the Payables Batch Entry window (Purchasing area page » Transactions » Batches) in some companies:

Payables Batch Entry with Posting Date disabled

When we investigated the issue, it turned out that the field was disabled in those companies which had a Payables Transaction Approval workflow active; I did additional testing and the Payables Batch Approval workflow does not have the same effect.

Continue reading “Payables Management Batch Posting Date Disabled When Workflow Active”

Microsoft Dynamics GP Crashes/Closes When Emailing After Microsoft Office Update

Microsoft Dynamics GPEarly last week, the Dynamics GP Support and Services Blog posted about a problem whereby Microsoft Dynamics GP will crash when emailing after the latest Microsoft Office update.

This officially effects all versions from Microsoft Dynamics GP 2013 RTM onward, but one comment on the above blog post says it also effects Dynamics GP 2010.

The Microsoft Office update which causes the problem is:

  • Office 365 – Version 1811 (Build 11029.20079) – Standard
  • Office 365 – Version 1811 (Build 11029.20045) – Insider Edition
  • Office 2019 – Version 1811 (Build 11029.20079)

To check your version of Office, launch Microsoft Outlook, click File then Office Account; on the right hand side of the screen is a section for About Outlook:

About Office section showing version number

There are two options to resolve the issue (you should only have to apply one of them):

  • Revert/Rollback Microsoft Office to the last build.
  • Rename Dynamics GP Code folder and run a Repair (this will remove 3rd Parties).

Instructions for both options are available on the Dynamics GP Support and Services Blog.

We’ve found that for clients with the problem, rolling back the version of Microsoft Office fixes the issue.

Microsoft Dynamics GP 2018 U.S. Year End Update Released (Includes Critical VAT Daybook Fixes)

Microsoft Dynamics GPDon’t be fooled by the name; the Microsoft Dynamics GP 2018 U.S. Year End Update includes other fixes, some of which are critical to clients running the Vat Daybook module.

This fix has all the usual stuff for the Payroll (US) module which you can read about here.

The other good stuff in this version is:

  • System
  • VAT Daybook
    • Purchasing tax amounts from GL entries are subtracting from boxes 2 and 7, instead of adding to boxes 4 and 7 on the VAT Summary.
    • Sales returns and credit memos are not deducting total taxable amount from box 6 on VAT return, and voids from box 1 and box 6.
    • Purchasing returns & credit memo’s, voids are not deducting total taxable amount from box 7 on VAT return, and invoices not updating box 4.

The Microsoft Dynamics GP hot fix is available from: Customer Source lock or PartnerSource lock.

The VAT Daybook fixes have also been rolled back into Microsoft Dynamics GP 2016 (but no earlier): Customer Source lock or PartnerSource lock.

Script to Insert Microsoft Dynamics GP 2018 R2 Missing Security

Microsoft Dynamics GPEach version of Microsoft Dynamics GP which is introduced sees additional functionality introduced; often this additional functionality means new windows are created. This in turns means that the security roles and tasks required by Dynamics Gp change.

A fresh install of Dynamics GP includes all of this new functionality by default, but an existing implementation is not updated.

The reason it isn’t automatically updated is to allow the client to decide if the new functionality should be updated or not. To facilitate this, the Dynamics GP Support and Services Blog provides a script for each version with SQL insert statements for the new roles and tasks.

I’ve previously had a post which I updated with this information, but have now created a permanent page linking to the scripts.

I’ll be keeping this page updated in future for all new versions.

Microsoft Dynamics GP Book Roundup

Microsoft Dynamics GPThere are a number of books available for Microsoft Dynamics GP which have been written by various people across a umber of years (although a few names crop up repeatedly). I thought it might be useful to list the books which are currently available for each version of Microsoft Dynamics GP; some of the books are only available for older versions of Dynamics GP, but the information within is still mostly relevant.

To avoid any appearence of favouritism, I have listed them in Dynamics GP version and author surname order (when multiple authors, the first listed author’s name is used).

Where there is no version in the name I have made by best guess as to which version it was written against.

Microsoft Dynamics GP 2018

Microsoft Dynamics GP 2016

Continue reading “Microsoft Dynamics GP Book Roundup”

Microsoft Dynamics GP Roadmap 2018-2020

Microsoft Dynamics GPAt the GP Tech Conference this week, a new road map for Microsoft Dynamics GP was released which runs through to 2020:

Microsoft Dynamics GP Roadmap 2018-2020

As announced, earlier this week, the next version of Microsoft Dynamics GP is 2018 R2 and is scheduled for release on the 1st October 2018.

As you can see, on the roadmap, Intelligent Edge will be playing more of a role in future releases, but there will also be features requested by customers and the wider community. It is this latter section which is a large part of the new features in the upcoming release.

SQL Script to Change Compatibility of All Databases

Microsoft Dynamics GPWhen moving databases between servers for an upgrade of Microsoft Dynamics GP, you will, when also upgrading SQL Server, need to change the compatibility level of the databases. Rather than dong this individually, the below script can be run against the system database to generate a script you can then run to update the compatibility level of all databases.

The highlighted variable should be changed to the relevant version.

/*
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).
*/
DECLARE @CompatibilityLevel VARCHAR(140) = 140


SELECT 'USE master
	GO
	ALTER DATABASE [' + DB_NAME() + '] SET COMPATIBILITY_LEVEL = ' + @CompatibilityLevel + '
	GO'
UNION ALL
	SELECT '
		ALTER DATABASE [' + ['Company Master'].INTERID + '] SET COMPATIBILITY_LEVEL = ' + @CompatibilityLevel + '
		GO'
	FROM
		SY01500 AS ['Company Master']
GO

This script doesn’t get the logical file name, but I’ve hooked it into the series I did on Logical File Name SQL Scripts as it will often be needed at the same time.

SQL Script to Change Database Owner of All Databases

Microsoft Dynamics GPWhen moving databases between servers, you need to make sure the databases are set to have an owner of DYNSA. Rather than dong this individually, the below script can be run against the system database to generate a script you can then run to update the db owner.

/*
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).
*/
SELECT 'USE [' + DB_NAME() + ']
	GO
	sp_changedbowner ''DYNSA''
	GO'
UNION
	SELECT 'USE [' + ['Company Master'].INTERID + ']
		GO
		sp_changedbowner ''DYNSA''
		GO'
	FROM
		SY01500 AS ['Company Master']
GO

This script doesn’t get the logical file name, but I’ve hooked it into the series I did on Logical File Name SQL Scripts as it will often be needed at the same time.