Introduction to common data service Flashcards
What is CDS?
The Common Data Service is a cloud-based solution that easily structures a variety of data and business logic to support interconnected applications and processes in a secure and compliant manner.Wh
Security: (azure active directory)
Common Data Service handles authentication with Azure Active Directory (AAD) to allow for conditional access and multi-factor authentication. It supports authorization down to the row and field level and provides rich auditing capabilities.
Logic for CDS; business rules, workflows, dupes
Common Data Service allows you to easily apply business logic at the data level. Regardless of how a user is interacting with the data, the same rules apply. These rules could be related to duplicate detection, business rules, workflows, or more.
Data: discover, model, report, validate
Common Data Service offers you the control to shape your data, allowing you to discover, model, validate, and report on your data. This control ensures your data looks the way you want regardless of how it is used.
Storage: physical data
Common Data Service stores your physical data in the Azure cloud. This cloud-based storage removes the burden of worrying about where your data lives or how it scales. These concerns are all handled for you.
Integration: APIs, webhooks, eventing, data exports
Common Data Service connects in different ways to support your business needs. APIs, webhooks, eventing, and data exports give you flexibility to get data in and out.
Scalability: storage per instance
Entities can hold millions of items, and you can extend the storage in each instance of a Common Data Service database to four (4) terabytes per instance. The amount of data that is available in your instance of Common Data Service is based upon the number and type of licenses that are associated with it. Data storage is pooled between all licensed users, so you can allocate storage as needed for each solution that you build. Additional storage can be purchased if you need more storage than what is offered within standard licensing.
Entities (like SFDC objects, leads, opprtys, etc)
An entity is a logical set of records that is used to store data. Entities are like tables in a relational database, but there are subtle differences. Records within an entity contain many fields to manage individual pieces of information about a single record.
CDM vs CDS
The standard entity design in a Common Data Service database is based upon an open data model standard called Common Data Model. Common Data Model is a logical design that includes a set of open-sourced, standardized, extensible data entities and relationships that Microsoft and its partners have published in an industry-wide initiative called the Open Data Initiative. This collection of predefined entities, attributes, semantic metadata, and relationships form the basis of the Common Data Model.
Open Data Initiative
The Common Data Model is the output of the Open Data Initiative. It provides a platform for a single, comprehensive view of your data, bringing together and enriching data from all your lines of business, across all your systems, to deliver real-time intelligence back into your applications and services. Microsoft has partnered with SAP and Adobe on the Open Data Initiative.
Common Data Service structure and benefits
The key benefit of using Common Data Model as the basis of a Common Data Service database is simplified integration of any solutions that use a Common Data Model schema because the standard entities of the solution are the same. You will also be able to take advantage of a rich ecosystem of solutions that vendors have built from using Common Data Model.
Types of entities (like standard vs custom objects)
Standard - The base set of entities that are created for every instance of a Common Data Service database. You can add more fields to any entity, but you can only delete fields from a custom entity.
Complex - Entities that contain complex, server-side business logic, including real-time workflows or plug-ins. Some of the entities that are used in Dynamics 365 applications are complex. Care must be taken if you add server-side logic to ensure that users have the proper license to use the complex entity. Additional information about complex entities can be accessed by following the link within the summary unit of this module.
Entity Ownership
You cannot change the type of entity ownership after creating the entity
User or team owned (security by user / team)
Organization-owned (all or nothing)
Business Rules - data validation
Regardless of where the data is coming from (canvas or model app) data is validated using business rules
Create business rules and recommendations to apply logic and validations without writing code or creating plug-ins.
Business rules provide a simple interface to implement and maintain fast-changing and commonly used rules
You can validate data regardless of what app it was entered from (scope)
Business rules can be copied (Save As)
They can be deactivated in order to make changes
Activate a business rule to apply changes
Why use CDS?
Easy to manage
Easy to secure
Access your Dynamics 365 Data
Rich metadata
Logic and validation
Integration tools
Productivity tools
