If you are notwithstanding on older version of this mid-market Corporate ERP application and you deployed like integration and modification technologies as Integration Manager by old eConnect or Advanced ODBC Source throughout text file, please review our discovery. There are several technology areas to what version 2010/11.0 might demand you to re-haul the fashion script. We just off the major upgrade, where version 8.0 was hosted in 32 borer Windows 2003 and SQL Server 2005. Plus, manifold home page shortcuts were calling VBscript by popular technology of impersonation, retrieving user ID, DSN, Password and group database, executing multiple SQL Select statements (checking whether or not customer RM00101, inventory item IV00101) and at that time executing Integration Management integration (directly in the script). We would like to apportioned lot our discoveries, surprises and some disappointments:
1. SQL 2008 and 64 particle platform. To our surprise we had issues rendering CSV text file via OPENROWSET require in SQL. We opened add hoc queries by way of sp_configure procedure (as SQL Server 2008 closes every one of the technologies, except basic ones ~ dint of. default), but this was not the end of the story. Second, we tried to cause Linked Server to our eCommerce DB at which place we have SQL 2005 on Windows 2003 32 scrap (with the option selected SQL Server), specified ‘sa' elucidation and its password (as we usually were doing in the beyond ). It was really impossible for us to confer select statement to successfully created Linked Server (individual of our custom triggers is supposed to update eCommerce database slab, when Invoice in Great Plains is paid, very lately we have to think about dissimilar technology to do the job, in the room of trigger for delete on SOP10100 table – SOP document header)
2. Integration Manager Advanced ODBC Source. What we had in IM 8.0 was SOP Transaction Integration, based forward the Advanced ODBC Source, reading data from CSV file. The reason concerning us to deploy Advanced ODBC was the urgency to use Union construction in the Source defining (as we had to split common row in the CSV file into manifold SOP Lines). In version 2010 IM Source preview showed us discipline lines (generated in SQL Select through Union statement over Microsoft Text Driver), in whatever manner integration run created the majority of the SOP Invoices free from the line items and with Zero in Document Amount. We tried to renew the integration, the result was another time strange with zero amount document (in whatever degree not the same documents had zeros). We could not identify the patterns, as the same Items were in some cases integrated as expected and in other cases they were skipped
3. FRx 6.7 by Service Pack 12. Here we had encouraging surprise, in the same proportion that we were able to redeploy FRx on 64 bit Windows 2008 Server (because remote desktop connection for managerial team), more on Windows XP and Windows 7 64 get the ~s on workstations in the office. Microsoft Business Solutions says that it doesn't advocate FRx on 64 bit platform, appropriate to the fact that they didn't convoy sufficient set of tests. With this patron we had all kinds of intricate scenarios, including multicurrency, Excel Worksheets, specified in the Reporting Tree. Originally in the discriminative characteristic phase we were even able to display FRx 6.7 with Service Pack 5 to operate with Dynamics GP 2010 databases attached SQL 2008 (however GP user countersign translation was obviously not supported and the no other than option to print FRx reports was to appliance SA user login, where SP 12 supports watchword encryption and users were able to application their GP login and password
4. Test Phase. The settlement was made to install GP components in quest of version 2010/11.0 on the same user workstations for key decision making users. Here we realized that you be possible to have Microsoft Great Plains 8.0 workstation coexisting through Dynamics GP 2010 (however you fail to keep some nice features in 8.0, of the like kind as importing budget from Excel file – 2010 interface, however can load budgets from Excel). Integration Manager uses registry toward its Regkey and you cannot be favored with two versions installed on the same Windows XP workstation. FRx also requires dedicated user workstation (we ended up to setup modern FRx and Integration Manager on unconnected Laptop for all the users to example these applications
5. Microsoft Management Reporter. We did particular upgrades for smaller customers, plus we did migration from FRx to MMR on the side of our internal accounting. However for this customer we got issues trying to inaugurate MMR with Domain Administrator account. We accomplished the failure and customer suggested to bludgeon to FRx. As the observation – it looks like MMR could exist installed if you create new ground in the Active Directory and find him Domain Administrator (rather than using Domain Administrator regard)
6. eConnect Installation on the User Workstation according to Integration Manager eConnect Sources. Here, anew we got issues installing eConnect when exposed to domain administrator account (Cannot add SQL User blunder message). The work around was to be the occasion of new user and make him branch of the Domain Administrators group
7. What was truly cool and what customer employees liked. Word templates bestow you the option to specify graphical logo for each company (we have more than twenty and each time they have to load RW Package by SOP Blank and Long invoice forms into current Reports.dic)
8. Alternatives to the crowd processing. In user home page you be able to now navigate to all SOP Invoices, in that case mark document (this feature allows you to impress SOP documents located in different batches) and therefore in action pane above you be able to post them all together (or convey Orders or Quotes to Invoices, beneficial to example)
No comments:
Post a Comment