On this article we will discuss the some particular features of Dynamics 365 CE that enable Dynamics Professionals to customize and evolve the tool before even using code.
My strategy will be to present this features or areas in Dynamics 365 CE and compare it with common tools and practices Software Developers use to deliver solutions.
Let us start by describing Dynamics 365 CE core components.
The core component in Dynamics 365 CE is called "Entity". Entities can be compared to relational databases object known as "Tables". (In fact, since Dynamics 365 CE uses SQL Server DBs in the back-end, Dyn365 entities translates into SQL DB tables. We will discuss this later on another post). Entities are composed by Fields and Relationships in the same fashion as SQL tables have Fields, Primary and Foreign Keys.
In Dynamics 365, we don't get to create different indexes as we do in a SQL relational database.
Fields are created in dynamics directly through it's web UI. Many of the data types available in SQL Server are available in Dyn 365.
Click the link to view a list of all data types available in Dyn 365 v9.0:
Types of fields and field data types
In Dyn365 relationships work almost in the same way as SQL relationships. The only particular type that does not exist in Dyn365 is a 1 to 1 relation.
Create and edit relationships between entities
Dynamics 365 allows developers/customisers to define the entry fields and their disposition on a form to be presented to a end-user for creating new or editing existing records.
Create and design forms
In Dyn365, professionals can determine how lists are presented to an end-user. Developers can define the order of columns and the filters to be applied on a particular record list.
Create or edit views (lists)