Want to know more about Common Data Model and Service? You need to understant what's the difference between CDS for Apps and Analytics? Feel free to use these slides and send me your feed backs.
3. Who Am I?
Nicolas Georgeault
• Founder and PPM @MuBrain Inc.
• More than 20 years of experience in
information management and 12
with Microsoft SharePoint
• Microsoft Specialist and Partner
• MVP for 9 years
• Machine Leaning certificate from
Stanford University
• Co-author of books about SharePoint
• Mad about Jazz/Blues and HorseBall
5. Agenda
• How much it costs?
• What is Common Data Model?
• What is Common Data Service?
• What’s the difference between Apps and Analytics?
• What can we do with it?
• Why is so important?
9. The Common Data Model
• Open-sourced Schema
• Standard business entities
• Commonly used concepts and activities
• well-defined, modular, and extensible
business entities
• Service Level Agreement
• Business centric
11. Open Data Initiative – Better together!
https://www.microsoft.com/en-us/open-data-initiative
13. Build modern business apps fast
Compose analytics, user experiences, and automation using
an integrated set of services from Microsoft
More efficient developers(*)
Seamlessly extend capabilities for power users and
leverage powerful Azure platform services
Business application platform innovation
Empowered power users
People who understand their business needs best can now
build apps quickly without writing code
Connected data across apps
Whether built on the Common Data Model or integrated with
existing systems, get more value from your data
Azure AppServices
Azure Service Fabric
Azure Functions
…
Azure Logic Apps
Azure API Management
BizTalk
…
Azure [Analysis Services]
Azure Data analytics
SQL Server BI
… CDM SDK
15. Let’s take this scenario
Customers
Customers
information
are centric
in any
business
But they are
spread in
many
different
systems
16. Let’s take this scenario
Customers
Each system
is using is
own data
model
System
vision of
the data
model
CRM
Support
Marketing
…
Billing system
Invoices
Payments
…
Delivery system
Timesheets
Expenses
…
Communication
system
Emails
Phones
…
Collaboration
system
Documents
Sites
…
19. Second scenario
Customers
Only one
application
connection
Only one
dashboard
connection
CRM
Support
Marketing
…
Billing system
Invoices
Payments
…
Delivery system
Timesheets
Expenses
…
Communication
system
Emails
Phones
…
Collaboration
system
Documents
Sites
…
Customer
20. Second scenario
Customers
Only one
application
connection
Only one
dashboard
connection
CRM
Support
Marketing
…
Billing system
Invoices
Payments
…
Delivery system
Timesheets
Expenses
…
Communication
system
Emails
Phones
…
Collaboration
system
Documents
Sites
…
Customer
This is the idea of the Common Data Service
25. Security
• You can secure: Databases, Entities, Records
• Databases can be Open (no security evaluated) or Restricted (security evaluated)
• Entities: can be secured for Create/Read/Update/Delete actions
• Records: Record-level Security in preview!
• Security is configured via Portal or the SDK
• Security applies to all endpoints (PowerApps, Flow, Power BI, Excel, etc.)
Environment Roles Database Roles
28. Build pro dev apps with the CDS SDK
• CDS SDK preview in progress
• Enables developers and ISVs to build apps on data in the CDS, or integrate
their services with CDS
• Facilitates CRUD, queries and management of the Common Data Model
• SDK can be used to implement advanced business logic against CDS (joins,
etc.), deploy as Azure Function for consumption in Power Apps
• Same SDK that our 1st party apps are using
29. Exemple: Dynamics 365 for Talent
• Dynamics 365 for Talent
suite is built on the
Common Data service
with the CDS SDK!
• Workforce management
and other apps coming
31. Microsoft Flow and Logic Apps
• Create workflows using Microsoft Flow
and the Common Data Service
• Conditional entries based on entity state
• Take actions including: Create Record,
Delete Record
33. Power BI
• Users can create reports directly against data
in the Common Data Service with Power BI
Desktop
• Data is grouped in “Perspectives” to make it
easier to start building the reports you want.
• Perspectives are meaningful grouping of
Entities for reporting purposes
• perspectives for standard entities are pre-defined
• ability to customize perspectives in preview
34. Microsft Excel
• CDS Entities (Standard and Custom)
can be managed via the Excel Add-In
• Excel Add In supports CDS languages,
picklists and rich lookup experience.
36. What is at the heart of the digital transformation?
…Data!
41. • ERPs systems are aggregations of continuous acquisitions
• No consistency in the data structures
• Multiple points of failure
• Multiple security holes
• Business data are spread
• Business agility with high migration complexity
45. Be Careful
Graph Database ≠ Microsoft Graph
What is a Graph Database?
https://en.wikipedia.org/wiki/Graph_database
Why you should use a Graph Database?
https://www.infoworld.com/article/3251829/nosql/why-you-should-use-a-graph-database.html
48. References
• Documentation:
• http://aka.ms/commondataservice
• Introduction to Entities
• https://www.youtube.com/watch?v=1VjFi6m1mOE
• Microsoft Common Data Service Guided Learning: Using
the data model - Custom Entities
• https://www.youtube.com/watch?v=lR4uv_GcbMI
• This Slidedeck
• https://www.slideshare.net/ngeorgeault/sps-vancouver-2018-what-is-cdm-and-
cds
60. Overview of building a model-driven app
• Component-focused approach to app development
• No code and the apps you make can be simple or very complex
• Unlike canvas app development where the designer has complete
control over app layout, with model-driven apps much of the layout is
determined for you and largely designated by the components you
add to the app.
Notes de l'éditeur
Open-sourced definition of standard business entities
Commonly used concepts and activities across a variety of business and application domains
The Common Data Model offers well-defined, modular, and extensible business entities such as Account, Business Unit, Case, Contact, Lead, Opportunity, and Product, as well as interactions and relationships between vendors, workers, and customers, such as activities and service level agreements.