Developers: Get started with Common Data Service
Where to start depends on what problem you are trying to solve. This guide includes information about a wide range of capabilities and it is unlikely you will ever use all of them. The following sections include several of the key areas to begin.
Work with data using Web services
There are two different web services that you can use to work with data: Web API and Organization service.
Which one you should use depends on the type of project you are working on. More information: Work with data using code
Applying business logic
The most common extensions created using code involve automating the processes used by businesses. You can find a summary of options available for you in Apply business logic with code. Each of these approaches are typically invoked based on events that occur on the server, so understanding of the Event Framework will be valuable.
Integrate with external data
Data management capabilities in Common Data Service not only lets you work with data within Common Data Service, but also effectively interact with external data critical to your business. More information:
Common Data Service entities
Entities store the business data you will work with. An understanding what they are and how to work with them is essential. More information:
Work with metadata
Developing a good working understanding of the metadata in the system can help you understand how Common Data Service platform works. Generally you will use designers to add, update, or delete entity schema that defines metadata, but both the Web API and the Organization service web services provide capabilities to perform CRUD operations on the entity schema. More information: Work with metadata using code
Use solutions to package and distribute extensions
If you are going to distribute the extensions you create or any customizations that they depend on, you will need to understand solutions. Solutions created by an individual are relatively simple to work with and don't require the skills of a developer. But for a team of developers to work productively with solutions and use effective application lifecycle management principles requires a more sophisticated approach. More information:
- Introduction to solutions
- SolutionPackager toolSolutionPackager tool
- Package Deployer tool
- Publish your app on AppSource
Create client applications and authentication
When you create extensions that apply business logic on the server you will not need to include code to authenticate. The only times you will need to authenticate are when you are creating a client application. A simple console client application is a good way to familiarize yourself with the Common Data Service APIs. Enabling a means to connect to the data is an important first step. Most of the code samples provided include a means to authenticate. The Xrm.Tooling connector provides capabilities to make authentication simpler. More information:
Send feedback about: