I ran across an issue a while back that a developer was running into after installing Dynamics SL 2011 on a machine with Dynamics GP 2010 (and Dynamics GP 10). Then in the next few days we had two more cases of the same issue (and again here , here , and here ). But I’m getting ahead of myself in that we didn’t notice that was a common thread until the third case. So anyway, what we found was that SL ran fine as did GP 10.0. However Dynamics GP 2010 would crash consistently on launch. After discovering that SL was the common denominator, we had un-installed SL and found that Dynamics GP 2010 again launched just fine. Reinstalling SL would again cause GP 2010 to crash on launch.
Today, I have another treat for Visual Studio Tools developers. After I posted the article: How to update Microsoft Dynamics GP Visual Studio Tools Addins on a live system , I was contacted by another community member, Srinivas Ramidi. He has created a little utility that makes using the DAG (Dictionary Assembly Generator) tool easier by providing a Graphical User Interface (GUI) to the tool
Convergence 2012 in Houston, TX, USA is over, but I recently found these videos and wanted to share them. Make sure you watch the Volunteer Highlight Video to see the amazing volunteer work that the Microsoft Dynamics community does for the host city of Convergence. Microsoft Dynamics Convergence 2012 Opening Video – A World of Opportunity (Please visit the site to view this video) Microsoft Dynamics Convergence 2012 Volunteer Highlight Video (Please visit the site to view this video) Convergence 2012 Closing Video (Please visit the site to view this video) Enjoy David
Till SQL Server 2008 R2, if you want to change the database on which you would like to execute a SQL query in SQL Server Management Studio (SSMS), the keyboard shortcut to do so was CTRL + U from the query window.
Over at ERP Software Blog, MIBAR.net has shared an article from ITWorld.com about 13 Common ERP Mistakes that we should avoid . It’s indeed a comprehensive list. Below are the points, which are elaborated in that article: Poor Planning Improper ERP Vendors Vetting Not understanding / using Key Features Underestimating Time & Resources Required Not having right people on team from the start Not setting priorities Not investing in training & change management Underestimating the importance of accurate data Taking the kitchen sink approach Not decommissioning legacy applications Not having an active load testing environment Ignoring Third-Party support alternatives Not having a maintenance strategy And I would like to add one further mistake: Keep on changing requirements in the middle of actual implementation OR Implementation without a concrete Sign-Off document I believe the above list pretty much completes the most common mistakes that we might make in an ERP implementation.
As the release of Microsoft Dynamics GP 2013 (formerly known as GP “12″) gets closer, there are more and more resources and information being released to help partners and customers get ready. Kevin from the Microsoft Dynamics Partner Community Blog has let us know that the Microsoft Dynamics GP 2013 Launch Portal is up and running and it should be visited on a regular basis to keep up to date with developments: Microsoft Dynamics GP 2013 Launch Portal (PartnerSource) My colleague,Kelly Youells from the Microsoft Dynamics Support Team has post the initial System Requirements for Microsoft Dynamics GP 2013.