Click here to
Subscribe to
our Newsletter
This is a reposting of an article I originally wrote on my Developing for Dynamics GP blog.
A while ago I posted an article on Modifying Microsoft Dynamics GP 2010 Word Templates which demonstrated the basic methods for customizing word templates for Microsoft Dynamics GP 2010.
This is a reposting of an article I originally wrote on my Developing for Dynamics GP blog.
This is a follow up post to my earlier post, which demonstrated how Report Writer when combined with the power of Visual Basic for Applications (VBA) was able to create a customisation that would not have been possible with Report Writer alone.
This is a reposting of an article I originally wrote on my Developing for Dynamics GP blog.
A few months ago, I worked on a support case where we needed to add a barcode to a Sales Order Processing transaction print out. We were able to achieve what we needed using Visual Basic for Applications (VBA) to handle some of the scripting for us. I have been meaning to write a blog post on how to make a customization like this for a really long time and have finally got around to it.
This is a reposting of an article I originally wrote on my Developing for Dynamics GP blog.
Alright, maybe I am stretching the truth a little, but I do get frustrated when people discount the Dynamics Report Writer as a useful tool. [Edit] I am not biased at all…. honest.
This is a reposting of an article I originally wrote on my Developing for Dynamics GP blog.
One of the most common customisations outside of North America is changing the Phone Number Format. The North American default format of (XXX) XXX-XXXX Ext. XXXX is not always suitable for other countries.
This is a reposting of an article I originally wrote on my Developing for Dynamics GP blog.
I recently responded on a forum post which asked why the paths for the custom forms and reports dictionaries in the Dynamics.set launch file where pointing to the Data folder. The post also asked why the application did not complain about the fact that the dictionaries listed in the Dynamics.set did not actually exist in the Data folder.
So, I thought it would be a good excuse to answer the questions raised as a blog post.
This is a reposting of an article I originally wrote on my Developing for Dynamics GP blog.
Over the years, I have seen a huge amount of effort and multiple calculated fields to format a date field on a report into a desired format that is something other than the default short date format, usually DD/MM/YYYY or MM/DD/YYYY depending on country (as defined in the control panel).
This is a reposting of an article I originally wrote on my Developing for Dynamics GP blog.
Last week, I discussed an issue where Currency values returned by VBA to a report are multiplied by 10 or 100. To workaround the issue we used string calculated fields rather than currency calculated fields on the report and formatted our values with the FormatCurrency() or FormatNumber() functions (depending on if we wanted the currency symbol or not).
This is a reposting of an article I originally wrote on my Developing for Dynamics GP blog.
Today, I wanted to highlight an issue that you might see when working with Visual Basic for Applications (VBA) and Report Writer.
The issue occurs when using VBA code to return a currency value to be displayed on the report and it appears to be randomly multiplied by 10 or 100. This is a known issue (Problem Report 59380) and this post should help explain what the problem is and provide an alternative solution.
This is a reposting of an article I originally wrote on my Developing for Dynamics GP blog.
Today, I had a support case that was asking about errors when importing a package via Customization Maintenance (Microsoft Dynamics GP >> Tools >> Customize >> Customization Maintenance). The partner was unable to find an explanation of the errors on the Internet and so I thought I would explain what the errors mean and provide some best practices to avoid these issues in the future.