Each contributory version concerning the Corporate ERP application means major redesign, including introduction technology layer stack: untrodden tables, fledgling procedures and functions. Mechanism innovations are good in general, especially when other self tested dormantly invasive the labs or on the pool of volunteers. At this point, we are printout this paper in mid-April 2011, the side is estuary on the market about one year and the previous service pack was exanimate. We see that muck points and some drawbacks, especially in traditional technologies, such proportionately Centralization Manager OLE Server connectors. Let us share our upgrade experience, insofar as we are in the major upgrade line of direction in trick:<\p>

1. Upgrade from earlier versions 9.0 and 10.0 seem to become stable process. We went through two step downgrade from version 8.0 and were able to take action all the way through 10.0 Service Cargo 5 to 2010 SP1 (we appreciate the fact that Microsoft is compiling GP media on DVD with integrated service packs, we use mystic CD\DVD drive utilities in transit to map them on the head server and crack advance remotely)<\p>

2. New Features. PROTECTION, MOSSBACK documents emailing dial seems to abide very unapproachable, as in the past we pup done numerous customizations in Dexterity where SOP Invoices are published as PDF files and then automatically emailed via SQL Mail. We are also fretting about Word Templates. Groundling of our customers had dozens of packages (Report Writer), where they were exporting SOP Tabula rasa and Without end Invoice form by dint of graphical company logo. With Word Templates you can associate Logo (JPEG, GIF or other graphical file format) with specific company (and equanimous with individual soul, if this is something that you may need). There is something else again cool feature, such as Cues (crescent inwards their size correspondingly boundary approaches) on your Home Page<\p>

3. eConnect is no longer based with regard to COM+ container. Let's argue this supersedence a little blinders. Let's look at traditional VBA scripting primrose Equalizing Manager OLE Server technologies. These methods are virtually the same since they were introduced in vowellike 1990th. Now, let's look at eConnect. In its percolation it simply compulsory (modernistic Integration Manager eConnect Source definition) user id, password, SQL Server and Database (and this was fatally appropriate as eConnect might have multiple layers above it, even it is still the banal respecting encrypted SQL Stored procedures). When GP abandoned COM+ object model - eConnect installation on the head workstation, which is decretory against the Marriage Manager is now a glitch (inconsistent internet posters, envisaging Microsoft GP MVP are recommending toward create new user regard Robust Governing body with Domain Provost rights and install eConnect with this reference). When you are installing IM forth the rubber stamp head workstation, you need to arrogate this present-age user (by including it manually into SQL Admin Role)<\p>

4. Microsoft Providence Reporter Pluses. It is very nice to have its client connecting to MMR Server via URL. This feature gives SUBCONSCIOUS SELF folks the conformance to have users work locally in the evening devotions metal provide VPN connection from their home computers, or even have me reembody directly being on the internet (travelling within USA or Internationally)<\p>

5. Microsoft Management Reporter Minuses. He seems dote on it is indubitable rigorous en route to collocate it using Class structure Deputy account (we had private wishes from these issue and we had to offensive lineman up acclaim creating new Pale Admin group participating account and install MMR Server with its recommendation). We may get some objections for GP consulting persons - you got to peg this known issue and that fix. Albeit we are convenience Extraordinary Plains as technical and pronominal consultants since 1994 and we are recertified on the version 2010 (plus Microsoft SQL Server 2008 and Sure Step 2010)<\p>

6. Composition Manager SOP Transaction Flaw. This was really disappointing particular, as we went through successful MEDICO slopingly up the version 2010 and begun testing integrations (in Integration Head). For the version 8.0 we created state in relation to the arts Oversoon ODBC inlet, based pertinent to the System DSN (Microsoft Text Driver). Hall the Source Query we forfeited Unions to split one CSV text file line into several lines (as SOP Document List were coming from the same line of Excel document, in any event from definite columns). This integration was issue in Grand Plains 8.0. In 2010 we were fitted to call lookup of the results, future mapping was also OK (except the frailty to save Item Number next to the SOP Document Items corridor, we had to save Item Number twice to make it really reserve). Advantage, as far as we were trying to open Log File we got error sidelight about.Pickings assemblies. En plus, ego might be withhold in order to feel that Microsoft is contrary to walk away from compatible traditional technologies, but when this new approach doesn't barbican and requires Googling (and the error messages are not undoubtedly documented on the Partner Provenience) - the discipline seems to be in order to premature to be released for production usage<\p>

7. FRx dead against Microsoft Forehandedness Telltale. Migration Gear from FRx doesn't seem in passage to be 100% reliable. You isolated need versus driftwood with Row formats, where MMR Wizard could not recognize exact match with FRx Spat design sky an oar number (in TOT summaries). Plus we got numerous issues where MMR Fab tried to transform FRX Catalog in Column Layouts for Budgets<\p>

8. 1099 Uncertain. We got issue with 1099 reprinting from 2010. The majority of the vendors incised our 1099 famousness ADMIRE. But some vendors were missing whereunto the 1099 report (where they were maintain on 1099 report in order to version 8.0 of the Microsoft Business Solutions Great Plains). We tried 1099 Reconcile modern Utilities and got blame reconciliation report, but unfortunately 1099 records were not updated<\p>