This presentation is dedicated to Microsoft Dynamics, its organizational and technical points.
This presentation by Dmytro Kuiavets, SPM at GlobalLogic Kharkiv, and Dmytro Golodiuk, Solution Architect at ZEPPELIN International, was delivered at IT Weekend in Kharkiv on May 27, 2017.
Transcript: New from BookNet Canada for 2024: BNC CataList - Tech Forum 2024
How to Manage Data Integration within Microsoft Dynamics
1. How to manage data integration within
Microsoft Dynamics efficiently:
organizational and technical points
Dmytro Golodiuk & Dmytro Kuiavets
2. Dmytro Golodiuk
Solution Architect at ZEPPELIN International
Technical lead of the .NET Development stack
Head of IT Architectural Committee at ZEPPELIN
International
Enterprise Architecture doer
Dynamics 365 & Office 365 Fan
Certified Professional
C# by Microsoft
Dynamics CRM 2011 by Microsoft
Scribe Insight by Scribe Software
Documenting Software Architecture by SEI CMU
3. Dmytro Kuiavets
• SPM at GlobalLogic Kharkiv
• President of Kiev Chapter of
International Institute of Business
Analysis (IIBA)
• “The Best Professional in Business
Analysis” by IT Ukraine Association,
2012
• Emotional Intelligence trainer
5. Enterprise softwareFrom Wikipedia, the free encyclopedia
• Enterprise software, also known as enterprise
application software (EAS), is computer
software used to satisfy the needs of
an organization rather than individual users.
• Enterprise application describes applications -- or
software -- that a that a business would use to
assist the organization in solving enterprise
problems.
6. Automated billing systems
Payment processing
Email marketing systems
Customer Relationship Management (CRM)
Enterprise Resource Planning (ERP)
Business Intelligence (BI)
Business Continuity Planning (BCP)
Enterprise Application Integration (EAI)
Enterprise Content Management
Enterprise search
Enterprise Messaging Systems (EMS)
Call center and customer support
HR Management (HRM)
Common Types of Enterprise Applications
10. Architecture Roles
A big part of what the Enterprise
Architecture does is make sure
that the organization has the
right systems in the right places
to do all of the stuff that needs
doing.
13. CIO and Trends
The report also notes that “By 2019, over 85% of new packaged customer
service and support software will be delivered on a cloud-based model, and
SaaS will emerge as an essential selection factor for CRM customer
engagement centers(CECs) in all geographies and for all but the most complex
processes."
17. Today’s Data Challenges
• Upgrading from legacy systems
• Data Integrity
• Adding more systems and more data in those systems
• All these systems need to be synchronized with one
other
• Actions in one system often need to trigger actions in
other systems
• New systems are rapidly evolving
• A change in one system can break the entire integration
network
18. 2001 20162001 2003 2005 2007 2009 2011 2013 2015
Microsoft CRM 1.0
6/1/2003
Microsoft CRM 3.0
12/1/2005
Dynamics CRM 4.0
12/1/2007
Dynamics CRM 2011
6/1/2010
Dynamics CRM 2013
7/1/2013
Dynamics CRM 2015
11/30/2014
Dynamics CRM
2016
11/30/2015
Dynamics
365
7/1/2016
Microsoft acquired iCommunicate
Microsoft Business Solutions Customer Relationship Management 1.0
Project Green
Dynamics brand was launched
The term “XRM” was introduced
Microsoft Dynamics CRM Online marked
the beginning of the cloud services era
in Microsoft’s business applications November 2011 Service Update
Cross-browser support
Polaris UIAcquisitions of FieldOne - global provider of field
service management solutions for the enterprise
Acquisition of Adxstudio Inc., Web portal and application lifecycle management solutions provider
Dynamics CRM Spring 2016 Wave (Update)
Microsoft to acquire LinkedIn
Evolution of Dynamics CRM
19. Dynamics 365 Evolution
Yesterday
Dynamics CRM
- Field Service
- Project Service Automation
- Parature
Dynamics AX
Project Madeira
Dynamics GP
Dynamics NAV
Dynamics SL
Yesterday
Dynamics 365 for Sales
Dynamics 365 for Customer Service
Dynamics 365 for Field Service
Dynamics 365 for Project Service
Dynamics 365 for Operations
Dynamics 365 for Financials
Dynamics GP
Dynamics NAV
Dynamics SL
21. Microsoft Dynamics
Data Integration Challenges
• Migrating from a legacy system to a new system
• Integration between different Dynamics
applications
• Integration between Dynamics 365 and a legacy
system
• Integration between On-Premise and Online
Dynamics 365 systems
• Synchronize data between systems while migration
project is ongoing
22. Approaches to Data Integration
1 – Custom
Coding
0 – No Data
Integration
Integration Platform
as a Service
2 - iPaaS 3 – Dynamics 365
Data Integration
Dynamics
365
23. Approaches 1: Custom Coding
Dynamics
365
• Detailed API and
Application Knowledge
Required
• High Integration Costs Put
Profitability at Risk
• Highly Skilled Developers
Required
• Significant Support
Requirements
• Do not forget about
integration processes
orchestration
24. Dynamics CRM Architecture
Reporting
(Dashboards, Charts, Excel,
FetchXML and SRS)
Integrated
Applications
Pre-Event Plug-ins
(.NET Assemblies)
Post-Event Plug-ins
(.NET Assemblies)
Web Services
Custom Workflow
(.NET Assemblies)
Backend Integration
Server-to-Server
Extensible Application: Form and client
side events, Ribbon, Sitemap, Web
Resources, JS libraries…
Front End
Integration
Business Entity Components
Data Access Components
Synchronous and Asynchronous Business Logic
Metadata Data
Filtered SQL Views
Data Access Platform
Workflow
Security
25. 90% of the overall
cost of custom-created
software comes after initial
development
- Gartner Research
Hey, That Was Tougher Than We Thought It Would Be…
26. Approaches 2: iPaaS
2 - iPaaS
Dynamics
365
• iPaaS reduces integration costs
• Developer Skill Level Not
Required
• Reusable Architecture /
Unified Software Design
• Faster Integration Setup
• Integration Processes
Orchestration is usually out-of-
box
• Simplified API Management
• Shorter deployment & Faster
time to market
• Faster response to run-time
issues
• Agile customization of
integrations
• Build Once, Connect to Many
29. Dynamics CRM 2011
Business Entities
Scribe Publisher QueueSales Order
Plugins
Scribe Plugin for
Dynamics CRM 2011
Dynamics CRM Web Services
Scribe ServerScribe Console
Integration
Process
Data
Monitor
Data View
Scribe Internal Queues
ScribeIn
ScribeRetry
ScribeDeadMessage
CRM ScribeIn
CRM ScribeFailed
Scribe Windows Services
Scribe Bridge
Server
Scribe Message
Server
Scribe
Monitor
Server
Scribe Event Manager
Scribe Admin
Server
Scribe Adapters
Adapter for
Dynamics CRM
2011
(On-Premises)
Adapter for XML
Adapter for Web
Services
Scribe Internal Database
SAP
NetWeaver
ABAP Code
BAPIs
31. Approaches 3:
Dynamics 365 Data Integration
Dynamics
365
This feature is PREVIEW. If you are interested in participating in the preview program,
contact us at cdspreviewprogs@microsoft.com
• New Data Integration
Feature by Microsoft
• Currently available as a
tab in the PowerApps
admin center
• Enables the flow of data
between Microsoft
Dynamics 365 products
through the Common
Data Service
34. New Skills Era
• „IQ gets you hired, EQ gets you promoted”
Phil Campbell, M.Ed. RCC, Counsellor-Coordinator
35. Backup 1: Useful Links
Install Microsoft Dynamics 365 for
Outlook
Deploy Office 365 Groups
Enable OneNote integration
Deploy Dynamics 365 App for
Outlook
Enable OneDrive for Business
Enable Office Delve
Dynamics 365 data integration
Scribe Software Company Page
Scribe Integration Platform for
Dynamics 365
Watch a Demo of Scribe Online and
Dynamics 365
36. Contact Us
Dmytro Kuiavets
Old style
Dmytro Golodiuk
New style
M +38.066.349.6158
S Dmytro_Kuiavets
dmytro.kuiavets@globallogic.com
Editor's Notes
Питання:
1.
2.
3.
Питання:
1.
2.
3.
З'являються по порядку
Common service data tier
The data tier is the lowest level and consists of a database (loosely speaking) and a well-defined data access layer. The data management tier with Microsoft CRM supports Microsoft SQL Server as the primary data store. The data access layer provides a consistent programming interface for the service developer, which abstracts platform business logic from the underlying data source.
The domain tier is the only direct consumer of the common service data layer.
Application and custom business logic
Just as there are two distinct presentation clients in Microsoft CRM, there are also two application layers. For the Outlook-based client, a lightweight application framework was built to support the Web-based application logic, but in a disconnected mode. The browser client uses Microsoft ASP.NET application components within an application framework. There is little business logic within the application tiers; the majority of application logic revolves around rendering and data validation. The Microsoft CRM application layer only adds a small amount of customized business logic; the majority was "built-in" to the platform itself.
Both application tiers use XML messages to communicate with the underlying platform layer. Communication between the application tier and the platform tier uses SOAP for both Outlook- and browser-based clients.
Service tier: domain logic
The service tier is responsible for creating problem domain-specific objects. This layer contains the building blocks for an application; but, by itself, is nothing more than a collection of related objects. However, the interaction between those objects within the domain can be assumed to implement more extensible logic, such as the Quote to Order to Invoice processing and pricing logic. The service tier contains more than just the Microsoft CRM business objects. It’s responsible for controlling access to objects and the database, raising events for workflow processes and custom business logic implementations.
The user interface and presentation tier
Microsoft CRM has two distinct presentation components, Microsoft Internet Explorer as the rich, Web-based4 user experience; and Microsoft Outlook as the rich, Microsoft Windows operating system-based experience. Both components make use of the rendering technology built into Internet Explorer. The internal rendering engine is hosted inside Outlook to present the same general look and feel as the Web application, but without the need for a Web server.
AdminServer - Provides an access point for the Console and starts Scribe Internal Database maintenance functions if maintenance is enabled.
MonitorServer - Hosts the monitoring process.
BridgeServer - Hosts processes supporting Publishers and Bridges.
MessageServer - Hosts processes supporting Microsoft Message Queuing (MSMQ).
EventManager - Hosts automated DTS file execution based on Time, File, or Query.