MSDynamicsWorld.com has got the coverage on Microsoft Dynamics GP roadmap refresh.
It’s quite exciting as well as stunning to know that we are moving towards service based GP architecture.
Dear All Readers,
Most of you might have noticed that my blog suddenly stopped working and was redirecting to some junk “This domain is on back order.” page.
I sincerely apologize to all who would have got disappointed for not being able to refer what you wanted to on my blog.
I’m happy & relieved to say that my blog is now back and is working perfectly.
Kindly continue your support and refer to my blog for whatever you want about Microsoft Dynamics GP. I promise I would ensure that this bad phase never happens again in future.
I received a strange support request today from one of my users that PO number is not shown fully on Purchase Invoice Inquiry Zoom window. Just tried to inquire some purchase invoices myself and I got what she mentioned:
If you see above highlighted PO number, it’s not shown fully. This will be the case only if you use GP’s standard PO number sequence or used entire PO length of 17 characters.
When I checked it on Modifier, I found a nice little icon sitting right next to PO number field, but overlapping it by some millimeters.
This icon denotes whether the PO line item is Drop-Ship or not.
And boy, isn’t that icon looks cute? But unintentionally, it is overlapping on PO number field. Not sure how folks at GP dev team skipped this.
Solution to this issue? Modifier. Use modifier to resize the field, till we get this fixed by GP dev team.
While upgrading our GP from GP2010 SP3 to GP2013 SP1, DYNAMICS database upgrade stopped unexpectedly with GP crashing without any information for me to debug.
But it stopped exactly at table syExcelReports and crashed. Without spending anymore time, I just went and checked my ODBC DSN setup, as explained by Aaron Berquist on his blog High Dynamics Range. Expectedly, the ODBC DSN driver was not pointing to SQL Server Native Client 10.0.
For some reason, GP fails to process upgrade further if your DSN driver is NOT native client 10.0 or above.
Those who upgrade your GP to latest version, please check DSN before you start database upgrade using GP Utilities.
I am late in blogging about this post. But NOW is the time, as this post just saved my 1/2 day. Seriously. Not kidding. I was stuck with one SQL query execution. There were records to be retrieved, but my code didn’t. After 5-10mins of frustrated troubleshooting, I remembered this post. I should have done that immediately then, but I didn’t.
I setup my VS Tools project to launch GP as instructed on this post and within 2 minutes I could find the issue.
This one deserves to be there on Microsoft Dynamics GP Cookbook (technical).
Highly informative post on Dynamics GP Support & Services blog on Common Tips and Issues when Troubleshooting and Testing Integrations in Integration Manager.
I have never read such an expansive post on Integration Manager (IM) ever. Mariano touches specific issues, David (and his technical team) on his blog shares specific topics. But this one’s so very expansive and one stop guide to IM issues and tips.
Bookmark this for your future reference.