{"id":5145,"date":"2016-12-19T20:29:38","date_gmt":"2016-12-19T20:29:38","guid":{"rendered":"https:\/\/blogs.msdn.microsoft.com\/premier_developer\/?p=5145"},"modified":"2019-02-14T20:27:47","modified_gmt":"2019-02-15T03:27:47","slug":"how-to-import-related-data-into-dynamics-365","status":"publish","type":"post","link":"https:\/\/devblogs.microsoft.com\/premier-developer\/how-to-import-related-data-into-dynamics-365\/","title":{"rendered":"How to Import Related Data into Dynamics 365"},"content":{"rendered":"

In this post, Senior ADM Justin Scott<\/a> walks us through how to maintain entity\/table relationships when importing data into Dynamics 365.<\/p>\n

\n

A recent project I was on involved bringing over customer and contact information from another proprietary CRM application. Being newer to the Dynamics platform, one challenge was to figure out how to maintain the relationships between two related tables (tables are known as \u201centities\u201d in Dynamics 365), such as the case we had here between Companies and Contacts. In the application that we were importing data from, there was a 1:N foreign key relationship between the companies and contacts. This meant that each company can have many contacts, and each contact could belong to one company as shown in the ERD diagram below:<\/p>\n

\"dynamics1\"<\/a><\/p>\n

You can use this relationship during the import, but afterwards, this same foreign key concept would not make sense considering Dynamics 365 takes care of entity relationships without the need to maintain your own foreign keys.\u00a0 Below I shared the steps needed to import the Companies and Contacts while keeping the relationships. The key concept is to map the foreign key just for importing purposes, and then let the system maintain the relationships going forward.<\/p>\n

1. <\/b>Get the data needed to be imported into csv files<\/b><\/h2>\n

\u00a0\u00a0 a.<\/strong> Export Company table data into an excel file including its primary key as a column.\n\u00a0\u00a0 b.<\/strong> Export Contact info into a second excel file, being sure to include the foreign key column that references the Company key column.\n\u00a0\u00a0 c.<\/strong> Be sure that both files have their column names as the first row of the files.\n\u00a0\u00a0 d.<\/strong> Save the Company and Contact files as separate comma-separated values (csv) files after all data grooming is complete.<\/p>\n

2. <\/b>Open the Dynamics 365 Import Wizard<\/b><\/h2>\n

\u00a0\u00a0 a.<\/strong> If you don\u2019t already have a Dynamics 365 account, you can sign up for a free trial here<\/a>.\n\u00a0\u00a0 b.<\/strong> Once logged into Dynamics 365, go to the import wizard by going to Settings<\/b> > Data Management<\/b> from the main CRM Dynamics home screen\n\"dynamics2\"<\/a>\n\u00a0\u00a0 c.<\/strong> Choose Imports from the Data Management form\n\"dynamics3\"<\/a>\n\u00a0\u00a0 d.<\/strong> Select the Import Data link at the top of the Imports form\n\"dynamics4\"<\/a>\n<\/b><\/p>\n

3. <\/b>Import your Contact records<\/b><\/h2>\n

\u00a0\u00a0 a.<\/strong> Since the contact records will have a column that links to the company records, we must import the company records first. Browse to your Company csv file you created.<\/p>\n

\u00a0\u00a0 b.<\/strong> For the Company data, I decided to utilize the existing \u201cAccount\u201d entity since it holds company-type information. Since I was using an existing entity, I need to choose one of the system data maps to make it easier to map fields:\n\"dynamics5\"<\/a>\n\u00a0\u00a0 c.<\/strong> You will need to go through each field in your import file and map it to a field in Dynamics 365.\n\"dynamics6\"<\/a><\/p>\n

\u00a0\u00a0 d.<\/strong> The Required Fields<\/b> section is looking for the main user-friendly way to identify the record. In our case, we would map the Company name to the existing Account Name<\/b> field.<\/p>\n

\u00a0\u00a0 e.<\/strong> Any new fields that can be added by selecting Create New Field<\/b> and then choosing what datatype it is.<\/p>\n

\"dynamics7\"<\/a><\/p>\n

\u00a0\u00a0 Note:<\/strong> There are only a few datatypes to choose from when using the import wizard, and the field data type cannot be changed later. The data types available are shown below:<\/p>\n

\"dynamics8\"<\/a><\/p>\n

\u00a0\u00a0 f.<\/strong> After all mappings are complete, select Next<\/b> to begin the import. A job is then submitted to begin the import process. This job can take a while to run, but you can view the progress and status of the run in the My Imports<\/b> section as shown below. This area will also show you if any errors occurred during the import.<\/p>\n

\"dynamics9\"<\/a><\/p>\n

Selecting the file name will give you additional details including information about any import errors that occurred.<\/p>\n

4.<\/strong> Import your Contact records<\/b><\/h2>\n

\u00a0\u00a0 a.<\/strong> See step 2 for how to open the import wizard.<\/p>\n

\u00a0\u00a0 b.<\/strong> Once in the import wizard, browse to your Contact csv file you created.<\/p>\n

\u00a0\u00a0 c.<\/strong> For the Contact data, I utilized the existing \u201cContact\u201d entity. Since I was using an existing entity, I need to choose one of the system data maps to make it easier to map fields:<\/p>\n

\"dynamics10\"<\/a><\/p>\n

\u00a0\u00a0 d.<\/strong> You will need to go through each field in your import file and map it to a row in Dynamics 365.<\/p>\n

\u00a0\u00a0 e.<\/strong> The key difference between the overall process of uploading Company verses contact records is that we want to define a field in Contacts that helps us link the contacts to the companies upon doing the import. To do this, we need to map the foreign key given to us by the source system. In the import dialog, the Type<\/b> should be set to Lookup<\/b>, the Related Record Type<\/b> should be set to the entity to relate to (in this case Company), and the Referred Field<\/b> should be set to the field that will match the foreign key (in this case ID) being imported as shown below.<\/p>\n

\"dynamics11\"<\/a><\/p>\n

\u00a0\u00a0 Note:<\/strong> The imported contact data had a column called LINK_COMP_ID<\/b> that was a foreign key in the source system to the field named ID<\/b> in the Company Entity that has already had its data imported.<\/p>\n

Summary<\/b><\/h2>\n

In the steps above we showed you how to take related data from another application and maintain that relationship when importing the data into the Dynamics 365. When doing this, Dynamics is designed to understand that you only need this mapping for the import and that after the import, this foreign key relationship will be maintained internally. In other words, you could drop the key and foreign key columns after all the imports were completed, and the relationships would still exist. Taking it a step further, having these relationships in the system sets you up nicely for creating a company form that has all the related company contacts listed on the same form.<\/p>\n

\n

Premier Support for Developers<\/strong><\/a> provides strategic technology guidance, critical support coverage, and a range of essential services to help teams optimize development lifecycles and improve software quality.\u00a0 Contact your Application Development Manager (ADM) or email us<\/a> to learn more about what we can do for you.<\/p>\n","protected":false},"excerpt":{"rendered":"

In this post, Senior ADM Justin Scott walks us through how to maintain entity\/table relationships when importing data into Dynamics 365. A recent project I was on involved bringing over customer and contact information from another proprietary CRM application. Being newer to the Dynamics platform, one challenge was to figure out how to maintain the […]<\/p>\n","protected":false},"author":582,"featured_media":37840,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"footnotes":""},"categories":[1],"tags":[3],"class_list":["post-5145","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-permierdev","tag-team"],"acf":[],"blog_post_summary":"

In this post, Senior ADM Justin Scott walks us through how to maintain entity\/table relationships when importing data into Dynamics 365. A recent project I was on involved bringing over customer and contact information from another proprietary CRM application. Being newer to the Dynamics platform, one challenge was to figure out how to maintain the […]<\/p>\n","_links":{"self":[{"href":"https:\/\/devblogs.microsoft.com\/premier-developer\/wp-json\/wp\/v2\/posts\/5145","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/devblogs.microsoft.com\/premier-developer\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/devblogs.microsoft.com\/premier-developer\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/premier-developer\/wp-json\/wp\/v2\/users\/582"}],"replies":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/premier-developer\/wp-json\/wp\/v2\/comments?post=5145"}],"version-history":[{"count":0,"href":"https:\/\/devblogs.microsoft.com\/premier-developer\/wp-json\/wp\/v2\/posts\/5145\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/premier-developer\/wp-json\/wp\/v2\/media\/37840"}],"wp:attachment":[{"href":"https:\/\/devblogs.microsoft.com\/premier-developer\/wp-json\/wp\/v2\/media?parent=5145"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/premier-developer\/wp-json\/wp\/v2\/categories?post=5145"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/premier-developer\/wp-json\/wp\/v2\/tags?post=5145"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}