As Microsoft Dynamics Technology partner, we would like to revisit popular Microsoft Dynamics CRM integration scenarios and technologies. This publication is intended to IT professionals and Microsoft Dynamics technical support people.
Upfront we have to admit, that we are not reviewing any third party tools and Microsoft CRM Add-ons, we are considering integration tools, available out of the box for Microsoft CRM customer. Microsoft CRM versions: current 4.0, also historical 3.0, 1.2, 1.1
1. Microsoft CRM SDK. If you are Microsoft Visual Studio .Net C#, VB or SQL programmer and developer, you may decide to dedicate some of your software development training time to familiarize yourself with SDK objects and methods: Lead, Account, Address, Contact, Quote, Order, Contract, Case, Task, etc. Microsoft CRM is pretty complex in its technology layers, and it is not recommended to populate MS CRM tables directly via SQL scripting – recommended way is to abstract your programming through MS CRM SDK layer
2. Dynamics GP Great Plains integration programming. Here you have to consider Dynamics GP eConnect, this Software Development Kit opens Microsoft Dynamics GP objects, such as customer, vendor, GL account, employee, Sales Invoice, Purchase Order, etc. eConnect is also MS Visual Studio programmer friendly, so you could enjoy eConnect self discovery. We recommend you to consider web integration project, where you combine Microsoft CRM SDK and Great Plains eConnect libraries
3. SAP Business One integration coding. In SB1 you should think about combining SAP Business One SDK libraries with Microsoft CRM SDK modules. SAP B1 and GP are both ERP and MRP applications and Microsoft CRM integration methodic is similar on technology layer
4. Lotus Notes Domino integration. Here you have various layers. Try to review ODBC integration if you are doing discovery. ODBC expects you to have repetitive structures in Lotus Notes, which is pretty common if you are dealing with custom Lotus Notes database
5. Microsoft CRM EDI programming. Electronic Document Interchange is typically associated with Vendor purchasing and order placement channel. If you have merchandise ordering logic from your Microsoft CRM Sales Orders, then consider formatted SQL Select statement from CRM tables
Dexterity Customization for Dynamics GP Evaluation Level Paper
When you are developer it is always a good idea to read technical manuals. But if you was just assigned to the IT team to decide if Dexterity is the right tool to customize your ERP application then first you need something which is in style of ‘easy reading papers’ or FAQ
Planning Dynamics GP Customization in Large Corporation
If you are reading this page then chances are high that you were not able to find ISV add-on and need customization project. Let’s talk about planning, quality assurance and future event such as version updates.
Dynamics GP Invoice Logo Attributed to Specific Company or Crossing the Borders of Three SOP Forms
Initial Great Plains Dynamics architecture had three SOP Invoice forms: Long, Short and Blank. Modern GP is popular in scenarios where you have more than three companies under one business entity umbrella
