Click here to
Subscribe to
our Newsletter
This is an update to the previous version of the change tracking projects for Customer and Vendor cards:
Based on the original projects, they have been enhanced to add some more fields into the default fields tracked, add support for array fields, and add support for tracking Modifier Added fields.
I have had quite a few requests for Dexterity Training recently. So once I decided to go to Community Summit in Orlando, Florida, USA in October, I planned to run a 5 day Dexterity Fundamentals Bootcamp in the week beforehand. Please register your interest as soon as possible to ensure the course goes ahead.
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).
After two years of uncertainty, I am finally heading back to the United States for the Community Summit conference in Orlando, Florida, USA in 10th to 13th of October 2022.
I will be running Dexterity and GP Power Tools training, presenting a number of conference sessions and manning an Expo booth.
Today, I started the morning with a support call with a US customer and partner regarding what appeared to be a performance issue caused by GP Power Tools.
Once we used GP Power Tools to troubleshoot and identify the root cause of the issue, it was easy to see why they incorrectly thought the problem was caused by GP Power Tools.
Read on to understand what happened and how to make sure it does not happen on your systems ….
This article and sample GP Power Tools project comes about after hearing about a disturbing situation that has resulted in an unsuspecting Australian business receiving a surprise $100,000 tax bill.
The sample project code provided at the bottom of this article was created to help ensure that Australian Microsoft Dynamics GP sites don’t get caught out in the same way.
I have been asked many times about integrating data using GP Power Tools. While this is not what GP Power Tools – Developer Tools module was originally designed to do, it can be used to integrate data (for both adding and updating records).
The main reason for writing this article and creating the updated project was because a friend asking for a quick method for updating Item List Price information because their suppliers are providing new pricing information on a weekly (or less) basis.
The IMPORT_EXAMPLE Project take an original example script and massively improves on its capabilities to make it really simple method to integrate data for Accounts, Customers, Vendors and Items from a CSV (Comma Separated Values) text file. The file can be edited with Excel or your favourite text editor but must be saved as an 8-bit ASCII file using the ANSI or UTF-8 option.
Yeah. I admit it.
I messed up! ☹️
But it is sorted and fixed now, thanks to a great article by my friend and fellow MVP, Jen Kuntz.
You might be aware of the new Security requirements for Bank Account Numbers which applies to ACH Originators and Third-Parties with more than 2 million ACH payments annually and becomes effective on 30-Jun-2022.
NACHA, the governing body for ACH transactions in the United States, is rolling out updated security requirements which are actually best practice whether you meet the transaction level targets or not.
Read on for how you handle the requirements on your Microsoft Dynamics GP system.
This article covers the latest “Must Have” free sample project for the GP Power Tools – Developer Tools module (requires Build 28 or later).
Back in 2012, I created code to obscure customer credit card details (see more information below). Using the same concepts, I have now created a project to obscure Bank Account Numbers for Checkbooks, Customers, Vendors and Employees.
Whether you have a requirement (see NACHA Security Requirements article) or not, best practice would be to make sure that Bank Account Numbers in your system are not human readable while stored in the database.
After three week’s work, I am thrilled to be releasing a second version of the Free SQL Search Lookups Example. Based on feedback from a number of users, the code for this example has been significantly improved and extended. It even now has an optional Automatic Selection mode for when there is only one record returned.
Please see the GP Power Tools Samples page for additional examples that you can download and use for free.
To give you an idea of how much it has changed, the old exported dbg.xml file was 321KB and the new one is 929KB. Read on to learn about all the changes made ….
This is a completely off topic post for me. It is not Microsoft Dynamics GP, Robotics or even puzzle related.
We recently moved house (twice) and during the shift from the original home to the final home, our Xbox One gaming console remained boxed up while we lived in temporary accommodation. When we unpacked the console after the second move it failed to power on. ☹️
A while back there was a forum post on the Community Forum asking how to stop the Vendor ID from automatically populating with the previously entered Vendor ID when entering Payables Transactions.
This functionality can be useful when entering multiple transactions from a single vendor, but can also cause data entry errors if entering a transaction from a different vendor and the ‘Vendor ID’ is not changed.
At first glance I thought it would simply be caused by the ‘Vendor ID’ field on the window having the object property of SavedOnRestart=True. However, that was not the case.
Back in October when Microsoft Dynamics GP 18.4 (October 2021) was first released, a problem was identified that affected Australian customers. This was discussed in the article:
This previous crashing issue was caused by a version mismatch on the Visual Studio Tools Addin DLL that provides the ABN (Australian Business Number) Lookup via a webservice to the ABR (Australian Business Register).
Read more »
With the release of Microsoft Windows 11, the hardware requirements for supported PCs took a jump from previous versions of Windows.
In particular, the requirement for Trusted Platform Module (TPM) 2.0 and a modern 64 bit CPU have caused a number of machines to not be eligible/supported to run Windows 11.
In my previous article: #MSDynGP Microsoft Dynamics GP and SMTP Email Failing, I mentioned that it was possible to check and/or change settings for your Exchange Online client.
There are a number of settings which can only be changed using PowerShell as they don’t have any user interface options available. However, many of the articles that provide the details on the settings never say how to actually get PowerShell working to use the settings.
This is where this article comes in …..
Over the last month or so many users have been reporting intermittent issues with sending emails failing with SMTP (Simple Mail Transfer Protocol) authentication failures.
The issue occurs when using Microsoft’s Exchange Online (part of the Microsoft 365 suite) as the email service. It is caused by Microsoft’s policies to improve authentication security for the Exchange Online service.
In my previous article I discussed a method I have developed for Iterating through a Dexterity Scrolling Window.
This technique is something that has been requested many times as working with scrolling windows from the user interface side has always been extremely difficult. Especially when trying to reference it as a VBA (Visual Basic for Applications) or VS Tools (Visual Studio Tools) “Grid”.
This article provides a real life example implemented using GP Power Tools (build 28 or later).
Over a year ago, October 2020 to be exact, I mentioned on a forum post that I have finally worked out how to cycle through a scrolling window using Dexterity code.
Being able to perform an action for each line in a scrolling window has been something that Microsoft Dynamics GP developers have been trying to do since VBA was added to version 4.0 of GP and Visual Studio Tools was added to version 9.0 of GP.
I promised I would blog about this technique … so read on for the details.
Over the last few days I have received a number of requests for clarification of the status of Winthrop Development Consultants’ products and whether they are at risk from the Java Log4J vulnerability that has been in the news recently.
The short answer is no.
For those who would like a bit more information read on…
Winthrop Development Consultants are proud to be one of the sponsors of the K2A Days & GPUC event running in Fargo, North Dakota, USA (the home of Microsoft Dynamics GP) this week.
The event is hosted by Implementation Specialists and for the first two days focusses on Key2Act (formerly Wennsoft) customers with the final three days covering everything Microsoft Dynamics GP.