Converting lookup relationship into master detail relationship

The name of the pictureThe name of the pictureThe name of the pictureClash Royale CLAN TAG#URR8PPP





.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty margin-bottom:0;







up vote
2
down vote

favorite
1












I had converted lookup relationship into master detail for a child object which contains lakhs of records. So when a parent record is deleted, all these child records has to be deleted automatically since now the relation has been converted into master-detail. Will this standard deletion throws some error since the records size is huge?










share|improve this question



























    up vote
    2
    down vote

    favorite
    1












    I had converted lookup relationship into master detail for a child object which contains lakhs of records. So when a parent record is deleted, all these child records has to be deleted automatically since now the relation has been converted into master-detail. Will this standard deletion throws some error since the records size is huge?










    share|improve this question























      up vote
      2
      down vote

      favorite
      1









      up vote
      2
      down vote

      favorite
      1






      1





      I had converted lookup relationship into master detail for a child object which contains lakhs of records. So when a parent record is deleted, all these child records has to be deleted automatically since now the relation has been converted into master-detail. Will this standard deletion throws some error since the records size is huge?










      share|improve this question













      I had converted lookup relationship into master detail for a child object which contains lakhs of records. So when a parent record is deleted, all these child records has to be deleted automatically since now the relation has been converted into master-detail. Will this standard deletion throws some error since the records size is huge?







      lookup master-detail






      share|improve this question













      share|improve this question











      share|improve this question




      share|improve this question










      asked 16 hours ago









      Sindhuja

      192




      192




















          3 Answers
          3






          active

          oldest

          votes

















          up vote
          1
          down vote













          If you have already done conversion ,the child records will be auto deleted upon parent record deletion.Look for if you have any triggers on the deletion of parent record as that could impact deletion.



          Below are some of the considerations that one should consider before changing relationship from lookup to master detail



          1. Make sure that every child records has a parent assigned .If you have records with no parents assigned the conversion will fail

          2. All child records will have the ownerId as that of parent and the sharing settings will be inherited of the Parents .


          3. Make sure you don't have reports referencing the field.If you have then those have to recreated as they might throw error .

          In short it does not matter how many records you have ,the system automatically takes care of conversion , however be sure to review the implications listed above and first make these changes in sandbox and experiment before doing this change in PROD environment .






          share|improve this answer






















          • OP was asking about cascading deletion after conversion!
            – codeyinthecloud
            16 hours ago






          • 1




            Enhanced the answer to make it appropriate
            – Mohith Shrivastava
            16 hours ago

















          up vote
          1
          down vote













          Along with the points mentioned in other answers, find additional notes



          1. Verify if owner field has been used in any classes as detail record of MD relationship should not have owner field.


          2. For huge number of records, there could be possibility of halting or locking the sharing settings, when you change it. So, this needs to be performed outside of business hours.


          3. There could be change in custom report types.


          Also, for more information, refer Considerations for Relationships






          share|improve this answer



























            up vote
            1
            down vote













            You should be fine with standard deletes as long as your data doesn't qualify to be a data skew.




            Even when you talk about data skew you see the issues mainly around
            updates because of high chance of locking issues but not on deletes.




            As a best practice, don't exceed 10,000 child records for a master-detail relationship. Also read Considerations for Relationships






            share|improve this answer






















            • Data skew won't impact deletion capability .It's good practice to ensure data skew is not violated however for deletion it should not matter as the deletion happens under the hood .
              – Mohith Shrivastava
              16 hours ago






            • 1




              @MohithShrivastava True let me highlight that part.
              – codeyinthecloud
              16 hours ago










            Your Answer








            StackExchange.ready(function()
            var channelOptions =
            tags: "".split(" "),
            id: "459"
            ;
            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',
            convertImagesToLinks: false,
            noModals: true,
            showLowRepImageUploadWarning: true,
            reputationToPostImages: null,
            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%2fsalesforce.stackexchange.com%2fquestions%2f239053%2fconverting-lookup-relationship-into-master-detail-relationship%23new-answer', 'question_page');

            );

            Post as a guest






























            3 Answers
            3






            active

            oldest

            votes








            3 Answers
            3






            active

            oldest

            votes









            active

            oldest

            votes






            active

            oldest

            votes








            up vote
            1
            down vote













            If you have already done conversion ,the child records will be auto deleted upon parent record deletion.Look for if you have any triggers on the deletion of parent record as that could impact deletion.



            Below are some of the considerations that one should consider before changing relationship from lookup to master detail



            1. Make sure that every child records has a parent assigned .If you have records with no parents assigned the conversion will fail

            2. All child records will have the ownerId as that of parent and the sharing settings will be inherited of the Parents .


            3. Make sure you don't have reports referencing the field.If you have then those have to recreated as they might throw error .

            In short it does not matter how many records you have ,the system automatically takes care of conversion , however be sure to review the implications listed above and first make these changes in sandbox and experiment before doing this change in PROD environment .






            share|improve this answer






















            • OP was asking about cascading deletion after conversion!
              – codeyinthecloud
              16 hours ago






            • 1




              Enhanced the answer to make it appropriate
              – Mohith Shrivastava
              16 hours ago














            up vote
            1
            down vote













            If you have already done conversion ,the child records will be auto deleted upon parent record deletion.Look for if you have any triggers on the deletion of parent record as that could impact deletion.



            Below are some of the considerations that one should consider before changing relationship from lookup to master detail



            1. Make sure that every child records has a parent assigned .If you have records with no parents assigned the conversion will fail

            2. All child records will have the ownerId as that of parent and the sharing settings will be inherited of the Parents .


            3. Make sure you don't have reports referencing the field.If you have then those have to recreated as they might throw error .

            In short it does not matter how many records you have ,the system automatically takes care of conversion , however be sure to review the implications listed above and first make these changes in sandbox and experiment before doing this change in PROD environment .






            share|improve this answer






















            • OP was asking about cascading deletion after conversion!
              – codeyinthecloud
              16 hours ago






            • 1




              Enhanced the answer to make it appropriate
              – Mohith Shrivastava
              16 hours ago












            up vote
            1
            down vote










            up vote
            1
            down vote









            If you have already done conversion ,the child records will be auto deleted upon parent record deletion.Look for if you have any triggers on the deletion of parent record as that could impact deletion.



            Below are some of the considerations that one should consider before changing relationship from lookup to master detail



            1. Make sure that every child records has a parent assigned .If you have records with no parents assigned the conversion will fail

            2. All child records will have the ownerId as that of parent and the sharing settings will be inherited of the Parents .


            3. Make sure you don't have reports referencing the field.If you have then those have to recreated as they might throw error .

            In short it does not matter how many records you have ,the system automatically takes care of conversion , however be sure to review the implications listed above and first make these changes in sandbox and experiment before doing this change in PROD environment .






            share|improve this answer














            If you have already done conversion ,the child records will be auto deleted upon parent record deletion.Look for if you have any triggers on the deletion of parent record as that could impact deletion.



            Below are some of the considerations that one should consider before changing relationship from lookup to master detail



            1. Make sure that every child records has a parent assigned .If you have records with no parents assigned the conversion will fail

            2. All child records will have the ownerId as that of parent and the sharing settings will be inherited of the Parents .


            3. Make sure you don't have reports referencing the field.If you have then those have to recreated as they might throw error .

            In short it does not matter how many records you have ,the system automatically takes care of conversion , however be sure to review the implications listed above and first make these changes in sandbox and experiment before doing this change in PROD environment .







            share|improve this answer














            share|improve this answer



            share|improve this answer








            edited 16 hours ago

























            answered 16 hours ago









            Mohith Shrivastava

            58.7k794133




            58.7k794133











            • OP was asking about cascading deletion after conversion!
              – codeyinthecloud
              16 hours ago






            • 1




              Enhanced the answer to make it appropriate
              – Mohith Shrivastava
              16 hours ago
















            • OP was asking about cascading deletion after conversion!
              – codeyinthecloud
              16 hours ago






            • 1




              Enhanced the answer to make it appropriate
              – Mohith Shrivastava
              16 hours ago















            OP was asking about cascading deletion after conversion!
            – codeyinthecloud
            16 hours ago




            OP was asking about cascading deletion after conversion!
            – codeyinthecloud
            16 hours ago




            1




            1




            Enhanced the answer to make it appropriate
            – Mohith Shrivastava
            16 hours ago




            Enhanced the answer to make it appropriate
            – Mohith Shrivastava
            16 hours ago












            up vote
            1
            down vote













            Along with the points mentioned in other answers, find additional notes



            1. Verify if owner field has been used in any classes as detail record of MD relationship should not have owner field.


            2. For huge number of records, there could be possibility of halting or locking the sharing settings, when you change it. So, this needs to be performed outside of business hours.


            3. There could be change in custom report types.


            Also, for more information, refer Considerations for Relationships






            share|improve this answer
























              up vote
              1
              down vote













              Along with the points mentioned in other answers, find additional notes



              1. Verify if owner field has been used in any classes as detail record of MD relationship should not have owner field.


              2. For huge number of records, there could be possibility of halting or locking the sharing settings, when you change it. So, this needs to be performed outside of business hours.


              3. There could be change in custom report types.


              Also, for more information, refer Considerations for Relationships






              share|improve this answer






















                up vote
                1
                down vote










                up vote
                1
                down vote









                Along with the points mentioned in other answers, find additional notes



                1. Verify if owner field has been used in any classes as detail record of MD relationship should not have owner field.


                2. For huge number of records, there could be possibility of halting or locking the sharing settings, when you change it. So, this needs to be performed outside of business hours.


                3. There could be change in custom report types.


                Also, for more information, refer Considerations for Relationships






                share|improve this answer












                Along with the points mentioned in other answers, find additional notes



                1. Verify if owner field has been used in any classes as detail record of MD relationship should not have owner field.


                2. For huge number of records, there could be possibility of halting or locking the sharing settings, when you change it. So, this needs to be performed outside of business hours.


                3. There could be change in custom report types.


                Also, for more information, refer Considerations for Relationships







                share|improve this answer












                share|improve this answer



                share|improve this answer










                answered 16 hours ago









                Santanu Boral

                29.4k52150




                29.4k52150




















                    up vote
                    1
                    down vote













                    You should be fine with standard deletes as long as your data doesn't qualify to be a data skew.




                    Even when you talk about data skew you see the issues mainly around
                    updates because of high chance of locking issues but not on deletes.




                    As a best practice, don't exceed 10,000 child records for a master-detail relationship. Also read Considerations for Relationships






                    share|improve this answer






















                    • Data skew won't impact deletion capability .It's good practice to ensure data skew is not violated however for deletion it should not matter as the deletion happens under the hood .
                      – Mohith Shrivastava
                      16 hours ago






                    • 1




                      @MohithShrivastava True let me highlight that part.
                      – codeyinthecloud
                      16 hours ago














                    up vote
                    1
                    down vote













                    You should be fine with standard deletes as long as your data doesn't qualify to be a data skew.




                    Even when you talk about data skew you see the issues mainly around
                    updates because of high chance of locking issues but not on deletes.




                    As a best practice, don't exceed 10,000 child records for a master-detail relationship. Also read Considerations for Relationships






                    share|improve this answer






















                    • Data skew won't impact deletion capability .It's good practice to ensure data skew is not violated however for deletion it should not matter as the deletion happens under the hood .
                      – Mohith Shrivastava
                      16 hours ago






                    • 1




                      @MohithShrivastava True let me highlight that part.
                      – codeyinthecloud
                      16 hours ago












                    up vote
                    1
                    down vote










                    up vote
                    1
                    down vote









                    You should be fine with standard deletes as long as your data doesn't qualify to be a data skew.




                    Even when you talk about data skew you see the issues mainly around
                    updates because of high chance of locking issues but not on deletes.




                    As a best practice, don't exceed 10,000 child records for a master-detail relationship. Also read Considerations for Relationships






                    share|improve this answer














                    You should be fine with standard deletes as long as your data doesn't qualify to be a data skew.




                    Even when you talk about data skew you see the issues mainly around
                    updates because of high chance of locking issues but not on deletes.




                    As a best practice, don't exceed 10,000 child records for a master-detail relationship. Also read Considerations for Relationships







                    share|improve this answer














                    share|improve this answer



                    share|improve this answer








                    edited 16 hours ago

























                    answered 16 hours ago









                    codeyinthecloud

                    2,167219




                    2,167219











                    • Data skew won't impact deletion capability .It's good practice to ensure data skew is not violated however for deletion it should not matter as the deletion happens under the hood .
                      – Mohith Shrivastava
                      16 hours ago






                    • 1




                      @MohithShrivastava True let me highlight that part.
                      – codeyinthecloud
                      16 hours ago
















                    • Data skew won't impact deletion capability .It's good practice to ensure data skew is not violated however for deletion it should not matter as the deletion happens under the hood .
                      – Mohith Shrivastava
                      16 hours ago






                    • 1




                      @MohithShrivastava True let me highlight that part.
                      – codeyinthecloud
                      16 hours ago















                    Data skew won't impact deletion capability .It's good practice to ensure data skew is not violated however for deletion it should not matter as the deletion happens under the hood .
                    – Mohith Shrivastava
                    16 hours ago




                    Data skew won't impact deletion capability .It's good practice to ensure data skew is not violated however for deletion it should not matter as the deletion happens under the hood .
                    – Mohith Shrivastava
                    16 hours ago




                    1




                    1




                    @MohithShrivastava True let me highlight that part.
                    – codeyinthecloud
                    16 hours ago




                    @MohithShrivastava True let me highlight that part.
                    – codeyinthecloud
                    16 hours ago

















                     

                    draft saved


                    draft discarded















































                     


                    draft saved


                    draft discarded














                    StackExchange.ready(
                    function ()
                    StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsalesforce.stackexchange.com%2fquestions%2f239053%2fconverting-lookup-relationship-into-master-detail-relationship%23new-answer', 'question_page');

                    );

                    Post as a guest













































































                    Popular posts from this blog

                    How to check contact read email or not when send email to Individual?

                    Displaying single band from multi-band raster using QGIS

                    How many registers does an x86_64 CPU actually have?