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.
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:
This is a reposting of an article I originally wrote on my Developing for Dynamics GP blog.
GP Power Tools – Administrator Tools Module can provide this functionality without needing customizations. (http://WinthropDC.com/GPPT)
Following on from my previous posts: Customising the Company Login window series Part 1 – Introduction, Customising the Company Login window series Part 2 – Visual Basic for Applications and Customising the Company Login window series Part 3 – Dexterity, here is a discussion about trying to create a solution using Visual Studio Tools.
This is a reposting of an article I originally wrote on my Developing for Dynamics GP blog.
GP Power Tools – Administrator Tools Module can provide this functionality without needing customizations. (http://WinthropDC.com/GPPT)
Recently a comment from David M (not me) was posted on the Support Debugging Tool Portal page asking:
“We have some fairly long names for our GP companies. Well, when logging onto GP, the second “Company Login” screen cuts off the company names too short for us. The entry field for companies allow for longer strings (65 Characters) but only displays 31 characters on the pull-down list. There is plenty of real estate on this window going unused. Can anyone think of a way to enhance/fix this to display more of the company name?”
This is a reposting of an article Patrick Roth originally wrote on my Developing for Dynamics GP blog.
This will be a 2-for-1 post today as the example given solves a frequently asked question and was used to solve a customer issue.
This is a reposting of an article Patrick Roth originally wrote on my Developing for Dynamics GP blog.
One thing we’ve noticed recently is an uptick of cases involving Visual Studio Tools assemblies causing Dynamics GP to crash after being installed.
This is a reposting of an article Patrick Roth originally wrote on my Developing for Dynamics GP blog.
It seems like a trivial subject for our dedicated readers but we had a new customer who is just learning Dexterity and he was having trouble recently trying to select items out of a ListBox. And just today the issue came up about Drop Down Lists (DDL) and getting the value selected using VBA in a different case. So this seemed like a good time to put this together.
This is a reposting of an article I originally wrote on my Developing for Dynamics GP blog.
I was recently asked about a custom button that was added to a window and how to change the internet URL that the button opened when it was closed. I was not provided with any other information or screenshots.
This is a reposting of an article Alice Newsam originally wrote on my Developing for Dynamics GP blog.
One of the features included in the Microsoft Dynamics GP 2013 Service Pack 2 release was the ability to now render Visual Studio Tools customizations in the web client. For those of you that missed the overview session of this feature at the recent Microsoft Dynamics GP Technical Airlift 2013, I thought I’d share some “things to consider” in a post.
This is a reposting of an article Lee Butenhoff originally wrote on my Developing for Dynamics GP blog.
Let’s jump right in. We debug our Visual Studio applications over and over; and attaching to the test environment is among the most important, and time-consuming skills we use. (How many times have I launched GP2010 when I was thinking of GP2013?)
Of course we all simplify our testing by building the dll and pdb files directly in the DynamicsAddins folder (right?). If not, start doing that.
Were that the only thing to learn here, that knowledge alone would be worth the price of admission. But it’s a fairly obvious step, and many of us already send the built dll file to the folder.
This is a reposting of an article I originally wrote on my Developing for Dynamics GP blog.
IMPORTANT NOTICE: Menus for Visual Studio Tools is now Visual Studio Integration Toolkit from Winthrop Development Consultants (http://winthropdc.com/VSIT)
Winthrop Development Consultants Blog 