Dynamics GP Version Update Under the Hood

Database obviously has to be upgraded table by table.  Legitimate question is why at all do we need to upgrade tables within the database?  The answer is simple – because new version introduces new fields to support added business logic.  To be precise – not every table has new fields introduced, and if table is the same in the new version – there is no need to update it.  However if table structure changes, then update copies table into temporary database, drops and recreates table and then moves back all the records from tempdb.  Besides tables themselves Great Plains Dexterity supports its own structure of indexes, and each index requires token stored procedures, these have z prefix in the name – all these objects are simply dropped and then reloaded from the installation DVD (this process typically requires several minutes to accomplish, you can see its progress by installing Lesson Company TWO).  Let’s review how your GP consultant does upgrade:

1. Dex.ini - log enabling.  The best way to find out what happened with DB side update is to enable logging in Dex.ini file.  It could be found in Data subfolder of the user workstation (in Program Files (x86)\Microsoft Dynamics\GP2010 or GP, if you are on version 10.0 or 9.0).  Open Dex.ini for editing and normally three lines on the top should be like the following: SQLLogSQLStmt=FALSE, SQLLogODBCMessages=FALSE, SQLLogAllODBCMessages=FALSE.  Simply change FALSE to TRUE and as the result Dexterity Utilities will create DEXSQL.LOG file in the same Data subdirectory.  If DB side upgrade completes without errors – everyone should be happy and you may switch back TRUE to FALSE.  But if upgrade produces error message and stops – there is time to open Dexsql.log file, scroll it all the way down in notepad or Write.exe and diagnose which stored procedure produced the error and possibly in which table and why.  At this point you can fix the problem and re-launch update – it will quickly catch up (skipping all the steps successfully passed and resume with the failed step redo).  If you cannot fix the issue on your own, this log file should be given to Microsoft Business Solutions Technical support engineer

2. If Database Side update fails.  You may decide to try the following checklist.  First of all, there is so-called Upgrade Path (where MBS specifies which source and target release could be used for upgrade, for example version 10.0 SP5 to 2010 SP1).  Modern versions, such as 10.0 and 2010 check SP for the source and target release and do not allow to proceed, if requirement is not met.  In older versions, such as 9.0, 8.0, 7.5, 7.0, 6.0, 5.5, 5.0, 6.0, 4.0 and earlier you can continue with update (without warning), but if required SP is not applied to you may expect your Dexterity Utilities to fail in upgrading (again, remember to enable logging, see paragraph #1).  If you forget to apply required service pack for the source or targeted version, consider restoring Dynamics and each company databases on the server, apply service packs and start over

3. Client Side Applications. These are typically GP Workstation (fat client), FRx Client and Server (Sysdata folder stores FRx metadata, if you are practicing with version 2010/11.0 you may use Microsoft Management Reporter as replacement to FRx Financial Reporter), Integration Manager (and its database, typically IM.MDB).  Client side also includes Reports.dic – modified reports (likely candidates are SOP Blank and Long Invoice forms with company logo).  If you are deploying Microsoft Dynamics GP Business Portal – its data is subject for update in DB side upgrade process and you will need to install new BP web based user interface.  If you have ISV add-ons or custom modules (specially programmed for your company in Great Plains Dexterity) – you would need to contact ISV if they have version upgrade scripts or procedure.  In the case of unique Dexterity custom module, please contact your original Dexterity developer and have him review the code (if this person is no longer available, please try to find Dynamics.dic or Extract.dic file with your Dex Sanscript codes – if you can find either one of these files, you can turn it to another  Dexterity coder for analysis and upgrade)

4. eConnect technology and its version update.  MBS seems to change eConnect interfaces more frequently, comparing to such traditional technologies as Integration Manager, Dexterity, VBA/Modifier.  For example, if you were using eConnect connectors in Integration Manager 8.0 – you were providing direct user ID, password and company database ID.  In version 10.0 these parameters were outsourced to COM+ object (COM container that could be opened in Control Panel).  Inversion 2010 eConnect local installation (client side) is no longer part of COM+, it is .Net Assembly.  If you are deploying eConnect in Integration Manager, custom web application, or call it via web services, we recommend you to keep one of your IT technician updated with eConnect trends (consider visiting Microsoft BS events in your area, online customers seminars and even GP customer eConnect related training courses).  Econnect might be critical, especially when you are nationwide or international ecommerce retailer and you are deploying real time ecommerce shopping cart integration by programming eConnect objects directly in MS Visual Studio C# or VB projects

5. SQL Server 2008 and 2005.  There is the trend to move away from such technologies as Data Transformation Packages, Linked Servers (where development was done on 32 bit Windows platform, but with switch to 64 bit Windows and SQL Server we see more emphasis on such technologies as SSIS – SQL Server Integration Services).  Well, there is technology recycling trend, which is at this time probably about ten years (we will see how long 64 bit processors be around, before being replaced by something more powerful).  If you have custom integration processes pulling data via Linked Server mechanism from Oracle, Sybase, please note that these databases are supported with respective drivers in SSIS.  And now some excurses to the history

6. Pervasive SQL 2000/Btrieve or Ctree DB platform.  If you are on one of these, the versions might be 7.5 (this is the last version where Pervasive SQL 2000 and Ctree were available), 7.0, 6.0, 5.5, 5.0 (this version was released prior to Pervasive Software Acquisition over Btrieve Technologies).  If you are on Pervasive SQL /Btrieve – you should expect migration step to MS SQL Server

7. Great Plains Accounting for DOS, Windows or Mac: 9.5, 9.2, 9.1 8.0 and earlier.  Both Great Plains Software in late 1990th and Microsoft Business Solutions considered GPA for DOS, archaic Windows and Mac customers who persisted to stich to their old version and do not migrate to Great Plains Dynamics Select, as small business accounting customers and prospects.  As alternative platform for Small Business Corporate ERP GPS introduced Small Business manager/Financials 7.0, 7.5, 8.0 (where GPS was already acquired by Microsoft and renamed into Microsoft Great Plains Business Solutions, later on just to Microsoft Business Solutions).  There was a migration tool from GPA to Small Business Manager, but with version 10.0 MBS decided to cease SBF business line with recommendation to migrate to Dynamics GP 2010 or 10.0 Business Ready Business Essentials

8. Crystal Reports and your new version.  Crystal is just a reporting tool, where you are Great Plains SQL programmer should provide report engine via SQL view or Stored Procedure.  If you are sticking to these guidelines, your reports should be version proof

9. If you feel that your concerns are not addressed or your question is not answered, please feel free to contact our office.  Support domestically in the USA, Canada, Mexico and internationally.  This option is possible via Web Sessions, Skype or Phone conferences and direct visits onsite (in the case of the large scale project).  Our consulting team speaks English, Chinese, Portuguese, Spanish, Russian, Filipino.  Feel free to call us 1-866-304-3265, 1-269-605-4904, or email help@efaru.com