Tag: Microsoft Dynamics GP 2018

When 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 (https://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.

When 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 (https://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.

With the release of the Microsoft Dynamics GP 2018 July Hotfix you now have the option of using Azure Active Directory Organization Accounts for the originator, approver and manager roles in Microsoft Dynamics GP Workflow.

Making Azure Organisation Accounts work with Workflow for originators, approvers and managers now means that Workflow can be used in pure Azure environments which do not have a traditional Domain Controller available.

Lucas Miller on the Dynamics GP Support and Services Blog has a blog post running through the steps to configure and install the necessary components to use this new functionality.

This post is part of the series on installing and configuring version 2 of this free GP Transaction Search addin from Steve Endow of Precipio Services.

GP Transaction Search is usable as soon as it has been installed, but can be customised in two ways by amending the GP.TransactionSearch.dll.config which is in the addins folder.

Firstly, you can change the SearchAsYouType valuer from True to False; I’d recommend this change for large datasets or where speed issues are detected:

Continue reading “GP Transaction Search v2: Customising the Configuration”

This post is part of the series on installing and configuring version 2 of this free GP Transaction Search addin from Steve Endow of Precipio Services.

Now that the prerequisites are installed we can download and install the addin. GP Transaction Search can be downloaded from Precipio Services:

Continue reading “GP Transaction Search v2: Downloading and Installing”

This post is part of the series on installing and configuring version 2 of this free GP Transaction Search addin from Steve Endow of Precipio Services.

In version 2 there is a new prerequisite; the Visual Studio Integration Toolkit (VSIT) from Winthrop DC. In version 1, the GP Transaction Search window replaced the Transaction by Document window; in this version, VSIT has been used to allow the GP Transaction Search windows have their own menus.

VSIT is a separate download; there is a download for each version of Microsoft Dynamics GP going back to 2010. Select the correct version and download the file:

Continue reading “GP Transaction Search v2: Installing the Prerequisites”

This post is part of the series on installing and configuring version 2 of this free GP Transaction Search addin from Steve Endow of Precipio Services.

The second version of GP transaction Search has followed along after version one very quickly. Despite that, it has gone from one search window for Payables Transactions, to including search windows for Receivables Management and Sales Order Processing.

In version one, the search window took over the menu of Transaction by Creditor Enquiry, but in this version, Steve has utilised the Visual Studio Integration Toolkit from Winthrop Development Consultants to create menus for each window:

Steve Endow of Precipio Services has recently launched a new GP Transaction Search addin for Microsoft Dynamics GP. The initial version had only a PM Transaction Search which replaces the Transaction by Document window (Purchasing » Inquiry » Trx by Document) in the Purchasing series.

Following very quickly on from version one, is a second version of the addin which contains a number of enhancements; I decided to do this second series as the installation if v2 differs substantially from v1.

Over the next few posts, I’m going to be taking a look at the installation, configuration and future of version 2 of this add-on.

GP Transaction Search v2
Available Search Windows
Installing the Prerequisites
Downloading and Installing
Customising the Configuration

Back at the end of June, Microsoft released the Microsoft Dynamics GP July Hotfix – 2018 Mid Year Tax Update. I’ve delayed posting as there was a retraction and re-release of the hotfix due to some changes in Ontario tax and I decided to give it a little time to settle down.

There are a number of bug fixes in this release, two of which I reported to Microsoft:

• The ability to copy workflow steps was announced as a Microsoft Dynamics GP 2018 feature of the day; however, once GP 2018 was released I found there was a bug in the copy where the conditions were linked and couldn’t be changed without changing the original step.
• The additional fields added to workflow in Dynamics GP 2018 were meant to be included in the Vendor Change workflow as sensitive fields, but the testing I did showed this wasn’t the case so I logged it with Microsoft.

Both of these fixes have been reported as fixed, so I will be giving this a test over the next few days, as I have a few clients waiting for these fixes.

Everyone will have their own notable fixes, but below is the list of items which I think will have relvance to my clients:

• You may notice the Cash Receipts Inquiry Zoom window is cut off in certain areas, missing fields, after you upgrade to Dynamics GP 2018.
• If a user’s workstations regional settings are set to the date format of DDMMYYY, transaction entry screens in web client does not reflect this date format. The main date in the top right corner does, but transaction entry screens do not. They show as MMDDYYY.
• The VAT report was not including transactions that originated from General Ledger.
• The VAT Report does not mark off transactions in the TX30000 table when regional settings are DATE/TIME format set to English-UK.
• PM Payables Transaction Workflow A get/change operation on table ‘PM_Transcation_WORK’ failed.

For the full list of fixes, see the Dynamics GP Support and Services Blog blog for full details and download links for supported versions of Dynamics GP (2015, 2016 and 2018).

Download links for Microsoft Dynamics GP 2018 are below:

• CustomerSource (login required)
• PartnerSource (login required)

I’ve assisted a few clients to upgrade to Microsoft Dynamics GP 2018 recently and have seen two different errors cause problems with Workflow.

As part of the upgrade process, database objects are deployed and various scripts run against them. This includes the wfdeployclrassemblies stored procedure which deploys the .NET Assemblies required by Workflow for such tasks as AD lookups and sending of emails.

However, I’m going to make the running of this stored procedure a standard, manual, part of the upgrade as I am finding that if it isn’t run after the upgrade is complete, that AD lookups don’t work until it is (this usually manifests in approvals failing to find a user to email or approvals failing if the user had the email from before the upgrade). I might was preempt and do it manually every time in order to give clients a smoother process. To run the stored proc, open SQL Server Management Studio and, against the system database, typically called DYNAMICS run the following (it’ll take a few minutes):

exec wfdeployclrassemblies

The other issue I’ve now seen more than once (and have also seen when upgrading some clients to prior versions), is that during the upgrade the Workflow managers are lost:

Continue reading “Workflow Approval Request Error After Upgrade”