This is another mea culpa post; I’ve been doing enough of them I’m thinking of giving them their own tag.
I was created a virtual machine with the Fabrikam, Inc. demo company in it. When GP Utilities was processing I got this error pop up;
A few days ago the Microsoft Dynamics GP Support and Services blog moved from MSDN to the Microsoft Dynamics GP Community site where it had been syndicated for a while.
Full details of the move are here
Today, on the Developing for Dynamics GP blog, David Musgrave starts a series of posts on the Support Debugging Tool which is definitely going to be worth reading.
The series starts with a post on understanding the logging modes.
I was doing some testing to compare the SSRS Trial Balance against the standard report version but ran into a problem straight away when I found the SSRS version returned no data.
A quick search online found me this post SSRS: GL Trial Balance Summary report returns no data – Follow Up by Mariano Gomez where he discussed the exact problem I had encountered.
As Mariano says this has been fixed in the upcoming SP3 but for now there is a Knowledge Base article covering a workaround which is to alter the stored procedure (seeglPrintSRSTrialBalance) which is used for returning the data: GL Trial Balance SRS Reports return no data using Microsoft Dynamics GP.
Continuing Mark Polino’s weekly DynamicAccounting.net series of posts recommending an MS Connect suggestion.
This weeks is a vote on allowing a Journal to be composed in Microsoft Office Excel and then copied and pasted into the General Ledger Transaction Entry window. This functionality would be useful for those people who don’t have Integration Manager – Financials.
If you’d be interested in seeing this change made, please go to Connect and vote.
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.
I’m taking a slight detour away from posting the series of how to’s on the Professional Services Tools Library to highlight an installation error that I’ve recently seen when installing PSTL.
A client recently installed PSTL and reported receiving the below error message;
I’d sent them the PSTL download along with the instructions on how to install it without realising that there was a missing part to me instructions (which has now been added).
When installing PSTL into a company for the first time, you must log into Microsoft Dynamics GP as the sa user as there are some tables which get created (covered in KB Article 861564 which is actually a retired article but does mention the issue and the resolution).
Continuing Mark Polino’s weekly DynamicAccounting.net series of posts recommending an MS Connect suggestion.
This weeks is a vote on improving intercompany transactions. While, as Mark points out, the suggestion is a little on the vague side, voting to imProve intercompany will focus Microsoft’s gaze upon the subject of intercompany support.
If you’d be interested in seeing this change made, please go to Connect and vote.
As an aside, I’m at square one house wise now but had my time taken up With a side project (details to be announced soon) but I now aim to get back posting with some regularity.
Mark Polino on DynamicAccounting.net recently started a series of weekly posts recommending an MS Connect suggestion.
This weeks is a vote on reordering the debit and credit columns in SmartLists so they match the ordering in the rest of the system.
If you’d be interested in seeing this change made, please go to Connect and vote.
Mark also follows up with a Microsoft Dynamics Community column discussing how ISVs can benefit from following the voting patterns on MS Connect.
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.