With sites using Microsoft Dynamics GP over Citrix Presentation or XenApp, where they have set Citrix to time users out after a certain period of inactivity, we occasionally see the following error message when another user tries to open the voucher in Payables Transaction Entry ( );
In Microsoft Dynamics GP 2010, Microsoft introduced the Reporting Ledger functionality which allows journals to be posted to one of three reporting ledgers; base, local, or International Financial Reporting Standards (IFRS).
This functionality is controlled via the General Ledger Setup window ();
As the post title says; there may be a disruption in how often I am able to post to this site over the next few days and, perhaps, weeks.
The reason is that I start a new job today.
Over the last eight years I have worked as a support analyst, a senior support analyst and as a finance consultant for a Microsoft Silver Partner in the NW of England dealing with Microsoft Dynamics GP.
As of this morning, I am starting a new job as a consultant for a Microsoft Gold Partner in the NE of England dealing with Microsoft Dynamics GP but also with the potential for learning some Microsoft Dynamics CRM.
I intend that the subject matter remain mainly with Dynamics GP but I will include anything of interest from Dynamics CRM that I come across.
I hope you’ll bear with me through any disruption and don’t forget about me 🙂
As well as using eConnect to integrate journals from an external system into the GL, we also use it to integrate invoices into Payables Management. Overall we have far fewer problems integrating transactions via eConnect than we had in the past using Integration Manager, but we do still encounter some problems; usually with transactions being posted in the external system and then disappearing.
This is sometimes a more exotic reason but is usually an issue with the eConnect service needing to be restarted. When we first started using eConnect we often had problems when the server was rebooted as the eConnect service was starting before the MSMQ service and didn’t then function correctly.
To fix this issue we added a dependency to MSMQ on the eConnect service which ensures the eConnect one does not start until MSMQ is ready. This particular fix has just resulted in a site posting invoices in an external system which didn’t arrive in Microsoft Dynamics GP. Continue reading → Integrations Via eConnect Disappearing
In this post I discussed fixing a Sales Invoice which was corrupt and how Microsoft Dynamics GP Check Links couldn’t be used to fix the problem as it only looks at the standard tables but the invoice in question was a recurring invoice created using Nolan Business Solutions’ Advanced Sales Order processing with recurring Invoices. Continue reading → Mea Culpa: Fixing A Corrupt Sales Invoice
David Musgrave asked this morning if I could supply a detailed RSS feed.
Well, ask and ye shall receive. We now have two RSS Feeds (Summary and Detailed):
These links are available in the footer of every page.
I was on site today to do a sales demo of a couple of new modules to an existing client. At the end of the demo, the new Head of Finance had a word with me about the Aged Debtors report which was not working correctly.
He showed me a copy of the report and all invoices, regardless of the transaction date, were showing in the Current Period. My first thought was that the Aging process (Microsoft Dynamics GP menu ¯ Tools ¯ Routine ¯ Sales ¯ Aging) had not been run; a hurried think for other options drew a blank. Continue reading → Aged Debtors Report Problem
One of the undocumented features of Microsoft Dynamics GP is the ability to use a custom splash screen.
The standard splash screen displayed by Microsoft Dynamics GP 2010;
Well, I’ve just finished installing SQL Server 2008 R2 and Microsoft Dynamics 2010 R2 on the Windows 8 Developer Preview and GP is exactly like it is on Windows 7. Continue reading → Microsoft Dynamics GP 2010 R2 On Windows 8 Developer Preview
Before instaling the Windows 8 Developer Preview onto my laptop I first tried installing it into a virtual machine.
It was doing this install which introduced me to the “user friendly” BSOD;