Microsoft CRM Development: SDK, C#, SQL, Exchange, Integration, Crystal Reports – overview for programmer Written by Andrew Karasev Microsoft CRM is new player on CRM software market. The whole conception behind CRM seems to be different. In case of traditional CRM software (Siebel, Oracle) - application was designed with platform independence in mind. Microsoft CRM is dedicated to Microsoft technology and so deploys all Microsoft tools: Windows Active Directory, Microsoft Exchange 2003/2000, SQL Server, Crystal Reports Enterprise, Biztalk server, Microsoft Outlook, Internet Explorer, Microsoft Great Plains as backend, etc. If you are software developer, database administrator or web designer who is asked: how do we customize Microsoft CRM – we are giving you directions in this article. 1.Microsoft CRM SDK – this is software development kit with C# and partly VB.net code samples – it is supported by Microsoft Business Solutions technical support. It is based on web service calls, if you are C# .NET developer – you are excellently positioned to do this type of customizations. This is preferred modification scenario and this should be easily upgradeable customization. VB.Net examples will be available soon. 2.Legacy SQL Data integration. This is also easy and safe. If you have SQL database, sitting on same or linked SQL Server – you can create ASPX .Net application and simply integrate it into CRM. You can place it on navigation bar or menu in isv.config – please refer to MS CRM SDK 3.Legacy ASP integration – this is somewhat more sophisticated. You have to deploy HTTP handler to be a middle party between CRM which is .Net based and ASP which is legacy IIS. The trick is – you have to have INI file with security settings to penetrate into MS CRM with proper credentials, calling web service. Microsoft Great Plains Data Conversion – overview for developer Written by Andrew Karasev Looks like Microsoft Great Plains becomes more and more popular, partly because of Microsoft muscles behind it. Now it is targeted to whole spectrum of horizontal and vertical market clientele. Small companies use Small Business Manager (which is based on same technology – Great Plains Dexterity dictionary and runtime), Great Plains Standard on MSDE is for small to midsize clients, and then Great Plains serves rest of market up to big corporations. If you are developer who is asked: how do we convert our old system data for initial Great Plains setup – read this and you will have clues on where to look further. 1.Great Plains Integration Manager - this is rather end-user tool - it is very intuitive, it validates 100% of business logic, brings in/updates master records (accounts, employees, customers, vendors. etc.) brings in transactions into work tables. The limitation of Integration Manager - it does use GP windows behind scenes without showing them - so it is relatively slow - you can bring 100 records for ongoing integration - for one-time conversion/integration you are probably OK with IM. By way you can program Integration Manager with VBA. 2.eConnect – it is type of Software Development Kit with samples in VB.Net. Obviously development environment should be Visual Studio.Net. eConnect will allow you to integrate master records - such as new customers, vendors, employees, etc., plus you can bring transactions into so called Great Plains work tables (eConnect doesn't allow you to bring open or historical records - you need to post work records in Great Plains, same limitation applies to Integration Manager above). eConnect is rather for ongoing integration. It was initially created for eCommerce application integration to Great Plains. 3.SQL Stored Procedures. Obviously you have unlimited control and possibilities with SQL queries. You need to know Great Plains tables structure and data flow. Launch Great Plains and go to Tools->Resource Description->Tables. Find table in proper series. If you are looking for customers – it should be RM00101 – customer master file. If you need historical Sales Order Processing documents – they are in SOP30200 – Sales History Header file, etc. Do not change existing tables - do not create new fields, etc. Also you need to realize that each GP table has DEX_ROW_ID - identity column. For ongoing integrations - sometimes it is good idea to use inbound/outbound XML in parameters - then you can deploy web service as a middle party between two systems. Cont'd on page 2 ==>   ImproveHomeLife.com © 2005 Terms of Use