CRM Configuration Migration Tool: Work Smarter with Metadata Entities
Dynamics for Customer Engagement apps uses a metadata the information in the attributes and relationships are used to create the. Microsoft Dynamics CRM SP1 SDK includes a new tool for easily moving Configuration Migration Tool: Working Smarter with Metadata Entities So, we have both a 1:N and N:1 relationship between our entities, . Import Information 8 Processing Entity Email Attachment, 1 Records in this entity. Applies to Dynamics for Customer Engagement apps version 9.x From the Tools navigation area you can select Entity Metadata to inspect Edit Relationship: Open the selected relationship form in the default . Get started with SharePoint integration · Enable document management for entities.
This includes information about entities, attributes, relationships, and option sets. The Dynamics for Customer Engagement Web services contain the messages that you use to read or write the definitions for all the entities each organization. It can also be used to build a client-side metadata cache, which is useful for applications that access the metadata frequently.
For example, you may want to create a custom search solution that supports all entities, even those created after the solution has been installed. A very important role of the metadata is to provide the framework to deliver a fully metadata driven user interface.
The entity metadata controls the grid and form layout, and how navigation options are presented.
When you create a custom entity, the information in the attributes and relationships are used to create the appropriate user interface for that entity. In addition, this supports multiple languages in the user interface so that one user may see labels and other text in a different language from another user. These languages and the associated labels are stored in the metadata.
The language edition of Dynamics for Customer Engagement server that is installed for an organization is considered its base language. To read more about metadata and how to find metadata reports, see Entity Metadata.
The following table lists the objects described by the metadata. Metadata object Description Entity An entity is a container for data, similar to a table in a traditional database.
Each entity contains a set of attributes. N relationshipbut in order to make the experiment more interesting, I also added a lookup on the category form that allows selecting the default subcategory to be used. So, we have both a 1: We can pick from entities included in a specific solution. After selecting the entity, we can either choose which fields we want to transfer data from or just be lazy and add the whole entity into our schema definition.
Configuration Migration Tool: Working Smarter with Metadata Entities
Save and Export will give us an XML file with the contents from the included entities, fields and relationships. The next step is the data export. The last step is to connect to a different organization that already has the same schema. The CMT window will again show the details of the process and inform you about the number of records imported.
Now we have two CRM orgs with identical data in our chosen configuration entities and fields. Even though the CMT log showed that 6 Subcategory records had been imported, all I had in my target system was 4 records: The subcategory value for Category A was actually the Subcategory 1 record that was a child record of Category B in the source system.
CMT provides access to the log file of the latest import job conveniently from the top toolbar, so I opened up the logs and went to review the entries. So, it appears that because subcategory records with primary field values 1 and 2 had already been inserted into the target system, CMT did not create the last two records but instead updated the contents of the earlier records, thus creating the mismatches discovered.
CRM – Understanding CRM Metadata – Hosk's Dynamic CRM Blog
To change this, you should click Tools — Configure Import Settings and then select the fields that determine a unique record in your source data.
Since there was now a mismatch between the configuration data in different environments, this was a good opportunity to try out the capabilities of CMT in maintaining changes in such data.
To make the sample data a bit easier to match, I decided to update the subcategory names primary fields with the parent category prefix, such as A1, B2 and so on.