TDS update packages don't remove unneeded items Planned maintenance scheduled April 17/18, 2019 at 00:00UTC (8:00pm US/Eastern) Announcing the arrival of Valued Associate #679: Cesar Manara Unicorn Meta Zoo #1: Why another podcast?Habitat TDS Version - Sync Items to SitecoreDoes TDS know to delete items with delta packages?Given TDS delta packages do not track deletions how could this be achieved?TDS sync always shows Items are different even after updataingCustom TDS Delta PackagesTDS GetFilesToTransformTDS remote deploymentIs it possible to remove publishing targets using TDS?Status of items added to TDS projectsUsing TDS can I make a single update package?

3 doors, three guards, one stone

Should I discuss the type of campaign with my players?

What exactly is a "Meth" in Altered Carbon?

How to tell that you are a giant?

Can inflation occur in a positive-sum game currency system such as the Stack Exchange reputation system?

The logistics of corpse disposal

What's the meaning of 間時肆拾貳 at a car parking sign

What does the "x" in "x86" represent?

Ring Automorphisms that fix 1.

Output the ŋarâþ crîþ alphabet song without using (m)any letters

Is it true that "carbohydrates are of no use for the basal metabolic need"?

How to override model in magento2?

English words in a non-english sci-fi novel

What does F' and F" mean?

Why do people hide their license plates in the EU?

Why am I getting the error "non-boolean type specified in a context where a condition is expected" for this request?

Generate an RGB colour grid

How to bypass password on Windows XP account?

How do I keep my slimes from escaping their pens?

How to react to hostile behavior from a senior developer?

2001: A Space Odyssey's use of the song "Daisy Bell" (Bicycle Built for Two); life imitates art or vice-versa?

What does an IRS interview request entail when called in to verify expenses for a sole proprietor small business?

First console to have temporary backward compatibility

How to find out what spells would be useless to a blind NPC spellcaster?



TDS update packages don't remove unneeded items



Planned maintenance scheduled April 17/18, 2019 at 00:00UTC (8:00pm US/Eastern)
Announcing the arrival of Valued Associate #679: Cesar Manara
Unicorn Meta Zoo #1: Why another podcast?Habitat TDS Version - Sync Items to SitecoreDoes TDS know to delete items with delta packages?Given TDS delta packages do not track deletions how could this be achieved?TDS sync always shows Items are different even after updataingCustom TDS Delta PackagesTDS GetFilesToTransformTDS remote deploymentIs it possible to remove publishing targets using TDS?Status of items added to TDS projectsUsing TDS can I make a single update package?










2















For some reason, when I create new update packages (release build in VS), the update packages are not removing old items. Where I've noticed this specifically is with templates.



Example:
Before updates:

Email Form (template) has an "Email Validation" group containing a field called "Banned Domains" which is a csv list of email domains to not accept submissions from and some other fields.



I decided to move this field to a central setting so that you didn't have to config/update each form separately so...
After updates:

Email Form (template) has an "Email Validation" group containing everything but that list of "Banned Domains".



After building using the release config, I take the resulting update package and apply it, but it doesn't remove the "Banned Domains" field from the template on the applied server as I expected. I have to manually remove it.



What might I be doing wrong? Is there a config for TDS I need to tweak?
I'm a newbie with TDS. I inherited it from the company that setup our enviro, so please forgive me if this is a "stupid" question.










share|improve this question


























    2















    For some reason, when I create new update packages (release build in VS), the update packages are not removing old items. Where I've noticed this specifically is with templates.



    Example:
    Before updates:

    Email Form (template) has an "Email Validation" group containing a field called "Banned Domains" which is a csv list of email domains to not accept submissions from and some other fields.



    I decided to move this field to a central setting so that you didn't have to config/update each form separately so...
    After updates:

    Email Form (template) has an "Email Validation" group containing everything but that list of "Banned Domains".



    After building using the release config, I take the resulting update package and apply it, but it doesn't remove the "Banned Domains" field from the template on the applied server as I expected. I have to manually remove it.



    What might I be doing wrong? Is there a config for TDS I need to tweak?
    I'm a newbie with TDS. I inherited it from the company that setup our enviro, so please forgive me if this is a "stupid" question.










    share|improve this question
























      2












      2








      2








      For some reason, when I create new update packages (release build in VS), the update packages are not removing old items. Where I've noticed this specifically is with templates.



      Example:
      Before updates:

      Email Form (template) has an "Email Validation" group containing a field called "Banned Domains" which is a csv list of email domains to not accept submissions from and some other fields.



      I decided to move this field to a central setting so that you didn't have to config/update each form separately so...
      After updates:

      Email Form (template) has an "Email Validation" group containing everything but that list of "Banned Domains".



      After building using the release config, I take the resulting update package and apply it, but it doesn't remove the "Banned Domains" field from the template on the applied server as I expected. I have to manually remove it.



      What might I be doing wrong? Is there a config for TDS I need to tweak?
      I'm a newbie with TDS. I inherited it from the company that setup our enviro, so please forgive me if this is a "stupid" question.










      share|improve this question














      For some reason, when I create new update packages (release build in VS), the update packages are not removing old items. Where I've noticed this specifically is with templates.



      Example:
      Before updates:

      Email Form (template) has an "Email Validation" group containing a field called "Banned Domains" which is a csv list of email domains to not accept submissions from and some other fields.



      I decided to move this field to a central setting so that you didn't have to config/update each form separately so...
      After updates:

      Email Form (template) has an "Email Validation" group containing everything but that list of "Banned Domains".



      After building using the release config, I take the resulting update package and apply it, but it doesn't remove the "Banned Domains" field from the template on the applied server as I expected. I have to manually remove it.



      What might I be doing wrong? Is there a config for TDS I need to tweak?
      I'm a newbie with TDS. I inherited it from the company that setup our enviro, so please forgive me if this is a "stupid" question.







      tds






      share|improve this question













      share|improve this question











      share|improve this question




      share|improve this question










      asked Apr 12 at 16:09









      MichaelMichael

      877




      877




















          3 Answers
          3






          active

          oldest

          votes


















          3














          Update packages do not remove items. Only updates and inserts are performed. If you want to remove items you will need to create a post installation step that would do the work.



          You can learn more about post installation steps here.
          https://www.teamdevelopmentforsitecore.com/Blog/creating-tds-custom-post-deploy-step






          share|improve this answer























          • If a parent item is set to KeepAllChildrenSynchronized then deletes are performed after installation. If a template or field is failing to delete it’s likely because there is a linked item.

            – jrap
            2 days ago











          • There are several baked-in post deploy actions that are not well documented- one of which is to perform this style of deletes. The connector method and update package are supposed to have feature parity and I know a simple action like a delete is included in that parity. What’s more important is the version of TDS being used and the method used for installation, neither of which was explained.

            – jrap
            2 days ago


















          0














          We have seen this specific issue crop up, but only in the templates section. There is some limitation related to the templates area specifically where Sitecore does not respect the KeepAllChildrenSynchronized setting when applying changes.



          To resolve this for templates, we had to add a step to our deployment process where we deleted all of our (custom) templates before installing the .update package. The only way we could do this (with so many items using those templates) was using dbbrowser.aspx:



          DB Browser photo






          share|improve this answer






























            0














            TDS Update Packages do perform deletes. Update packages have feature parity with the connector method (i.e. when you sync from Visual Studio)... anything you can do from Visual Studio is possible with Update Packages.



            If a parent item is set to KeepAllChildrenSynchronized, then in Visual Studio you would see a changed/deleted/added item beneath said parent. The same is true for update packages. Therefore, if you remove an item and then create an update package it will attempt to delete it.



            The Caveat



            As @Dan Sinclair mentioned, this doesn't always work with templates. Just like with Content Editor, you cannot delete a template that has existing items using that template. The same is true for update package installations. You would first need to delete any items associated with that template, then the update package would perform the deletion of the template (again, assuming the parent is set to KeepAllChildrenSynchronized).






            share|improve this answer























              Your Answer








              StackExchange.ready(function()
              var channelOptions =
              tags: "".split(" "),
              id: "664"
              ;
              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: 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%2fsitecore.stackexchange.com%2fquestions%2f18087%2ftds-update-packages-dont-remove-unneeded-items%23new-answer', 'question_page');

              );

              Post as a guest















              Required, but never shown

























              3 Answers
              3






              active

              oldest

              votes








              3 Answers
              3






              active

              oldest

              votes









              active

              oldest

              votes






              active

              oldest

              votes









              3














              Update packages do not remove items. Only updates and inserts are performed. If you want to remove items you will need to create a post installation step that would do the work.



              You can learn more about post installation steps here.
              https://www.teamdevelopmentforsitecore.com/Blog/creating-tds-custom-post-deploy-step






              share|improve this answer























              • If a parent item is set to KeepAllChildrenSynchronized then deletes are performed after installation. If a template or field is failing to delete it’s likely because there is a linked item.

                – jrap
                2 days ago











              • There are several baked-in post deploy actions that are not well documented- one of which is to perform this style of deletes. The connector method and update package are supposed to have feature parity and I know a simple action like a delete is included in that parity. What’s more important is the version of TDS being used and the method used for installation, neither of which was explained.

                – jrap
                2 days ago















              3














              Update packages do not remove items. Only updates and inserts are performed. If you want to remove items you will need to create a post installation step that would do the work.



              You can learn more about post installation steps here.
              https://www.teamdevelopmentforsitecore.com/Blog/creating-tds-custom-post-deploy-step






              share|improve this answer























              • If a parent item is set to KeepAllChildrenSynchronized then deletes are performed after installation. If a template or field is failing to delete it’s likely because there is a linked item.

                – jrap
                2 days ago











              • There are several baked-in post deploy actions that are not well documented- one of which is to perform this style of deletes. The connector method and update package are supposed to have feature parity and I know a simple action like a delete is included in that parity. What’s more important is the version of TDS being used and the method used for installation, neither of which was explained.

                – jrap
                2 days ago













              3












              3








              3







              Update packages do not remove items. Only updates and inserts are performed. If you want to remove items you will need to create a post installation step that would do the work.



              You can learn more about post installation steps here.
              https://www.teamdevelopmentforsitecore.com/Blog/creating-tds-custom-post-deploy-step






              share|improve this answer













              Update packages do not remove items. Only updates and inserts are performed. If you want to remove items you will need to create a post installation step that would do the work.



              You can learn more about post installation steps here.
              https://www.teamdevelopmentforsitecore.com/Blog/creating-tds-custom-post-deploy-step







              share|improve this answer












              share|improve this answer



              share|improve this answer










              answered Apr 12 at 16:26









              Chris AuerChris Auer

              8,76911146




              8,76911146












              • If a parent item is set to KeepAllChildrenSynchronized then deletes are performed after installation. If a template or field is failing to delete it’s likely because there is a linked item.

                – jrap
                2 days ago











              • There are several baked-in post deploy actions that are not well documented- one of which is to perform this style of deletes. The connector method and update package are supposed to have feature parity and I know a simple action like a delete is included in that parity. What’s more important is the version of TDS being used and the method used for installation, neither of which was explained.

                – jrap
                2 days ago

















              • If a parent item is set to KeepAllChildrenSynchronized then deletes are performed after installation. If a template or field is failing to delete it’s likely because there is a linked item.

                – jrap
                2 days ago











              • There are several baked-in post deploy actions that are not well documented- one of which is to perform this style of deletes. The connector method and update package are supposed to have feature parity and I know a simple action like a delete is included in that parity. What’s more important is the version of TDS being used and the method used for installation, neither of which was explained.

                – jrap
                2 days ago
















              If a parent item is set to KeepAllChildrenSynchronized then deletes are performed after installation. If a template or field is failing to delete it’s likely because there is a linked item.

              – jrap
              2 days ago





              If a parent item is set to KeepAllChildrenSynchronized then deletes are performed after installation. If a template or field is failing to delete it’s likely because there is a linked item.

              – jrap
              2 days ago













              There are several baked-in post deploy actions that are not well documented- one of which is to perform this style of deletes. The connector method and update package are supposed to have feature parity and I know a simple action like a delete is included in that parity. What’s more important is the version of TDS being used and the method used for installation, neither of which was explained.

              – jrap
              2 days ago





              There are several baked-in post deploy actions that are not well documented- one of which is to perform this style of deletes. The connector method and update package are supposed to have feature parity and I know a simple action like a delete is included in that parity. What’s more important is the version of TDS being used and the method used for installation, neither of which was explained.

              – jrap
              2 days ago











              0














              We have seen this specific issue crop up, but only in the templates section. There is some limitation related to the templates area specifically where Sitecore does not respect the KeepAllChildrenSynchronized setting when applying changes.



              To resolve this for templates, we had to add a step to our deployment process where we deleted all of our (custom) templates before installing the .update package. The only way we could do this (with so many items using those templates) was using dbbrowser.aspx:



              DB Browser photo






              share|improve this answer



























                0














                We have seen this specific issue crop up, but only in the templates section. There is some limitation related to the templates area specifically where Sitecore does not respect the KeepAllChildrenSynchronized setting when applying changes.



                To resolve this for templates, we had to add a step to our deployment process where we deleted all of our (custom) templates before installing the .update package. The only way we could do this (with so many items using those templates) was using dbbrowser.aspx:



                DB Browser photo






                share|improve this answer

























                  0












                  0








                  0







                  We have seen this specific issue crop up, but only in the templates section. There is some limitation related to the templates area specifically where Sitecore does not respect the KeepAllChildrenSynchronized setting when applying changes.



                  To resolve this for templates, we had to add a step to our deployment process where we deleted all of our (custom) templates before installing the .update package. The only way we could do this (with so many items using those templates) was using dbbrowser.aspx:



                  DB Browser photo






                  share|improve this answer













                  We have seen this specific issue crop up, but only in the templates section. There is some limitation related to the templates area specifically where Sitecore does not respect the KeepAllChildrenSynchronized setting when applying changes.



                  To resolve this for templates, we had to add a step to our deployment process where we deleted all of our (custom) templates before installing the .update package. The only way we could do this (with so many items using those templates) was using dbbrowser.aspx:



                  DB Browser photo







                  share|improve this answer












                  share|improve this answer



                  share|improve this answer










                  answered Apr 12 at 17:52









                  Dan SinclairDan Sinclair

                  2,3591727




                  2,3591727





















                      0














                      TDS Update Packages do perform deletes. Update packages have feature parity with the connector method (i.e. when you sync from Visual Studio)... anything you can do from Visual Studio is possible with Update Packages.



                      If a parent item is set to KeepAllChildrenSynchronized, then in Visual Studio you would see a changed/deleted/added item beneath said parent. The same is true for update packages. Therefore, if you remove an item and then create an update package it will attempt to delete it.



                      The Caveat



                      As @Dan Sinclair mentioned, this doesn't always work with templates. Just like with Content Editor, you cannot delete a template that has existing items using that template. The same is true for update package installations. You would first need to delete any items associated with that template, then the update package would perform the deletion of the template (again, assuming the parent is set to KeepAllChildrenSynchronized).






                      share|improve this answer



























                        0














                        TDS Update Packages do perform deletes. Update packages have feature parity with the connector method (i.e. when you sync from Visual Studio)... anything you can do from Visual Studio is possible with Update Packages.



                        If a parent item is set to KeepAllChildrenSynchronized, then in Visual Studio you would see a changed/deleted/added item beneath said parent. The same is true for update packages. Therefore, if you remove an item and then create an update package it will attempt to delete it.



                        The Caveat



                        As @Dan Sinclair mentioned, this doesn't always work with templates. Just like with Content Editor, you cannot delete a template that has existing items using that template. The same is true for update package installations. You would first need to delete any items associated with that template, then the update package would perform the deletion of the template (again, assuming the parent is set to KeepAllChildrenSynchronized).






                        share|improve this answer

























                          0












                          0








                          0







                          TDS Update Packages do perform deletes. Update packages have feature parity with the connector method (i.e. when you sync from Visual Studio)... anything you can do from Visual Studio is possible with Update Packages.



                          If a parent item is set to KeepAllChildrenSynchronized, then in Visual Studio you would see a changed/deleted/added item beneath said parent. The same is true for update packages. Therefore, if you remove an item and then create an update package it will attempt to delete it.



                          The Caveat



                          As @Dan Sinclair mentioned, this doesn't always work with templates. Just like with Content Editor, you cannot delete a template that has existing items using that template. The same is true for update package installations. You would first need to delete any items associated with that template, then the update package would perform the deletion of the template (again, assuming the parent is set to KeepAllChildrenSynchronized).






                          share|improve this answer













                          TDS Update Packages do perform deletes. Update packages have feature parity with the connector method (i.e. when you sync from Visual Studio)... anything you can do from Visual Studio is possible with Update Packages.



                          If a parent item is set to KeepAllChildrenSynchronized, then in Visual Studio you would see a changed/deleted/added item beneath said parent. The same is true for update packages. Therefore, if you remove an item and then create an update package it will attempt to delete it.



                          The Caveat



                          As @Dan Sinclair mentioned, this doesn't always work with templates. Just like with Content Editor, you cannot delete a template that has existing items using that template. The same is true for update package installations. You would first need to delete any items associated with that template, then the update package would perform the deletion of the template (again, assuming the parent is set to KeepAllChildrenSynchronized).







                          share|improve this answer












                          share|improve this answer



                          share|improve this answer










                          answered 18 hours ago









                          jrapjrap

                          2,6621630




                          2,6621630



























                              draft saved

                              draft discarded
















































                              Thanks for contributing an answer to Sitecore Stack Exchange!


                              • 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%2fsitecore.stackexchange.com%2fquestions%2f18087%2ftds-update-packages-dont-remove-unneeded-items%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







                              Popular posts from this blog

                              Sum ergo cogito? 1 nng

                              三茅街道4182Guuntc Dn precexpngmageondP