Dynamics,Version,Update,Strate computer Dynamics GP Version Update Strategy and Practical Recommenda

Gone are those times when the companies and the organisations didn't need a hi-tech system to handle them. Owing to the considerable increase in the business sector and thus, an enormous increase in the complexity of the organisational struc ----------------------------------------------------------Permission is granted for the below article to forward,reprint, distribute, use for ezine, newsletter, website,offer as free bonus or part of a product for sale as longas no changes a

Also, on the other hand – running outdated version is generally bad idea, as here you cannot get support directly from ERP vendor, the consulting pool is shallower.  Plus, being on the old release often also exposes you to hardware failures and recovery (where new computer hardware is not compatible with old technologies, such as WindowsNT, Novell, old SQL Server 7.0, etc.).  Let’s try to come through recommended strategies and practical recommendations:1. Skip one version.  If you are normal customers, where you do not expect something excited to be released in new coming version, we recommend you to consider skip one update.  For example, if you are on release 9.0, you probably may skip update to 10.0 and now when 11.0/2010 is available with its Service Pack 1 – you are ready to go with update project.  In this scenario you are exposing your company to couple of new technologies: Windows Server 64 bit and MS SQL Server 2008 (where your 9.0 is likely hosted in SQL 2005 or 2000).  Microsoft Business Solutions technical support team is trying to keep at least two or three recent versions officially supported – as you can see – your company is covered with MBS support as well2. Wait for at least one service pack to be released.  Typically every new version is announced on special event, such as trade show, where incentives are offered for pilot upgrades.  In real life we know that DVD with graphical logo is not something you would like to try to use in update right away.  Software development industry introduced such concepts as Alpha, Beta, Release Candidate, Manufactured DVD/CD and then pioneering customers are exposed to new bugs discovery and clean up in following Service Packs.  We recommend you wait until the first or better couple of service packs are released3. Current Dynamics GP situation, as we are writing this paper I April 2011.  Now we see upgrade season to version 2010 on SQL Server 2008 64 bit.  Also, Microsoft introduced a move in switching from FRx to Microsoft Management Reporter.  As FRx Financial Reporting might be critical for your Accounting department, we recommend you to make small steps toward MMR.  If you are using such technologies as Multicurrency, Excel Worksheets link in Row Format or Reporting Tree in FRx – we recommend you to undertake test migration from FRx to MMR4. Dexterity Customization Upgrade.  If you have custom modules, we recommend you have their code reviewed by professional Dexterity programmers and test upgrade environment is recommended5. Report Writer upgrade.  With latest versions 2010, 10.0, 9.0, and 8.0 we do not see issues with RW reports migration.  In the past we were involved in the projects where we had to modify formula fields in such popular reports as SOP Blank Invoice form (versions 7.0, 6.0, 5.5)6. Integration Manager.  If your historical version deploys eConnect connectors, then you need test update for IM.  eConnect bearing technology migrated from direct access to SQL (in 8.0) to COM+ (9.0 and 10.0) to .Net Assemblies (11.0).  Surprisingly enough traditional OLE Server based Integrations are version neutral and require minimum efforts to be upgraded7. Crystal Reports.  These are usually based on SQL Server Stored Procedure or view and are neutral to database changes, attributed to new releases8. What to do if we are several versions behind?  Well, you should expect several steps to get you on the modern release.  If you are on Microsoft Small Business Financials, Great Plains on Pervasive SQL or Btrieve or use Intellisol Advanced Purchase Order Processing – there are migration tools, specific to each case9. Great Plains Accounting for DOS, Windows or Mac.  Typical scenario is to redeploy it on Windows XP 32 bit workstation on Pervasive SQL 2000 SP one or two.  Then use migration tool to migrate from GPA 9.5 (if you are on 9.2, 9.1 – you need upgrade diskette to move you to 9.5) to Great Plains Dynamics on Pervasive 7.5, then migration tool to Great Plains Select 7.5 on MS SQL Server 2000 and all the way up to 2010/11.010. Dynamics GP Upgrade in International Environment.  If you are multinational corporation with offices and facilities overseas, where GP serves as international subsidiary accounting application – we recommend you first verify if Microsoft Business Solutions has new version localized for your targeted country.  Since Microsoft acquired its new Corporate ERP platforms, such as Axapta, Navision, Solomon, Great Plains – it got more room for changing its offer in specific country or region.  We got a feeling that MBS is leveraging Dynamics AX on the international market, especially in Europe (including Russia, Kazakhstan), Brazil, China.  Dynamics GP is available in English speaking countries and in Spanish speaking Latin America11. For further information, please call us 1-866-304-3265 or email [email protected].  We provide service in USA and internationally via web sessions.  Local service is available in Chicago, Los Angeles, San Diego, Houston, Dallas, West Michigan: St Joseph, Benton Harbor, Kalamazoo, Holland, Saugatuck, New Buffalo, Muskegon