|
||
Recent marketing decision of Microsoft to rename its products: Microsoft Business Solutions Great Plains, Navision, Axapta, CRM and Solomon into Microsoft Dynamics GP, NAV, AX, CRM, SL for Project Green Wave 1, intending to merge them into just Microsoft Dynamics in Wave 2. For application developer it should open new ways and opportunities. In this small article we'll orient developer in customization, integration & reporting tools.
• XML Web Services - Eventually all Microsoft Dynamics GP modules will be in your disposition through SDK. At this moment SDK is in progress – but it is clear that it will use eConnect or Integration Object SDK (new name for eConnect). eConnect objects will be expanded and will have web service interface.
• Microsoft Dexterity - In July 2005 we see some signs of Microsoft Dexterity renaissance. Microsoft resumes Great Plains Source code program – it is access to DYNAMICS.DIC, project and field service dictionaries with Dexterity scripts (regular dictionaries, that you can find in GP workstation folder have sanscript scripts stripped out). Program pricing will probably make it available for large and mid-size consulting companies only, but the fact of reopening this program gives some additional credits to Microsoft Dexterity and we believe that it will be playing role in the next decade. You can actually call web services from Microsoft Dexterity.
• Business Portal - Business Portal has all the chances to step-by-step replace existing proprietary interfaces for all Microsoft Dynamics future brands: GP, AX, NAV, SL, except probably CRM – it is already web-based (and MS Outlook-based – which is another strategic direction) application. Business Portal will have its own and hopefully open for MSDN subscribers SDK with C#, and probably VB.Net examples. Business Portal is .Net application. Plus you should be aware of new rewritten eOrder (new name – Order Management) – as you might know old eOrder was legacy ASP application. Order Management is being integrated into Business Portal.
• Visual Studio - As we will see GP object exposed via XML web services – this is where Visual Studio developer can take control (except Dexterity forms and screens). Visual Studio will be tool of choice to customize Business Portal, for example
• Microsoft SQL Server Reporting Services - These services more likely will be a replacement to Great Plains ReportWriter and Crystal Reports, especially when we are talking about Business Portal.
• Integration - You will have web services for the majority of GP objects. Plus Integration Manager will more likely use eConnect/Integration Object SDK technology
• Document Workflow - It will be a must in the close future. We know that traditional workflow provider is Lotus Notes/Domino. Microsoft will be working in this direction, where Microsoft Sharepoint might play a role in the close future.
Microsoft Dynamics GP 9.0 has multiple improvements and “Project Green” innovations. One of the new key words, Microsoft Business Solutions people like to introduce and increase the frequency of using is eConnect. 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.