TDS update packages don't remove unneeded items
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
add a comment |
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
add a comment |
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
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
tds
asked 13 hours ago
MichaelMichael
877
877
add a comment |
add a comment |
2 Answers
2
active
oldest
votes
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
add a comment |
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
:
add a comment |
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
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
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
2 Answers
2
active
oldest
votes
2 Answers
2
active
oldest
votes
active
oldest
votes
active
oldest
votes
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
add a comment |
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
add a comment |
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
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
answered 12 hours ago
Chris AuerChris Auer
8,72911146
8,72911146
add a comment |
add a comment |
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
:
add a comment |
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
:
add a comment |
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
:
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
:
answered 11 hours ago
Dan SinclairDan Sinclair
2,324727
2,324727
add a comment |
add a comment |
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.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
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
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
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