eConnect object and methods will have more exposure for Visual Studio.Net C# or VB developers through XML web services.  Also emphasis shift will be in the field of Microsoft Dynamics GP Business Portal, this is also understandable – Microsoft has to deemphasize former legacy proprietary technologies, such as Microsoft Dexterity (former Great Plains Software Dexterity), Navision C/SIDE (this is in case of Microsoft Dynamics NAV – former Navision Attain), step-by-step phasing them off and replacing with open-source .Net web development.  In this small article will touch the “top of the iceberg” in Microsoft Great Plains 9.0 customization, development and integration.

Microsoft Dexterity Source Code Program reopening.  When Microsoft bought Great Plains Software five years ago – it quickly closed Great Plains Dexterity source code program for new enrollments, leaving it open for existing VARs.  One of the reasons in our opinion was Microsoft optimism in quick Microsoft Business Solutions product merge: Great Plains, Navision, Axapta, Solomon.  It didn’t happen with the expected speed and now it is clear that serious development for Microsoft Dynamics GP requires Microsoft Dexterity skills and experience and access to the source code (DYNAMICS.DIC with Dex sanscripts codes).  If you plan your custom application to work with Microsoft Dynamics GP “fat client” – it is DEX.EXE with DYNAMICS.DIC, Dynamics.set and your custom dex dictionary – the Microsoft Dexterity is the tool of choice.

Microsoft Dynamics GP Integration Manager.  Former Microsoft Great Plains Integration Manager – versions 5.0, 5.5, 6.0, 7.0, 7.5, 8.0 were based on OLE technologies, deploying Dexterity application as OLE server, and so using Great Plains Forms to implement integration.  The result was moderate and slow performance.  Now Integration Manager is in the process of being rewritten in eConnect – eConnect will have majority of Microsoft Dynamics GP forms and objects: SOP, POP, IV, Payroll, AR, AP, GL, BR, Manufacturing, BOM.  Some drawback of this nice innovative feature – if you are using heavy customization if former Microsoft Access based IM database – you should consider rewriting your customization in new IM.

Reporting.  ReportWriter will stay, however Microsoft SQL Reporting Services will be the reporting tool of choice over former Crystal Reports.  You should expect phased change from Crystal to MSSQL Server RS.

Tables Structure.  Will stay – this will mean certain legacy eCommerce programs staying in business reassurance.  SOP10100, SOP10200, SOP30200, SOP30300, GL00100, RM00101, PM00200 and other tables will be around for the next … 10 years or so