For me, this New Year day is going to be Joyous for two reasons:
1. My Daughter’s First New Year Day.
2. My Blog has been inducted into Microsoft Dynamics GP Community Blogs. Follow my articles from here: https://community.dynamics.com/blogs/gplearn/default.aspx.
Thanking all my Blog Readers & Critics, for your tremendous support. I will work hard to be even more responsible and informative in my articles.
Wishing all a Great 2010 ahead.
VAIDY
This post from Dynamics Confessions blog, informs us about Incompatibility of Dexterity 10.00.320 Build with .NET Framework 3.5SP1.
Those who are working on similar lines, have a look at this article and be informed on what needs to be done in such scenarios.
NOTE: Download Dexterity 10.00.324 Build separately from PartnerSource and install it as soon as you apply GP SP4 on Dexterity. Because this particular Build 324 is the actual SP4 for Dexterity Common Components and Dexterity itself.
VAIDY
This is sort of Confession:
I was completely out of Community Newsgroups for the past month or two, for various pressing reasons. I realized that I missed a lot out of not learning and sharing with Users and Consultants.
Well, I was making a mistake of not participating in Newsgroups which is the wealth of information. Whatever I have gained as a Consultant, most part of it have come from Blogs, Newsgroups and Articles. I should have managed my schedule in such a way that at least an hour each day could be dedicated to Newsgroups, learn & share what I know in GP.
So from today, I will be back again, part of our Community Newsgroups.
VAIDY
This one is very simple yet powerful illustration, on How GP calculates Sales Taxes, from Frank Hamelly on his gpTip42Day.
I am writing an Pointer Article to this inspite of adding gpTip42Day as a Side Bar Link, as this article taught me the actual calculation behind Sales Taxes. I usually assume from the way the amounts are arrived at, but I had never known about the theory behind it.
Must read.
VAIDY
This one may or may not have caught the attention of Consultants. So here you have it.
I was working on a GP 10.0 SP4 installation on the following environment:
1. Windows Server 2008 Standard
2. SQL Server 2008
3. GP 10.0 SP4
4. 64 Bit Environment
I installed SQL Server 2008 first and then installed GP 10.0. When I launched my GP Utilities, the ODBC Data Source to SQL Server was not listed at all. I must admit that I did not search any forums or KB to find out the reason and solution.
But I found this: SQL Server 2008 on Windows Server 2008 R2 must be applied with SP1 mandatorily. This was the reason my ODBC DSN did not get listed in my GP Utilities. I applied SQL2008 SP1 and it worked.
VAIDY
Thanks to Mark Polino for his article, which in turn referred to Original Article from Touchstone’s Blog.
POINT TO NOTE: FRx 6.7 SP11 is not available for downloads at the moment. This has been pulled out due to some bug in it. Will be available in another 4 weeks, hopefully.
UPDATE (22nd DEC 2009): We will still be able to download the SP11 but with bug, if I have understood it correctly. I doubled checked it and looks like we are able to download this. But not sure whether the reported critical bug is resolved or not.
VAIDY
This one’s amazing. Matt Landis introduces to a new Add-on to GP which unites Bing Search and Dynamics GP Customer Maintenance. And there is a video which demonstrates how this work.
I am absolutely amazed, to say the least. And this particular Add-on demonstration shows how GP is flexible and open to do what we wish to.
Good one, Matt.
VAIDY
This one was a real menace for me, to say the least.
One of the Users reported the error message “This document has been posted.” for a particular SOP Document.
The following were the observations:
1. This document was never saved in a batch.
2. GP hung at the time of entering this document.
3. The User killed GP session in order to come out of the Hung Session.
4. User confirmed that he did not enter any Batch while creating this Document.
5. Once restarting GP (after the KILL), he entered the SOP Number (which he had noted down) and received this Error Message.
Following this, I first resorted in clearing all the Activity Records (ACTIVITY, SY00800, DEX_LOCK & DEX_SESSION). There is a KB article, KB#857082, explaining this issue and the resolution. BUT this did not solve the issue at all. I was still getting the same error message again.
I checked the SOP10100 table for the record and found that document residing there. Also in SOP10102 and SOP10200 tables. Now, I did the following:
1. Created an SOP Batch in GP.
2. Updated the SOP10100 record for that document with the Batch Number that I created in GP.
3. Tried opening the document, but in vain. Still the same error.
4. Checked several updates but to no avail.
After quite an amount of frustrating time, SQL Profiler and Dex Script Log, I found the following:
Batch Source (BCHSOURC) field of table SOP Header Work (SOP10100) MUST NOT BE EMPTY. It has to be “Sales Entry” (Note the Cases; It has to be exactly “Sales Entry“). If the Batch Source field is empty, GP understands that this document is a Real Time document and that it should not be residing in SOP Header Work table at all.
Alright, after I updated this field, I am good to go to open that stuck SOP Document.
NOTE: Always in scenarios like this, delete the SOP Document and recreate it. It’s not advisable to amend anything to this released SOP Document. We never know what else would be wrong with such documents.
Happy Debugging; What else could I say !?!?! :-).
VAIDY
Dynamics GP - Learn & Discuss 