GP Power Tools is a subscription based product. This means it needs current, valid Registration Keys to stay operational.
If you have written Mission Critical Custom Code using GP Power Tools – Developer Tools module, you will want to ensure that those triggers and scripts stay active at all times and if the registration fails for any reason that you are notified immediately.
Community Summit Conference 2021, hosted by Dynamic Communities (DC) ran in Houston, Texas, USA last week from 12th to 15th October 2021.
I presented a session on Microsoft Dynamics GP development tools. Because I am still unable to leave Australia due to the pandemic border closures, the session was a pre-recorded video presentation.
Community Summit Conference 2021, hosted by Dynamic Communities (DC), is happening right now in Houston, Texas, USA until from 12th to 15th October 2021.
I am presenting a session on Microsoft Dynamics GP development tools as the first session of the day on Friday. As I am still unable to leave Australia due to the pandemic border closures, the session has been pre-recorded and will be run as a video presentation.
However, I will be online in a Microsoft Teams Meeting for the duration of the session and would love for anyone attending the conference (and those just interested in GP Development) to join me and others in the community for a chat and Q & A session.
Over the last couple of months I have been seeing a huge uptake on the sale and use of GP Power Tools – Development Tools module as more and more Microsoft Dynamics GP customer sites move their customizations away for the now “End of Life” Visual Basic for Applications (VBA).
This article explains some of the differences and techniques for the common method driving the user interface using code written in VBA, Dexterity and Visual Studio Tools (C# or Visual Basic .Net).
Dynamic Communities (DC), the team behind GPUG, will be hosting their Community Summit Conference on 12th to 15th October 2021. The agenda with sessions has now been posted online and I will be presenting a session on Microsoft Dynamics GP development tools.
The Dynamics User Group (DUG) will be hosting its DynamicsCon Conference on 20th to 23rd September 2021. The agenda with sessions has been posted online after the session voting and selection has been completed and I will be presenting a session on Microsoft Dynamics GP development tools.
Today is the last day to vote for your favourite DynamicsCon conference sessions ahead of the conference scheduled for 20th to 23rd September 2021.
Make sure that you register and apply your 12 votes today to shape what you want to see at the conference.
The next installment of DynamicsCon conference is scheduled for 20th to 23rd September 2021. The session submission period is over and now we enter the session voting period until 28th July.
During this voting period all registered attendees have 12 votes to apply to sessions as they wish, then the votes will be tallied and the final session lists published. See this explanation for more details of the process.
I have been fairly quiet recently on the blog and forums as I have been concentrating on developing the next build of GP Power Tools. All I can say is that it is awesome and you will love it. I have a “Sneak Peak” article coming soon.
While working on the development and testing process, I had some unusual behaviour from my .Net Visual Studio Tools Addins and spent an entire day troubleshooting the issue so I could identify the cause and work out a solution. Read on for the gory details….
Following on from the previous articles: #GPPT Speeding Up Referencing Modifier Added Fields and staying Web Client compatible and #GPPT Referencing Modifier Added Fields in the Web Client using .Net Execute, this article looks how we can use VB.Net rather than C# as the scripting language in the .Net Execute scripts.
Both VB.Net and C# use the .Net Common Language Runtime (CLR) and it is usually possible to write exactly the same code in either language. So we will duplicate our existing C# scripts and convert them to VB.Net, then we will duplicate the triggers to call the new scripts.
Using the method discussed in the article #GPPT Referencing Modifier Added Fields in the Web Client using .Net Execute it was possible able to get past some of the limitations mentioned in the article Dynamics.Application Object not available on Web Client.
However, running the .Net (C# or VB.Net) code is slightly slower than running the Dexterity (sanScript) code. This article explains a method of how to improve Desktop Client performance while staying compatible with the Web Client.
You probably saw the recent article: Dynamics.Application Object not available on Web Client where I described an issue that was recently discovered and meant that the “Continuum” based triggers and scripts used to reference Modifier Added Fields in GP Power Tools – Developer Tools module were unable to work in the Web Client.
I mentioned a workaround that would function with the current GP Power Tools code when running on the Web Client (and Desktop Client). This article will show how you can use scripts in the .Net Execute Setup window to reference Modifier Added Fields.
This article comes about because we have identified a feature of GP Power Tools that does not work as expected on the Web Client. GP Power Tools has the ability to run scripts and register triggers against Modifier added fields and Modal Dialogs. These features uses the Dynamics.Application object and in particular a suite of functionality historically known as “Continuum”.
We can now confirm that the Dynamics.Application object is not available at all when running Microsoft Dynamics GP in the Web Client and so any functionality reliant on this object will fail to work.
As a follow on to the recent post : #GPPT Why every GP site needs GP Power Tools – Developer Tools, this article explains the benefits of replacing your VBA (Visual Studio for Applications) and VSTools (Visual Studio Tools for Microsoft Dynamics GP) customizations with GP Power Tools.
It has been prompted by the issues seen because the redistributable version of VBA that is packaged with Microsoft Dynamics GP has reached end-of-life as explained in the following articles from the Microsoft Dynamics GP Support and Services team:
The release of Build 15 of the free product Visual Studio IntegrationToolkit is a bonus to Visual Studio Tools for Microsoft Dynamics GP developers around the globe.
As well as the enhancements to the Menu Navigation functionality and the addition of support for custom Area Pages, Build 15 adds a new Helper functions module with over 220 functions.
This build is the result of a month’s development effort and is why you have not heard much from me on the blog recently.
You might have seen my posts on Twitter and Facebook recently about my new
toy mini laptop PC, the crowd funded GPD Pocket 2.
I have been burnt before with crowd funded projects (I supported 3 smartwatches and only one make it to production and it under-delivered 😦 ), so I was wary of getting involved again. However, this was the second generation of the GPD Pocket and demo devices had already been delivered to a number of YouTube reviewers. I felt fairly safe to get involved with crowd funding again, as this would give me a discount and get the device earlier.
I recently had issues with one of my products and need to share the cause of the issue and the solution with the Microsoft Dynamics GP development community.
I made changes to all my products late last year, introducing a new registration system. The code uses Visual Studio Tools for Microsoft Dynamics GP addin DLLs written in Visual C# to handle all the communication with the appropriate registration server.
With the addition of Service Based Architecture (SBA) into Microsoft Dynamics GP 2015 and later, Dexterity global procedures can be marked as Service Enabled.
This allows a Dexterity global procedure to be a Service procedure which is exposed as a REST based web service via Service Base Architecture.
I am writing this article after seeing the side effects of Visual Studio Tools developers not following Best Practice when adding references to their projects.
Two mistakes made by the developer in this example resulted in Microsoft Dynamics GP failing to launch with the “An exception occurred while trying to load or initialize the addin” error.
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.
Use the tool to post newly integrated transaction batches real time using calls from Dexterity, Visual Studio Tools or as a Service Based Architecture (SBA) Web Service (for v14.0 or later).