Microsoft Great Plains Integration with MS CRM overview for consultant

This integration is the first time Microsoft created for Prairie 7.5 (micro-soft dynamics of the current primary care physician), and later on Microsoft& 39;s patch release 8.0 enables integration between primary care physicians and 1.2 ms crm (now Microsoft Dynamics crm). This requires the integration of the platform and biztalk created a dedicated computer: windows2003 instance of the server structure of the state. Form, accessible through a Web interface. Suit. We briefly review the technical integration capability can give insight, based on our experience.
customer / account. When creating an account, ms crm - Integrated dynamics doctor - an account is automatically created prairie. It is a bit of a challenge for all of the features and settings to work, especially if you plan to use a base class, address, etc. At the same time, if the normal operating parameters, such as the amount credited to provide value ms crm - and then the number of primary care physicians the smoothly. Somewhat non - elegant - it is difficult to increase the prairie designed for the customer& 39;s records for the automatic numbering. Outside the box - Integrated custnmbr crm generate from the account name - this means custnmbr takeoff from all of the prairie, you must print the form.
SOP sales orders. Crm order to solve the sale - This is the prairie. The most common question is - if there is no order to integrate customers, why not set up a credit limit prairie. You have to find ways to deal with this problem, the procedure of the enemy. Customer
history. Another common problem. When you run / ms crm implementation - Existing customers crm earnings from the prairie. Typically, the sales order and then move quoted ms crm-generation process, where a good mechanism to merge Microsoft Word to print in the form of a contract or a quote for a client quote templates. Import tool to enable customers to obtain ms crm when - they are in the integration of primary care physicians automatically ms crm redundancy. You must delete the records of new customers and prairie ms integration of the primary care physician records in a database update crm teureul integration. We offer the following script (the first to analyze the case, please use this script only if it is structured very comfortably ms crm scripting and the primary care physician, greatplainsserver is connected to the server - in writing server-side integration gpcrm ): Set entitykey
update integrationentityinstance
integrationentityinstance a b.custnmbr in
join = [greatplainsserver]. [Gpcompanydb]. Dbo.rm00101 b left (a.entitykey, 8) = left (Replace (custname, & 39; & 39;, & 39; & 39;), 8) = &
where entitytype 39; customer & 39; yawney dania



Bookmark it: