Click here to
Subscribe to
our Newsletter
Development related Posts
A recent post on LinkedIn asked about the reasons that most of the column names in Microsoft Dynamics GP are cryptic abbreviations of 8 upper case characters. My friend and fellow Microsoft MVP, Jen Kuntz (congrats on being re-awarded) responded and in that response tagged me.
I wrote up another comment, and then decided to turn that comment into a blog post….. here it is. 😁
Today, I was asked by a consultant how to parse specific data out of the record note associated with a transaction or master record in Microsoft Dynamics GP using a SQL Server query.
GP uses the SY_Record_Notes_MSTR (SY03900) Record Notes Master table to store a text field of up to 32767 characters linked to master or transaction record using the Note Index (NOTEINDX) field. The next available Note Index is stored in the SY_Company_MSTR (SY01500) Company Master in the system (DYNAMICS) database and is assigned to new records when they are created.
Today I was asked if the GP Power Tools Automatic Logout functionality can be used to automatically logout other external applications, for example: SalesPad For GP from Cavallo.
My initial answer was that it was not possible as the Automatic Logout functionality provided in GP Power Tools is Dexterity based and does not have the ability to affect other applications.
But then I thought about it some more and …
This is a further update to the previous versions of the change tracking projects for Customer and Vendor cards:
Based on the version 2 projects, this update adds tracking to the Vendor and Customer EFT Bank Maintenance windows.
As is becoming a tradition, I will once again be running the 5-day Dexterity training class in the week before the Community Summit conference in Charlotte, North Carolina, USA in October. Please register for the training now and plan to be in Charlotte for the week before the conference.
Dexterity is the development environment that Microsoft Dynamics GP is built on and the best tool to use for any customization to the user interface of the product. Knowledge of Dexterity is vital for anyone customizing Dynamics GP even when using other development tools such as GP Power Tools – Developer Tools module, Visual Studio Tools (C# or VB .Net) or “End of Life” VBA (Visual Basic for Application).
Back when Australia introduced its Goods and Services Tax (GST) in July 2000, I designed and developed the Business Activity Statement (BAS) Tax reporting tool which also contained a utility to update tax schedules and recalculate taxes on unposted Sales Order Processing Transactions.
This code was re-used in October 2010 when New Zealand changed its GST tax rate. The code from the BAS reporting tool was copied and placed into Runtime Execute scripts for the Support Debugging Tool (see original article).
This week I was contacted by James Bacon from Green Rubber – Kennedy Ag as he wanted to use the code again to update some transactions when a tax rate had changed. While the code did “mostly” work, this was an opportunity to update the code to improve it and use more features in GP Power Tools.
Microsoft Dynamics GP has added support for Multi Factor Authentication (MFA) to the emailing functionality inside Dynamics GP to allow it to connect to Microsoft Exchange, now that simple authentication is no longer supported.
However, there is no MFA functionality for logging into the Microsoft Dynamics GP application itself… until now.
[Edit] Build 33 of GP Power Tools now supports true MFA on login using an Authenticator app with a One Time Password:
Using GP Power Tools Developer Tools module, with a single after login trigger, it is possible to force the request to connect to Microsoft Exchange and close GP if the connection is not authenticated.
Yes, you heard correctly. Winthrop Development Consultants is thrilled to be Title Sponsor of the March 2023 DynamicsCon Virtual Conference taking place on 15th and 16th of March 2023.
Make sure you register to attend this free online conference to learn more about Microsoft Dynamics GP and related products and technologies.
This article has two purposes. The first is to highlight a very useful script published by Michael Krasivsky from The Resource Group back in 2016. The second is to explain how easy it is to use the GP Power Tools SQL Execute Setup window to execute scripts against multiple databases.
Microsoft Dynamics GP provides access to all the SQL Resources (Tables, Views, Stored Procedures, etc.) using the DYNGRP SQL role. For this technique to work correctly, all GP users need to be assigned to the DYNGRP role and all SQL objects need access “Granted” to the same DYNGRP role.
We get reports every now and then of a user being logged out of Microsoft Dynamics GP by the GP Power Tools Automatic Logout feature even though they have been active on GP within the timeout period.
This happens because there is no way to track “Inactivity” in Microsoft Dynamics GP, so instead we attempt to track “Activity” by triggering on common events/scripts within GP and resetting the last active time and date.
However, there are times when a user could be active in GP and manages to avoid invoking any of the actions that would be identified as “Activity”. When this happens, they can be logged out incorrectly.