A client on Microsoft Dynamics GP 10 (we’re talking to them now about an upgrade to GP 2015) is in the process of setting up a new company and needs to be printing out a few of reports (SI, SR, PO and Remittance) with different logos for the new company.
If you’re a long new GP user you’re probably used to the Word Templates which have the logo supplied from the library in Template Configuration () or by assigning different Word Templates to the different companies.
However, as longer time GP users are aware, the Word Templates were introduced in Dynamics GP 2010; before that all reports were produced using the modified reports created in Report Writer where it wasn’t really possible to have different logos.
That is, it wasn’t possible to have different logos in the same place. Way back in 2008 David Musgrave (while a Microsoftie) did a post on the Developing for Dynamics GP blog on how to have a conditional logo on the modified report by using a conditional field to show or hide logos.
It’s not really a solution that can be called elegant (hey it involves Report Writer!), but it was most certainly a useful one. So until this client gets their upgrade performed (hopefully first quarter 2015) I need to get their modified reports customised to hide the logo for their main company when producing documents and the exact steps had faded from memory somewhat.
So I needed to hunt out the old post I remembered David writing (I also remember using it back in 2008) and it actually took a little finding (found it through a question on the Community Forum).
I had a curious one a few months ago (which I forgot to post). A client I was implementing Microsoft Dynamics GP for encountered a problem whenever they printed a report; all of the text was overlapping:
If a document was printed from Microsoft Word it was fine; if a GP report as printed to XPS and then sent to the printer from there then it was also fine. It was just the reports printed directly from Microsoft Dynamics GP which had the overlapping text problem.
Doing some more testing I was able to narrow the problem down further, from thinking it was all GP reports, to only the text based reports. Not having seen this problem before I thought a quick online search might find me an answer.
By using the information in David’s post to update the settings in the dex.ini file I was able to resolve the problem.
I added the following lines to the dex.ini file on each client (and left notes with the client’s IT department so they could do this on any new installations):
FontCourier New=Lucida Console
In Microsoft Dynamics GP 2010, Microsoft changed the underlying tables used by the Check Remittance; I believe this was for purposes of efficiency. However, the downside is that the table, pmRemittanceTemp, used to replace PM_Payment_WORK did not contain the vendor’s address or a link to a table which did.
In the past I have tended to use VBA to add the vendor’s address to the Check Remittance because it was quick and easy to do and I didn’t revisit this approach until Microsoft Dynamics GP 2013 was released. And the reason I revisited, was because of the new Web Client which does not support VBA customisations.
As always, I figured I might as well do a blog post about this and had it scheduled in to write when Richard Wheeler asked the question on the Community Forum. So, here is the step-by-step guide to adding the vendor address back onto the Check Remittance modified report.
I have received a copy of the newly published Microsoft Dynamics GP 2013 Reporting, by David Duncan and Chrisopher J Liley, from Packt Publishing to review. This is an update of a previous book the pair wrote for Microsoft Dynamics GP 2010:
The book covers an extensive range of the reporting tools in, or available with, Microsoft Dynamics GP 2013:
- SmartList Builder including Excel Report Builder
- Report Writer and Word Templates
- Reporting Services Reports
- Analysis Cubes
- Management Reporter
While importing a customised Form with VBA I encountered a problem and received a Component write exception;
The form itself had imported but the VBA element had not.
Not having seen this error before I hit up Bing and soon found a blog post from Dex Master David Musgrave where he discusses this exact issue on GP9 (I was loading a customisation from GP9 to GP 2010 to upgrade).
The answer was not quite what I wanted. I was hoping for something nice and simple, but instead I needed to export all the customisations, delete the forms.dic, reports.dic and dynamics.vba files and then reimport all of the customisations.
After I did this the import worked fine.
At the end of December, Developing Microsoft Dynamics GP Business Applications, written by Leslie Vail and published by Packt Publishing was released.
I got a copy of the book in order to do a review and have decided to break the review down into multiple parts. The reason for this is that the book includes some practical examples which I have decided to do and then include the results of this in the review; after all if it is a book on developing how can you accurately review the book if you don’t use what you learn to build something?
The book is aimed at developers new to working with Microsoft Dynamics GP, so bear in mind that I am not a developer when reading my reviews. Quick synopsis of my background: I started my career as a trainee developer and moved through a variety of roles such as developer and support analyst before moving to my current position as consultant and project manager.
I oversee development teams working on additions or amendments to Microsoft Dynamics GP as well as personally undertaking some modifications using Report Writer or Modifier with VBA. So despite not being a developer, I am used to working with them and did, once upon a time, be one myself.
The first chapter of the book covers the Microsoft Dynamics GP Architecture from a high level perspective.
It covers the history of the GP interface from it’s origins with Great Plains Software, an overview of Dexterity and the development environment. There is a detailed explanation of the launch file (Dynamics.set), which included a couple of points of which I wasn’t aware, and the configuration/preferences file (Dex.ini).
The explanation of the Dex.ini file included the ExportOneLineBody switch which I didn’t know about, but for which I have an immediate use.
Leslie then goes on to explain about the structure of the tables in the SQL Database which always strikes newcomers as arcane and overly complex. Leslie explains this well with plenty of detail on both the structure, including both the physical and technical names, and how transactions move between tables as their state changes.
Chapter 1 wraps up with a detailed explanation of the UI covering how forms are constructed, how the scrolling windows work and the common buttons used on forms, scrolling windows and individual buttons.
The second chapter of the book focuses on the fundamentals of integrating applications with Microsoft Dynamics GP.
I was recently asked to assist the Support team to look into an issue with the Trail Balance Summary modified report. The problem was that when sent to screen or printer the report was fine, but when exported to Tab Delimited file, the columns didn;t match up with the totals at the bottom.
Trial Balance Summary on Screen shows as aligned;
Microsoft have started the Microsoft Dynamics GP 2013 Feature of the Day series on the Inside Microsoft Dynamics GP Blog.
The twelfth feature they’ve announced is Additional Word Templates.
Microsoft Dynamics GP 2010 introduced the Word Templates as alternatives to the standard Modified Reports but the selection available was limited. In Microsoft Dynamics GP 2013, users can now use Word Templates for all Sales Order Processing document types (such as Back Orders) as well as Packing Slips and Picking Tickets;
I’ve recently been working on a Microsoft Dynamics GP 2010 implementation project for a client.
We created custom Word templates () for POP Purchase Order Blank Form, SOP Blank Quote Form, SOP Blank Order Form and SOP Blank Invoice Form without problems and granted access to the relevant companies.
To test the new Word templates we printed the documents to screen so we could quickly see the result. The POP Purchase Order Blank Form worked fine but when it came to the SOP documents we had a problem. When printing any of the SOP documents as Word Templates, instead GP printed the Standard Report Writer reports. Continue reading → Problem With SOP Word Templates
I installed Microsoft Dynamics GP 2010 R2 onto my work laptop a few weeks ago, just after I started working for this company.
I needed a demo environment and so installed the most recent version. I’ve been getting an error since that time whenever I switched back from Report Writer to GP itself;