Category: GP (Great Plains)

this is a simple script, but I’ve written it about four times now so I figured I’d post it so I can find it easily next time I lose my local copy.

Perfect Image are resellers of the Advanced Bank Reconciliation module from Nolan Business Solutions (along with the other add-ons they’ve written for Dynamics GP) and I often need to demo this replacement for the standard Bank Rec module.

One item I typically show is the auto-Propose function which matches transactions against statement lines in the Reconcile Bank Transactions window (Transactions » Financial » Advanced Bank Reconciliation » Reconcile Bank Transactions).

To do this I need to be able to import statement lines which match the transactions in Dynamics GP; the easiest way of doing this is to extract the transactions.

This can be done with a very simple SQL script:

SELECT
   ORPSTDDT
   ,ORDOCNUM
   ,TRXAMNT
   ,SOURCDOC
FROM
   NCABR012

Once the data has been extracted it can be imported during the demo using the standard ABR Import Statement routine.

Microsoft Dynamics GP includes a large number of reports which will automatically print off when a transaction or batch is posted; and some postings produce many different reports.

When I implement a new client I typically leave them on during training with an instruction to identify which ones they want to use after go-live as I will switch off any I’m not told to leave on.

I used to do it the other way and tell people to let me know which ones they wanted switched off; however, this lead to all reports being left on and then it being mentioned a year or so down the line that they get all these reports printing that they don’t want.

So now, all get switched off unless I am specifically told to leave them on. As I’ve dealt with clients with many companies (I think the largest is 180 companies) this is not something I want to do manually.

Fortunately, the settings for whether the reports should print is stored in SQL table which means a SQL script can be written to switch them off in bulk.

Continue reading “Deactivate All Reports (Except PM EFT Payment Register) In All Companies”

I was working with a client the other day with Integration Manager to import some purchase orders when we received the following error on some of the purchase orders:

The vast majority of the documents integrated without problem. When we examined the documents which failed, we determined that those which failed were those which had a currency of Euro.

Integration Manager errors are typically very unhelpful and this was no different; the first thing we checked was to see if the PO Number existed in GP, but as we expected it did not.

We did some investigating and found that the Euro Exchange Rate’s Transaction Rate Default in GP was defined as Exact Date; I was able to update this to Next Date after which the integration stopped producing errors.

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.

And it did; I found an old post from David Musgrave on the Developing for Dynamics GP blog where he covers how to change the font used for Text reports.

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
Tolerance=-1
MinMilHeight=100

After installing Microsoft Dynamics GP in a new test system, I then installed Integration Manager and tried to run an integration to test.

After clicking the Run button the following message popped up:

Integration Manager: The destination could not be initialized due to the following problem: -Input string was not in a correct format

This error is typically one seen when Microsoft Dynamics GP is not running (I’ve seen it at a few clients running Citrix when they have Integration Manager running on one server and Microsoft Dynamics GP on another), but I had Microsoft Dynamics GP open in the background.

I quickly realised the problem; I had imported some modified reports into GP which contained VBA and to avoid an error I had right clicked and used Run as Administrator when starting Microsoft Dynamics GP, but had started Integration Manager normally.

This meant the two applications were running in different states and Integration Manager could not see Microsoft Dynamics GP.

To resolve the issue I closed Integration Manager and reopened it using the menu in Microsoft Dynamics GP (Microsoft Dynamics GP menu » Integrate » Integration Manager); this is the way I typically recommend clients open it in order to avoid this problem on Citrix XenApp or other ways of publishing applications.