I recently posted a method of repurposing the Microsoft Dynamics GP 2018 R2 Intelligent Cloud Insights page to show a website of your choice.
However, if you are running an earlier version of Microsoft Dynamics GP you also have the option to display a custom website by repurposing the Connect pane on the user’s Homepage.
This is the index article for my series about setting up and working with your Dexterity Development Environments.
Disclaimer: This is the Musgravion principles of development machine setup. It is not the only method but it has worked for me for many years and has been fine tuned during my career. Feel free to use it if it works for you.
This is the seventh article in my series about setting up and working with your Dexterity Development Environments.
If you have not read the previous articles, please do so first using the links below:
This is the sixth article in my series about setting up and working with your Dexterity Development Environments.
If you have not read the previous articles, please do so first using the links below:
This is the fifth article in my series about setting up and working with your Dexterity Development Environments.
If you have not read the previous articles, please do so first using the links below:
Another reason for the lack for articles recently is that I have been working on a hotfix for GP Power Tools.
Developers…. make sure you read the last bullet point in the list below. No more SDK woes.
A hotfix for GP Power Tools Build 22 was released on 19-Jun-2017. This release shows as Last Modified: 19-Jun-2017 on the About GP Power Tools window and the installer version is XX.00.0022.7.
This is the fourth article in my series about setting up and working with your Dexterity Development Environments.
If you have not read the previous articles, please do so first using the links below:
This is the third article in my series about setting up and working with your Dexterity Development Environments.
If you have not read the previous articles, please do so first using the links below:
This is the second article in my series about setting up your Dexterity Development Environments.
If you have not read the previous article, please do so first using the link below:
This article has been a long time coming and is the first of a series of articles on how I set up my machine for developing Dexterity applications across multiple versions.
I promised I would detail how my system is set up a while back at the reImagine 2015 conference and had never got around to writing the article until now.
In case you missed it, yesterday was Fabrikam Day for the Microsoft Dynamics GP community. This was the 12th April 2017, the date that the sample company’s, Fabrikam, data is based around.
For more information about Fabrikam Day and the sample company have a look at my article from yesterday:
After months of work, I am extremely excited to announce that GP Power Tools for Microsoft Dynamics GP (GPPT) Build 22 is now available for download. Please update your systems to get all the new features.
GP Power Tools was previously known as Support Debugging Tool (SDT), which was discontinued in October 2014. If you are still using the previous product, please upgrade to the supported and much better GP Power Tools product.
In the last eight years, there have been an increasing number of display issues when using Microsoft Dynamics GP on high resolution monitors. There are a number of different factors coming into play which cause Dynamics GP to display incorrectly.
This article explains the issues, their causes and their solutions and finally explains how GP Power Tools makes the solutions extremely simple to implement.
[Edit] FYI: Build 29 of GP Power Tools automatically applies the fixes during installation.
I am pleased to announce that the next build of GP Power Tools for Microsoft Dynamics GP (GPPT) is now available for download.
GP Power Tools was previously known as Support Debugging Tool (SDT), which was discontinued in October 2014. If you are still using the previous product, please upgrade to the supported and much better GP Power Tools product.
For the Visual Studio Tools for Microsoft Dynamics GP developers out there, I am pleased to announce that the next build of the Visual Studio Integration Toolkit for Microsoft Dynamics GP (VSIT) is now available for download.
The Visual Studio Integration Toolkit was previously known as Menus for Visual Studio Tools (MVST), which was discontinued in October 2014. If you are still using the previous product, please upgrade to the supported product.
I am pleased to announce that the next build of the Batch Posting Service Toolkit for Microsoft Dynamics GP (BSPT) is now available for download.
The Batch Posting Service Toolkit provides service procedures to retrieve a list of Batch Numbers for a specified Batch Source and to post the batch for a specified Batch Source and Batch Number.
It is designed to be used to post newly integrated batches of transactions real time and can be called via Dexterity, Visual Studio Tools or as a Service Based Architecture (SBA) Web Service (for v14.0 or later).
Service Based Architecture (SBA) was released with Microsoft Dynamics GP 2015, it covers technologies to make Dynamics GP more accessible to external applications by allowing Dexterity global procedures to be exposed as Web Services. It also allows Dexterity code to directly access and use .Net objects via the .Net Interop.
SBA opens up an entire new world of development opportunities.
Today, I am proud to announce the upcoming release of a new product from Winthrop Development Consultants.
Welcome to Batch Posting Service Toolkit for Microsoft Dynamics GP for versions GP 2010 (v11.0), GP 2013 (v12.0 including R2) and GP 2015 (v14.00 including R2).
If you come across the problem below, please download the GP Power Tools Build 20 hotfix 2 which is now available from the Mekorma website.
When using the Configuration Export/Import window to import a configuration settings file created with the Support Debugging Tool into GP Power Tools, it will say that there is nothing to import.
This issue was caused by the changes to make GP Power Tools work with SQL tables rather than with temporary tables written to a Debugger.xml file. It happened because the table names written into the configurations settings file was incorrectly changed so that they had a _TEMP suffix.
If you follow this blog, I am sure you already know that GP Power Tools has been released through my distribution and support partner, Mekorma, for Microsoft Dynamics GP 2010, GP 2013 and GP 2015.
The question I am hearing now from existing Support Debugging Tool sites is:
“Now that GP Power Tools is available, what happens to my Support Debugging Tool installation?“.
Winthrop Development Consultants Blog 