Dynamics Gp Upgrade Project Overview And Version 2010

We are typically a bit conservative to recommend version update as soon as brand new version is just released. Instead, we prefer to do new features demonstration and have ERP user to be prepared to new bells and whistles and sometimes new business logic, which might be really needed. The best tactic in our opinion wait until couple of service packs are released and known issues and bugs fixed. We do not really believe that you would like to be in the pool of initial new release users, who is supposed to place technical support cases, most of them could be related to programming bugs. This approach is shared by some resellers and this was pretty much similar for all the historical versions and current release 2010 (also referred as 11.0). Lets review the procedure and talk about popular issues and their fixes:

1.GP Utilities. Traditionally it was and is done in Utilities application. When you install User Workstation from DVD image (not the manufactured DVD, as Microsoft releases images with integrated Service packs, see introduction above) following step is suggested run Utilities. This application looks into MS SQL Server via ODBC System DSN (created automatically and usually named Dynamics GP2010). If old version is found on the Server it begins upgrade. First this is Dynamics database and then companies one-by-one. Database side update is probably largest share of computer processor time. What is happening here? Simple steps: if new table is introduced it is created with related atomic stored procedures (with Z prefix they are needed for Dexterity table access). If table structure changes table is copied into temporary database, dropped and recreated and then reloaded from the copy. Finally, you are coming through the steps of upgrading modified forms (if you have Modifier module or customization site enabler) and reports (if you customized them in Report Writer usually SOP Blank Invoice form). We are reasonably laconic in general process covering. We have earlier articles, where we were describing the process in details

2.Updating to 2010/11.0. We had our first projects on 2010 with integrated SP1. As new version is often done on the new Windows and SQL Server, we recommended Windows 2008 Enterprise and SQL Server 2008 R2 64 bit version. When you are restoring companies and Dynamics DB from backup, do not forget to change DB compatibility level to 2008 (with earlier versions this step was not required). The path was from 10.0 on SP4 to 2010 SP1. We had over twenty companies to migrate and database side update went perfect without errors and warnings. Customer was using SOP Short and Long invoice forms modified and saved in packages (as each company needed logo and special disclaimer), initially created in version 8.0. The same packages were loaded successfully and modified reports upgrade was not really required

3.FRx. As user stayed on WindowsXP 32 bit, there were no need to rush and migrate to Microsoft Management Reporter. We applied FRx 6.7 Service Pack 12, recommended for 2010. On the Server, which is 64 bit Windows 2008 FRx client also works without problem, as we do remote desktop login and add or modify existing reports in FRx there

4.Integration Manager. Here we were disappointed. Old integrations were using Advanced ODBC sources. When we were testing the integrations (target to SOP transaction entry) we discovered that old-good-days integration creates all the document headers but only few documents got lines created. After consuming some budget hours we decided to search knowledge base on the Partner Source. Yes, this was known issue not resolved until late march 2011. This fact was disappointing as Advanced ODBC source is one of our key technology advantages and we used it in all known historical versions of Great Plains Dynamics. It looks like SP2 finally resolves this problem (we applied Integration Manager patch, posted on Partner Source)

5.OpenRowSet, Linked Server or simply importing text file in programming code. These constructions do not work as you would expect them to do. We spent couple of hours trying various drivers, reading internet posts and decided switch to SSIS (SQL Server Integration Services) packages. Usually we are taking Great Plains customers with challenging customization and integration needs and projects and we are a bit disappointed. Down the road we will have to recode existing integration and customization packages. In our opinion the problem is associated with 64 bit platform and drivers compatibility. Old Linked Server was probably based on 32 bit drivers and 64 SQL Server doesnt realize that it needs to call legacy drivers. But maybe this was something else

6.Some Fresh Air. It seems like Microsoft Business Solutions is concentrating on such new and revolutionary features as MS Office Stack, SSRS, Word Templates, Emailing Invoices directly from user interface in PDF format, Office Web Components or Sharepoint metrics, Reminders, To-Dos, Microsoft Management Reporter. Old logic is carried over as it is. However new features are built on the base of the old objects and this is where old Dexterity business logic might be screwed. Also, as we believe in Integration Manager major attention was given to eConnect connectors, while core functionality, such as Advanced ODBC source was damaged. Also there were a lot of discussions about FRx incompatibility with Windows7 64 bit. However we saw numerous examples, where it simply works, including the most complex FRx constructions: consolidated reporting tree, including reading budgets from Excel worksheets. We have to admit, that you may expect to get couple of error message in FRx installations. However we discovered that simply ignoring these messages is leading to successful installation and deployment. Of course the good news about FRx is just a temporary relief, as Microsoft stopped all new development for FRx and you should expect it to be finally incompatible in the matter of few years

7.eConnect. From one hand it is definitely good news, that eConnect is advancing and covering more master records and transactions. On the other hand virtually every new version of GP is redesigning eConnect envelop. It was direct SQL connection in 8.0. in 10.0 it was COM+ object, now in 2010 it is .Net assembly. Such change often ends up with the fact for you, software developer, that you have to review program code, where eConnect libraries are deployed. Crystal Reports, SSRS, Excel reports if those have access method via SQL Stored procedures, views or direct table link in reports wizard, it seems like they do not need to be reviewed on the compatibility with 2010. They should probably work as they are. In the case of Dexterity customizations, likely that they will work as is. In some cases 2010 changes table relations, where Dexterity Sanscript code should be reviewed and changed accordingly

8.Bonus Topic or Upgrading very old version all the way up to 2010. If you are on 8.0 there are typically two steps (8.0 -> 10.0 -> 2010). For earlier versions 7.5, 7.0, 6.0, 5.5, 5.0, 4.0 or Great Plains Accounting for DOS, Windows or Mac 9.5, 9.2, 9.1 and earlier please design your upgrade path with your VAR or Great Plains consultant. GPA for DOS as well as Great Plains Select was available on Pervasive SQL 2000/Btrieve DB platforms (plus GP Select on Ctree). There are migration tools to move you on MS SQL Server DB platform. There is also migration tool to move you from Microsoft Small Business Financials to GP 9.0

9.For additional information, please feel free to call us 1-866-528-0577 or 1-630-961-5918 (this number works for international customers) or email us help@albaspectrum.com We serve you USA/Canada nationwide via remote support (web sessions and phone/Skype conferences). Local service is available in Western Michigan, Chicagoland, Southern California (LA, Orange County, San Diego), Houston area of the state of Texas