A recent customer who upgraded to Microsoft Dynamics GP 2010 wanted to enable the email functionality to allow them to email creditor remittances out rather than having to print them out and sending a hard copy.
As our support account did not have an associated Exchange email account on their system I was getting errors when loading the forms used in this new functionality. So rather than risk problems due to these errors, I put together a quick document for their IT department to enable it themselves. I thought it might also be useful to create an internet version to refer other customers to if they want documentation. Continue reading “Feature Explained: How To Configure The Document Email Functionality”
On Developing for Dynamics GP David Musgrave has announced the release of the Support Debugging Tool Build 15
Build 15 introduces lots of new functionality as well as many fixes and improvements. Available from PartnerSource (login required)
We use eConnect to post journals from external systems into Microsoft Dynamics GP. After working fine for over a year, a customer site recently had transactions posted via eConnect vanishing.
There were no entries in the Journal messages under eConnect_Incoming Private message queue in Computer Management or in the eConnect section of the Windows Event Viewer. Once the message had left the client machine no trace could be found.
Continue reading “Journals Submitted To eConnect Vanishing”
Following on from yesterdays post about the Undefined Symbol error, where I discovered that Microsoft have removed the link from the check remittance tables to PM Creditor Master, I thought it might be useful to post the VBA workaround used to get the creditor address.
The first step was to create five Calculated Fields on the Check Remittance report; for simplicity I named them CreditorAddress1 through CreditorAddress5. No separate field for Post (Zip) Code was created as addresses can be of all different lengths and I like to output tidy addresses where I can.
Once the fields were created and added to the report, in the Remittance Header section, they were selected and made available to Visual Basic. Continue reading “Check Remittance Vendor Address VBA Workaround”
The customer I recently upgraded from Microsoft Dynamics GP 10 to GP 2010 have encountered an error during the payment run at the cheque remittances step;
Continue reading “Check Remittance Undefined Symbol Error When Upgrading to Microsoft Dynamics GP 2010”
One of my biggest problems with the SmartList in Microsoft Dynamics GP is the size of the two panes. The left hand pane resizes itself when you change the size of SmartList; when maximised it ends up being two fifths of the screen size which seriously cuts down the space for viewing the report.
But, now, help is at hand. Frank Hamelly, a Microsoft Dynamics GP MVP, on GP2themax has posted a modified SmartList window, from Nicole Albertson of Microsoft, which resizes the left pane.
The modified window is loaded in via Customisation Maintenance (Microsoft Dynamics menu » Tools » Customise » Customisation Maintenance) from a .package file and works by keeping the left pane a set size which maximises the pane showing the report data.
Hopefully, the next version of Microsoft Dynamics GP will come with a built in solution to this.
I have just returned from customer site where I did an upgrade of Microsoft Dynamics GP 10 to Microsoft Dynamics GP 2010 (I wish they’d called it GP 11 as the current nomenclature confuses customers) and got the error I often get when upgrading or installing GP on Windows 7 or Windows Server 2008 systems and have forgotten to do one of two very simple things. The explanation of the two things later, but first, the error message;
Continue reading “Microsoft Dynamics GP 2010 Utilities: BCP Utility Error”
Microsoft have recently been expanding on the roadmap for Microsoft Dynamics GP “12” (expected to be launched as Microsoft Dynamics GP 2012). One of the features which most interests me is the Named System Database Architecture. Continue reading “Dynamics GP “12” – Named System Database Architecture”