40
4 – 6 November 2014 Barcelona, Spain
| Date post: | 27-Jun-2015 |
| Category: |
Software |
| Upload: | fabienne-van-doornmalen |
| View: | 557 times |
| Download: | 0 times |
4 – 6 November 2014Barcelona, Spain
Integrating Microsoft Dynamics ERP with Microsoft Dynamics CRM using Connector for Microsoft DynamicsGonçalo AntunesCSS EMEA Microsoft Dynamics [email protected]
BKCP002
Session objectives and takeawaysSession objectives: • Discuss the Microsoft-provided integration solution for the Microsoft Dynamics product
line• Share some real scenarios, do’s and don’ts for successful Connector for Microsoft
Dynamics implementations• Highlight some of the extensibility options the Connector for Microsoft Dynamics offers
Session takeaways• General knowledge of Connector for Microsoft Dynamics and its capabilities and
benefits• Top-of-mind do’s and don’ts when considering the Connector for Microsoft Dynamics in
your projects
Session agenda• Overview• Architecture• Installation and configuration• Demo• Extensibility and troubleshooting• Real-life scenarios, Do’s and Don’ts• Q&A
Overview
What is the Connector for Microsoft Dynamics?• Robust Microsoft Dynamics integration that “just works” between
Microsoft Dynamics ERP and Microsoft Dynamics CRM• Easy install and deployment• Minimized architectural overhead• Support for Microsoft Dynamics CRM 4.0, 2011, 2013 On-premise and
Online deploymentsConnector
Management Client
CRM Database
CRM Web Services
ERP Database
ERP Web Services
Connector Database
ConnectorService
CR
M A
dapte
r ER
P A
dapte
r
Benefits• A Microsoft Dynamics product line integrated system
that increases business efficiency by keeping CRM and ERP systems in sync
• Save time by using an out-of-the-box integration with all the components you need
• No license cost
• Source-level filtering• Out-of-the-box template• Data transformation engine• Extensibility
Features
• Fields not mapped in CRM or ERP
• User-defined fields• Use constant
values or manipulate how data is transformed
• Import/export maps
• Run maps less often than default for maximum efficiency
• Run maps more often than default to support “real-time” business
• System- and business-level notifications
• Immediately, daily, or weekly
• Integrations retry when error is timing related
• Other errors may require intervention
Map templates Schedules Notifications Log files
Support for• Microsoft Dynamics CRM 4.0 On-premise (min. UR5)• Microsoft Dynamics CRM 2011 and 2013 in all deployments• Support for Microsoft Dynamics CRM 2015 will come soon
upon release!
• Microsoft Dynamics GP 2010 SP3, 2013, and 2013 R2• Microsoft Dynamics AX 2009 SP1, 2012 CU1, 2012 R2, and
2012 R3• Microsoft Dynamics NAV 2009 R2, 2013, and 2013 R2• Microsoft Dynamics SL 2011 SP1• Support for new versions of ERPs will come as they are
released
(For surrounding technologies, consult the documentation)
Architecture
Connector architecture
Integration Service
ER
P A
dap
ter
CR
M A
dap
ter
Instrumentation
Event Logging
Thread Mgmt
Diagnostics
Transform ServiceMS CRM (IIS)
CRM Web Services
CRM Store
Connector StoreConfiguration
Status Exceptions
ERP Store
ERP Web Services
Web Services
ClientNotifications Setup
Security Setup
Mapping Setup
Diagnostics
Failure Mediation
Document Setup
Information flowOne map execution detailed
Integration Map Activate
d
Map Queries Source System for New
Data
Map Queries
Destination System
for Corresponding Data
Map Updates
Destination Record with New
Data
Connector Waits for map to
run again
Destination System
Source System
Connector for Microsoft Dynamics
Out-of-the-box templateMicrosoft Dynamics ERP Integration Direction
Microsoft Dynamics CRM
Customer Account
Contact Contact
Currency Currency
Items, Resources Product
Price List Price Level
Sales Invoice Invoice
Sales Order Order
Salesperson ERP System User
Unit Schedules and Units Unit Group/Unit
Enumerated Values Pick List
* (Other entities and directions can be used; ensure testing is done and limitations are understood)
IntegrationParent-level entity in the ConnectorCan have multiple ones running in one serviceStart from Blank from out-of-the-box templateCan copy/move between environments
MapEntity-level relationDefine one entity from each source and destination systemActivate or deactivate, set schedules and source-level filtering
Field mapDefine mapping and transformation logic by fieldUse direct field, constants of functions
NotificationsPer integration, it is possible to set a notification to be sent by email
Important considerations• The ERP system is the master: once link is
done, some CRM features will be disabled or changed (for example, invoices will be controlled by ERP)
• Beware of data consistency; Connector is just the “data pump,” and will not validate business logic for you
Extended scenarios• Some extended scenarios can be achieved
(for example, sync 1 CRM Org to multiple ERPs), but are not considered supported; refer to reference below
Considerations for designing a single Microsoft Dynamics CRM organization to multiple Microsoft Dynamics ERP companies integrationblogs.msdn.com/b/dynamicsconnector/archive/2012/01/27/first-considerations-when-thinking-about-a-single-dynamics-crm-organization-to-multiple-dynamics-erp-companies-integration.aspx
Connector Team BlogAll updates and tweaks are published here
Integrating Microsoft Dynamics ERP with Microsoft Dynamics CRMblogs.msdn.com/b/dynamicsconnector/
Installation and configuration
Quick steps• Download• Set up applications• Set up Adapters (connection URLs and
credentials)• Configure products• Sync!
DownloadFrom PartnerSource or CustomerSource
Search for “Connector for Microsoft Dynamics”https://mbs.microsoft.com/customersource/northamerica/Connector/support/support-news/MSDY_ConnectorforMicrosoftDynamics
Application setupCRMEasy as setting up the integration user; solution will be imported throughout the process
ERP Straightforward, simple action of enabling the company for Connector synchronization (varies for each ERP, check documentation)
Adapter setupEasy setup of Adapters (URLs + credentials)
CRM configuration utilityStraightforward entity selection for integration
ERP configuration utilitiesVary for each one (below, example for Microsoft Dynamics NAV)
SyncCreate integrations and mapsMap and define sync on each direction to meet your project requirements
Demo
Gonçalo Antunes
Extensibility and troubleshooting
ExtensibilitySoftware development kit (SDK) is available• Possible to develop new adapters, object providers, and
mapping functions
• Included in the SDK are some Visual Studio templates where you can create these quickly
• The deployment will be as easy as copying the DLLs and registering the new adapter
TroubleshootingLogging and tracing• Logs are available and traces can be activated to capture all
service activity and communications with CRM and ERP webservices
Other tools• CRM platform traces• ERP-based logging• Web debuggers• SQL traces
Real-life scenariosDo’s and Don’ts
Case study availableCustomer: headON CommunicationElectronics Distributor Connects Systems to Simplify Operations, Enable Executive Control
Feedback verbatim:“By using Microsoft Dynamics NAV integrated with Microsoft Dynamics CRM, our financial management, customer engagement, and performance management are extremely effective in maintaining our competitive advantage and leading market share.”www.microsoft.com/casestudies/Microsoft-Dynamics-CRM/headON-Communication/Electronics-Distributor-Connects-Systems-to-Simplify-Operations-Enable-Executive-Control/4000011224
Do’s• Assess the Connector’s features, review
project requirements, and test to make sure it works prior to making decisions
• Always have the latest released build• Make sure you prepare the master data
and plan initial sync direction, to avoid duplicates
• When installing, prefer dedicated machine or low-web-activity one for deploying the service
Don’ts• Don’t think the Connector will be the
solution for every problem• If you have syncing process requirements
different from the template, assess and test the scenario further (for example, Account to Contact instead of Account to Customer)
• Don’t despise the initial sync process; a good one will ensure the future health of the integration
Additional tips• Use a dedicated account for integration
purposes (will not count for licensing)• Follow the documentation, in particular the
initial sync process section
Next steps, key actions, and resourcesYour feedback is important!
Fill out your evaluation!
Help us continue to improve sessions and the event by letting us know what you think
Evaluations can be completed in the following ways:
Communication kiosks located throughout the venue
Convergence website at www.Microsoft.com/convergence
Mobile event app (scan this tag to download the app)
Join the conversation online by following us!
#MSDynCRM
#MSDynAX
#MSDynNAV
#MSDynamics
@MSFTConvergence
Facebook.com/MSFTconvergence
Linkedin.com/company/Microsoft-convergence
#Office
#Office365
#MSCloud
#CONV14
Watch sponsor presentations on the Media Wall, and more!
The Convergence Experience Center has free technical support, demonstrations, and representatives from the user group communities.
Session recording and PowerPoint files can be found within Schedule Builder on the Convergence website.
© 2014 Microsoft Corporation. All rights reserved. Microsoft, Windows and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries.The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.
