This post is a bit of a “blast from the past” which I am posting as it seemed quite hard to find and you never know when I’ll need it again.
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).
He somehow slipped it out without me noticing, but David Musgrave of the Developing for Dynamics GP blog released Support Debugging Tool Build 17 before Christmas; this is the build which added support for Microsoft Dynamics GP 2013.
He was back yesterday with a hotfix release to fix a couple of issues.
Partners can download SDT from PartnerSource (login required); if you’re a customer you’ll need to contact your partner to obtain it for you.
David has links to SDT for Microsoft Dynamics GP 10 and 2010 here.
As well as rebuilding a corrupt GL00105, the Toolkit within the Professional Services Tools Library (PSTL) can be used to recreate SQL objects such as SQL Indexes or the Dex stored procedures.
A while ago I posted a script that could be used to fix a corrupt Account Index Master (GL00105). However, the Toolkit within the Professional Services Tools Library (PSTL) can be used to do the same thing without resorting to a custom script.
After installing the Professional Services Tools Library earlier this week, I’m doing a series of posts on the different functions available, for free, within.
This post covers the Copy Shortcuts options. This function allows shortcuts to be copied from on user to another.
Now that the Professional Service Tools Library (PSTL) has been installed it’s time to take a look at some of the functionality available.
The first one I’ll look at is how to disable a database so users cannot log in. Without using PSTL, to deactivate a database requires you to use the User Access window (
) and select each user in turn and uncheck the company to be disabled. If you have more than a handful of users, this can take a long time to do but with PSTL all users can be disabled very quickly.
As I mentioned in the last post, Microsoft Dynamics GP Support Blog announced that the Professional Services Tools Library had been made free of charge and can be downloaded from here (PartnerSoruce login required; Customers will need to contact their partner). The free PSTL is only available for supported versions of Microsoft Dynamics GP so if you are not using 10 or 2010 you will need to upgrade.
I thought it might be useful to do a short series of posts highlighting some of the PSTL tools and what you can do with them, so to start with I thought a post on how to install the module.
Earlier this week I posted about a bug in Integration Manager where it added extra zeros into the phone and fax number fields when importing creditors. Well, the same bug also affects debtors but a similar script to update debtors via a CSV is also possible.
I was doing some work for a client recently where we were loading lists of new creditors into Microsoft Dynamics GP from CSV files via Integration Manager. There is, however, a bug in IM 10 where it adds extra zeros to the phone and fax number fields of both creditors and debtors. These extra characters are, rather bizarrely, not always at the end but can be interspersed in the phone number.
The easiest work around was to put together a SQL script for loading the phone and fax numbers from CSV file which I did while on site which updated only a single address on the PM Creditor Master (PM00200) and PM Address Master (PM00300) tables.
David Musgrave has released build 16 of his Support Debugging Tool. Full details of the changes are available on the Developing for Microsoft Dynamics GP blog.
There are two updates available;