Tag: Microsoft Dynamics GP 2013 R2

I am slightly behind the times with this post as this news is a few weeks old, but I have been busy and am now trying to catch up. When David Musgrave was working for Microsoft he wrote the Support Debugging Tool which contained some very useful functions. I did wonder what the future held for it when he left Microsoft last year, but he posted a while ago that he had negotiated an exclusive agreement with Microsoft which allows him to continue work on and release the tool.

There will be some changed to the Support Debugging Tool under this agreement. Most noticeable is the fact that it will now be called GP Power Tools.

GP Power Tools will be initially released for the following Microsoft Dynamics GP versions:

• v11.0: Microsoft Dynamics GP 2010
• v12.0: Microsoft Dynamics GP 2013 and GP 2013 R2
• v14.0: Microsoft Dynamics GP 2015

There is going to be some changes to the functionality when GP Power Tools is launched:

• New simpler Navigation with menus and area page
• Database Validation, to ensure that your upgrades work
• Numerous enhancements and the odd bug fix
• And lots more….

Another change is that GP Power Tools will now be available via an annual subscription for each customer site at the special introductory price of US$365.00. That’s a dollar a day, and every four years you will get a day for free.

For now continue to use the free Support Debugging Tool for Microsoft Dynamics GP 2010 and GP 2013 (inc. GP 2013 R2) which is available from http://winthropdc.com/SDT.

Stay tuned here or to the WInthrop DC blog for more information on when to upgrade to GP Power Tools for continued support and improved functionality.

Those of you on Microsoft Dynamics GP 2015 will need to be patient for a while longer and wait for the release of GP Power Tools.

I had an oddity reported by a client just after an upgrade from Microsoft Dynamics GP 10 to Dynamics GP 2013 R2. After opening Enter/Match Invoice, entering the header information and clicking Auto-Invoice they received the following error:

I connected to their system and attempted to reproduce the error. My first few attempts failed and everything worked as expected. However, the problem did finally occur and I was able to see the problem happen a few times although it took a few minutes for me to realise the pattern.

The error message appeared when the cursor was in the lines scrolling window; if the cursor was still in a header field the error was not produced.

I have tested this on some of my test systems and the error appears to have been introduced between Dynamics GP 2013 SP2 and Dynamics GP 2013 R2.

The workaround is to make sure the cursor is not within the lines of the scrolling window and this message won’t appear.

I heard about this problem a short time ago, but have just had a client upgrade to Dynamics GP 2013 R2 and encounter this problem:

This issue was discussed at some length on the Community Forum with Frank Hamelly supplying a SQL script to update the assets.

With my client I took a slightly different tack and used the Fixed Assets Modifier tool in the Professional Services Tools Library (PSTL). This tool works on a single asset at a time and, unlike some of the other modifiers, does not allow import of a spreadsheet.

However, PSTL is written in Dexterity and allows the use of Dynamics GP Macros; so after doing an extract of all Asset IDs I was able to use mail merge to generate a macro to update all fixed assets containing a hyphen in the Asset ID.

I have checked Microsoft Dynamics GP 2015 and a hyphen is still disallowed in the Asset ID field.

We had a user recently who wanted to quickly see which users had access to which companies and the Security Roles which had been granted. While Dynamics GP does have a number of security reports, they are the standard ones which, while readable in the usual screen or printer output, cannot easily be exported to Excel. However, the client is on Microsoft Dynamics GP 2013 R2 and therefore has access to SmartList Designer.

While I could have done this entirely as a SmartList Designer report, I already had the majority of the SQL needed to generate this as a SQL View which SmartList Designer can access:

CREATE VIEW uv_PI_UserAccessAndGrantedSecurityRoles AS
SELECT
	['User Master'].USERID AS 'User ID'
	,['User Master'].USERNAME AS 'Username'
	,['User Master'].USRCLASS AS 'User Class'
	,ISNULL(['Class Master'].DSCRIPTN, '') AS 'User Class Description'
	,ISNULL(['Company Master'].INTERID, '') AS 'Intercompany ID'
	,ISNULL(['Company Master'].CMPNYNAM, '') AS 'Company Name'
	,ISNULL(['Security Assignment User Role'].SECURITYROLEID, '') AS 'Security Role ID'
	,ISNULL(['Security Roles Master'].SECURITYROLENAME, '') AS 'Security Role Name'
FROM
	SY01400 AS ['User Master']
LEFT JOIN
	SY40400 AS ['Class Master']
		ON ['Class Master'].USRCLASS = ['User Master'].USRCLASS
LEFT JOIN
	SY60100 AS ['User-Company Access']
		ON ['User-Company Access'].USERID = ['User Master'].USERID
LEFT JOIN
	SY10500 AS ['Security Assignment User Role']
		ON ['Security Assignment User Role'].CMPANYID = ['User-Company Access'].CMPANYID
			AND ['Security Assignment User Role'].USERID = ['User-Company Access'].USERID
LEFT JOIN
	SY09100 AS ['Security Roles Master']
		ON ['Security Roles Master'].SECURITYROLEID = ['Security Assignment User Role'].SECURITYROLEID
LEFT JOIN
	SY01500 AS ['Company Master']
		ON ['Company Master'].CMPANYID = ['User-Company Access'].CMPANYID
GO

Of course, the other reason I used the SQL rather than recreating entirely in SmartList Designer is that I can use this SQL in future, but a SmartList Designer is only usable on the system on which it is created as there is no import/export functionality.