Great,Plains,Upgrade,notes,fro computer Great Plains Upgrade: notes from the field
----------------------------------------------------------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 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
In any case latest service pack is recommended if you move your GP version to 10.0. We understand that upgrade to 10.0 was really enabled for the majority of Great Plains customers only in November 2007, when Microsoft Business Solutions released GP 10.0 SP1Prior to 10.0 SP 1 upgrade. When SP1 was not yet released, we tried probing upgrade and got issues with POP10100 table, which was pretty popular issue, known in 7.5 to 9.0 upgrade. Also Microsoft upgrade 9.0 SP2 to 10.0 (no service pack) took substantially longer than upgrade from 7.5 to 10.0. In our case in moving to version 10.0 we got upgrade issues for table IV10200. So, our recommendation dont even try upgrade to 10.0 without service pack applied to your 10.0 upgrading workstation.Service Pack 1 fixes. First of all the upgrade performance increased the upgrade time was reduced from over 20 hour to about 5 hours. Next the problem with IV10200 disappeared.Check Links recommendation. In our case check links prior to upgrade would take several days to run, which was not practical. However when upgrade was done and we went into production on version 10.0, we saw multiple places where check links would be a help: drilling down to GL open transactions, trying to open query to PM posted documents are two places. We immediately scheduled checklinks to run over next few weekends to cure all the companies. Warning for customers with custom integrations, where data is moved to GP through SQL stored procedures in your case check links may find integration business logic validation issues, so check with your custom integration developers if check links is safe thing to tryFRx. This time the decision was made to move FRx to Citrix 32 bit (as you may know it is not fully compatible with 64 bit Citrix at this time). FRx 6.7 move was surprisingly difficult we got a lot of problems, related to Citrix security restrictions. Also we got issues related to export to Excel as Microsof recommended there should not be spaces in path and file name, otherwise export to Excel produces errorsGP Security migration. As Microsoft explained in order to migrate old-fashioned security for users from 9.0 to new security model in 10.0, you GP workstation installation path should not have spaces which was a bit surprising as regular upgrade process creates GP workstation in C:\Program Files\Microsoft Dynamics\GP, and this path obviously has spaces. Please be aware about security upgrade problemReports problems. Also, we got issue with Purchase Order Blank form. By whatever reason temp table, which is replacement to POP10100 had empty company name, and ship to address fields. In order to work around we had to replace this table in ship to address calculated fields with Site master table this did the job, however it took us several hours to analyze the problem as not every PO was printed with blank ship to address. Company name was blanked on every report, until we replaced it with Company Name global field. Also this seems to be more often happening problem for 10.0 than it was happening for earlier versions Reports.dic becomes corrupt after several modifications of one of the reports the cure is simple: you make a copy of corrupt Reports.dic and import reports into fresh Reports.dic. The corruption in our cases behaved in the inability to add new text fields these new field were immediately turned to unknown field, when we moved cursor out of themGP Integration Manager in Citrix. IM didnt manifest any issues, when it was moved to Citrix 32 bit (the reason to stop it at 32 was eConnect .Net components compatibility)
Great,Plains,Upgrade,notes,fro