Dynamics 365 9.1 - Import data from excel for external entity





.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty{ height:90px;width:728px;box-sizing:border-box;
}







0















I'm trying to import data describing contacts from excel file.
Under my Contact entity Iv'e created a relationship to a new customized entity (Source).
How can I import data about my contacts from excel file including the Source which is a different entity Iv'e created?



When I import the data, there's no option to mention that the Source field is a lookup to another entity.



Thanks everyone,
Idan










share|improve this question





























    0















    I'm trying to import data describing contacts from excel file.
    Under my Contact entity Iv'e created a relationship to a new customized entity (Source).
    How can I import data about my contacts from excel file including the Source which is a different entity Iv'e created?



    When I import the data, there's no option to mention that the Source field is a lookup to another entity.



    Thanks everyone,
    Idan










    share|improve this question

























      0












      0








      0








      I'm trying to import data describing contacts from excel file.
      Under my Contact entity Iv'e created a relationship to a new customized entity (Source).
      How can I import data about my contacts from excel file including the Source which is a different entity Iv'e created?



      When I import the data, there's no option to mention that the Source field is a lookup to another entity.



      Thanks everyone,
      Idan










      share|improve this question














      I'm trying to import data describing contacts from excel file.
      Under my Contact entity Iv'e created a relationship to a new customized entity (Source).
      How can I import data about my contacts from excel file including the Source which is a different entity Iv'e created?



      When I import the data, there's no option to mention that the Source field is a lookup to another entity.



      Thanks everyone,
      Idan







      dynamics-crm microsoft-dynamics dynamics-crm-2013 dynamics-crm-365






      share|improve this question













      share|improve this question











      share|improve this question




      share|improve this question










      asked Nov 24 '18 at 9:55









      user1420373user1420373

      183




      183
























          2 Answers
          2






          active

          oldest

          votes


















          0














          When you set up your Contact import file you can add a column to identify the Source. The most obvious options would be the name or the ID.



          Here's an example of adding the Account name to a Contact import:



          Contact Import



          When you do the mapping, you can tell it which field on the Source entity to map to. In the above example, it maps to Account Name.



          Account Name Mapping






          share|improve this answer
























          • Thanks Aron. What if I needed to keep more than one source? Your solution helps me saving a specific source for a contact, but it may be necessary to add another source in the future to that contact (not by import, from crm itself).

            – user1420373
            Nov 24 '18 at 12:47











          • If Source is a lookup on the Contact entity, then you can only have one at a time. If you want multiple Sources per Contact, you'll likely need a many-to-many (N:N) relationship between Contact and Source. You can use the out-of-box N:N relationship, or if the relationship requires some additional info, you can create your own linking entity.

            – Aron
            Nov 24 '18 at 12:53













          • But if I use a many-to-many relationship between Contact and Source, how do I import a source from excel file?

            – user1420373
            Nov 24 '18 at 13:01











          • I've never used the bulk import tool to import data to an OOB N:N so you'd have to research whether that's possible. If you use a custom linking entity, you can import to it like any other entity, populating both the Contact and Source lookups via name or id.

            – Aron
            Nov 24 '18 at 13:57



















          0














          During the import, lookup fields will take the right related value by searching the Name of that record like:

          CustomerId(string);CountryId(lookup);

          exampleCustomerId; Italy;



          Italy is the name of that specific record.
          Relationship is automatically solved.



          Hope it helped :)






          share|improve this answer
























            Your Answer






            StackExchange.ifUsing("editor", function () {
            StackExchange.using("externalEditor", function () {
            StackExchange.using("snippets", function () {
            StackExchange.snippets.init();
            });
            });
            }, "code-snippets");

            StackExchange.ready(function() {
            var channelOptions = {
            tags: "".split(" "),
            id: "1"
            };
            initTagRenderer("".split(" "), "".split(" "), channelOptions);

            StackExchange.using("externalEditor", function() {
            // Have to fire editor after snippets, if snippets enabled
            if (StackExchange.settings.snippets.snippetsEnabled) {
            StackExchange.using("snippets", function() {
            createEditor();
            });
            }
            else {
            createEditor();
            }
            });

            function createEditor() {
            StackExchange.prepareEditor({
            heartbeatType: 'answer',
            autoActivateHeartbeat: false,
            convertImagesToLinks: true,
            noModals: true,
            showLowRepImageUploadWarning: true,
            reputationToPostImages: 10,
            bindNavPrevention: true,
            postfix: "",
            imageUploader: {
            brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
            contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
            allowUrls: true
            },
            onDemand: true,
            discardSelector: ".discard-answer"
            ,immediatelyShowMarkdownHelp:true
            });


            }
            });














            draft saved

            draft discarded


















            StackExchange.ready(
            function () {
            StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53457018%2fdynamics-365-9-1-import-data-from-excel-for-external-entity%23new-answer', 'question_page');
            }
            );

            Post as a guest















            Required, but never shown

























            2 Answers
            2






            active

            oldest

            votes








            2 Answers
            2






            active

            oldest

            votes









            active

            oldest

            votes






            active

            oldest

            votes









            0














            When you set up your Contact import file you can add a column to identify the Source. The most obvious options would be the name or the ID.



            Here's an example of adding the Account name to a Contact import:



            Contact Import



            When you do the mapping, you can tell it which field on the Source entity to map to. In the above example, it maps to Account Name.



            Account Name Mapping






            share|improve this answer
























            • Thanks Aron. What if I needed to keep more than one source? Your solution helps me saving a specific source for a contact, but it may be necessary to add another source in the future to that contact (not by import, from crm itself).

              – user1420373
              Nov 24 '18 at 12:47











            • If Source is a lookup on the Contact entity, then you can only have one at a time. If you want multiple Sources per Contact, you'll likely need a many-to-many (N:N) relationship between Contact and Source. You can use the out-of-box N:N relationship, or if the relationship requires some additional info, you can create your own linking entity.

              – Aron
              Nov 24 '18 at 12:53













            • But if I use a many-to-many relationship between Contact and Source, how do I import a source from excel file?

              – user1420373
              Nov 24 '18 at 13:01











            • I've never used the bulk import tool to import data to an OOB N:N so you'd have to research whether that's possible. If you use a custom linking entity, you can import to it like any other entity, populating both the Contact and Source lookups via name or id.

              – Aron
              Nov 24 '18 at 13:57
















            0














            When you set up your Contact import file you can add a column to identify the Source. The most obvious options would be the name or the ID.



            Here's an example of adding the Account name to a Contact import:



            Contact Import



            When you do the mapping, you can tell it which field on the Source entity to map to. In the above example, it maps to Account Name.



            Account Name Mapping






            share|improve this answer
























            • Thanks Aron. What if I needed to keep more than one source? Your solution helps me saving a specific source for a contact, but it may be necessary to add another source in the future to that contact (not by import, from crm itself).

              – user1420373
              Nov 24 '18 at 12:47











            • If Source is a lookup on the Contact entity, then you can only have one at a time. If you want multiple Sources per Contact, you'll likely need a many-to-many (N:N) relationship between Contact and Source. You can use the out-of-box N:N relationship, or if the relationship requires some additional info, you can create your own linking entity.

              – Aron
              Nov 24 '18 at 12:53













            • But if I use a many-to-many relationship between Contact and Source, how do I import a source from excel file?

              – user1420373
              Nov 24 '18 at 13:01











            • I've never used the bulk import tool to import data to an OOB N:N so you'd have to research whether that's possible. If you use a custom linking entity, you can import to it like any other entity, populating both the Contact and Source lookups via name or id.

              – Aron
              Nov 24 '18 at 13:57














            0












            0








            0







            When you set up your Contact import file you can add a column to identify the Source. The most obvious options would be the name or the ID.



            Here's an example of adding the Account name to a Contact import:



            Contact Import



            When you do the mapping, you can tell it which field on the Source entity to map to. In the above example, it maps to Account Name.



            Account Name Mapping






            share|improve this answer













            When you set up your Contact import file you can add a column to identify the Source. The most obvious options would be the name or the ID.



            Here's an example of adding the Account name to a Contact import:



            Contact Import



            When you do the mapping, you can tell it which field on the Source entity to map to. In the above example, it maps to Account Name.



            Account Name Mapping







            share|improve this answer












            share|improve this answer



            share|improve this answer










            answered Nov 24 '18 at 12:33









            AronAron

            2,40831019




            2,40831019













            • Thanks Aron. What if I needed to keep more than one source? Your solution helps me saving a specific source for a contact, but it may be necessary to add another source in the future to that contact (not by import, from crm itself).

              – user1420373
              Nov 24 '18 at 12:47











            • If Source is a lookup on the Contact entity, then you can only have one at a time. If you want multiple Sources per Contact, you'll likely need a many-to-many (N:N) relationship between Contact and Source. You can use the out-of-box N:N relationship, or if the relationship requires some additional info, you can create your own linking entity.

              – Aron
              Nov 24 '18 at 12:53













            • But if I use a many-to-many relationship between Contact and Source, how do I import a source from excel file?

              – user1420373
              Nov 24 '18 at 13:01











            • I've never used the bulk import tool to import data to an OOB N:N so you'd have to research whether that's possible. If you use a custom linking entity, you can import to it like any other entity, populating both the Contact and Source lookups via name or id.

              – Aron
              Nov 24 '18 at 13:57



















            • Thanks Aron. What if I needed to keep more than one source? Your solution helps me saving a specific source for a contact, but it may be necessary to add another source in the future to that contact (not by import, from crm itself).

              – user1420373
              Nov 24 '18 at 12:47











            • If Source is a lookup on the Contact entity, then you can only have one at a time. If you want multiple Sources per Contact, you'll likely need a many-to-many (N:N) relationship between Contact and Source. You can use the out-of-box N:N relationship, or if the relationship requires some additional info, you can create your own linking entity.

              – Aron
              Nov 24 '18 at 12:53













            • But if I use a many-to-many relationship between Contact and Source, how do I import a source from excel file?

              – user1420373
              Nov 24 '18 at 13:01











            • I've never used the bulk import tool to import data to an OOB N:N so you'd have to research whether that's possible. If you use a custom linking entity, you can import to it like any other entity, populating both the Contact and Source lookups via name or id.

              – Aron
              Nov 24 '18 at 13:57

















            Thanks Aron. What if I needed to keep more than one source? Your solution helps me saving a specific source for a contact, but it may be necessary to add another source in the future to that contact (not by import, from crm itself).

            – user1420373
            Nov 24 '18 at 12:47





            Thanks Aron. What if I needed to keep more than one source? Your solution helps me saving a specific source for a contact, but it may be necessary to add another source in the future to that contact (not by import, from crm itself).

            – user1420373
            Nov 24 '18 at 12:47













            If Source is a lookup on the Contact entity, then you can only have one at a time. If you want multiple Sources per Contact, you'll likely need a many-to-many (N:N) relationship between Contact and Source. You can use the out-of-box N:N relationship, or if the relationship requires some additional info, you can create your own linking entity.

            – Aron
            Nov 24 '18 at 12:53







            If Source is a lookup on the Contact entity, then you can only have one at a time. If you want multiple Sources per Contact, you'll likely need a many-to-many (N:N) relationship between Contact and Source. You can use the out-of-box N:N relationship, or if the relationship requires some additional info, you can create your own linking entity.

            – Aron
            Nov 24 '18 at 12:53















            But if I use a many-to-many relationship between Contact and Source, how do I import a source from excel file?

            – user1420373
            Nov 24 '18 at 13:01





            But if I use a many-to-many relationship between Contact and Source, how do I import a source from excel file?

            – user1420373
            Nov 24 '18 at 13:01













            I've never used the bulk import tool to import data to an OOB N:N so you'd have to research whether that's possible. If you use a custom linking entity, you can import to it like any other entity, populating both the Contact and Source lookups via name or id.

            – Aron
            Nov 24 '18 at 13:57





            I've never used the bulk import tool to import data to an OOB N:N so you'd have to research whether that's possible. If you use a custom linking entity, you can import to it like any other entity, populating both the Contact and Source lookups via name or id.

            – Aron
            Nov 24 '18 at 13:57













            0














            During the import, lookup fields will take the right related value by searching the Name of that record like:

            CustomerId(string);CountryId(lookup);

            exampleCustomerId; Italy;



            Italy is the name of that specific record.
            Relationship is automatically solved.



            Hope it helped :)






            share|improve this answer




























              0














              During the import, lookup fields will take the right related value by searching the Name of that record like:

              CustomerId(string);CountryId(lookup);

              exampleCustomerId; Italy;



              Italy is the name of that specific record.
              Relationship is automatically solved.



              Hope it helped :)






              share|improve this answer


























                0












                0








                0







                During the import, lookup fields will take the right related value by searching the Name of that record like:

                CustomerId(string);CountryId(lookup);

                exampleCustomerId; Italy;



                Italy is the name of that specific record.
                Relationship is automatically solved.



                Hope it helped :)






                share|improve this answer













                During the import, lookup fields will take the right related value by searching the Name of that record like:

                CustomerId(string);CountryId(lookup);

                exampleCustomerId; Italy;



                Italy is the name of that specific record.
                Relationship is automatically solved.



                Hope it helped :)







                share|improve this answer












                share|improve this answer



                share|improve this answer










                answered Dec 4 '18 at 16:37









                Davide CerquaDavide Cerqua

                11




                11






























                    draft saved

                    draft discarded




















































                    Thanks for contributing an answer to Stack Overflow!


                    • Please be sure to answer the question. Provide details and share your research!

                    But avoid



                    • Asking for help, clarification, or responding to other answers.

                    • Making statements based on opinion; back them up with references or personal experience.


                    To learn more, see our tips on writing great answers.




                    draft saved


                    draft discarded














                    StackExchange.ready(
                    function () {
                    StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53457018%2fdynamics-365-9-1-import-data-from-excel-for-external-entity%23new-answer', 'question_page');
                    }
                    );

                    Post as a guest















                    Required, but never shown





















































                    Required, but never shown














                    Required, but never shown












                    Required, but never shown







                    Required, but never shown

































                    Required, but never shown














                    Required, but never shown












                    Required, but never shown







                    Required, but never shown







                    這個網誌中的熱門文章

                    Academy of Television Arts & Sciences

                    L'Équipe

                    1995 France bombings