In this recipe, we'll go through the process of creating a new entity, look at how to configure such an entity, and in the end, how to clean up an entity that's not required in our solution package.
All customizations in this book are created as part of a solution. As such, we will be reusing the previously created solution.
In order to proceed, log in to your existing Dynamics CRM 2011 instance and navigate to the solution we created previously.
In the created solution package, we will be adding a new entity to store a list of all countries. We want this listing to be manageable by a user with proper permissions, so that it can be updated as they do business with new countries.
Country
, leave the Requirement Level with the default value Business Required, and the Type as Single Line of Text.Removing an entity that is not being used by our customization is again a relatively simple task.
Each entity is stored in the database as a set of two tables. The first one stores the base entity, while the second one stores the customizations to the entity. Creating a new entity in fact creates this set of tables, one that stores the entity generic properties, and another that stores each data fields defined. So, in our case, we will have a table called new_countryBase
, and another called new_countryExtensionBase
, as seen in the following two images:
The extended table has the following definition:
This information is only available while working On-Premise. With a Dynamics CRM 2011 Online instance, there is no direct access to the database.
Making modifications directly to the database in Dynamics CRM 2011 is not supported. This can cause various issues. All data access should go through web services. When creating custom reports, use the views. They also present the trimmed data security.
3.145.97.109