Complete to Ignore Update Sets in PROD

[dormarchan]

Hi Experts and Gurus,

When we apply Update Sets in PROD, I believe that the XMLs overwrites those old ones. In this respect, As an analogy, I view the update set as a basket of goodies. Since they are applied, I think I don't need the update set anymore. It is like keeping aside the basket after I empty it. I am inclining to set them to Ignore state.

What is my concern? Well, at our DEV instance, those update sets (still in Complete) are still selectable for merging. Now, we have hundreds and it just simply time consuming.

So, can we set the update sets to Ignore at PROD after they are applied?

Thank you for your feedback.

Salvador

[Chuck Tomasi · Accepted solution]

Hi Salvador,

Yes, that's a great idea to set your prod update sets to Ignore as a matter of your process. Now when clone back to Dev, they aren't in your way for future updates.

Let me know if I can answer any other update set questions.

[Chuck Tomasi]

Let me know if that answered your question. If so, please mark it as correct so that others with the same question in the future can find it quickly and that it gets removed from the Unanswered list.

If you are viewing this discussion from your "inbox", use the "mark as correct" option under actions. If you are viewing it directly from the thread use the Correct Answer link (red with a star).

Thank you

[Laurie Marlowe1]

Hey Chuck,

We have an issue with update sets since we moved to Fuji (or maybe we just discovered it at that time).   We always set our updates sets in production to ignore after committing.   What is happening is update sets set to ignore do not prevent the completed update set from a lower environment from being loaded again.  

For example:

1. Set completed update sets in production to ignore.
2. Clone production to test.
3. Retrieve update sets from dev to test.
4. Update sets come from dev to test as loaded.   These update sets were committed in production, so it is not the difference between what was in test, but not yet in production.

What we have been doing is comparing the update sets that are being loaded into test, with the ones that show ignore in test.   THEN we have to go set the ones that should not have loaded into test, to ignore in dev.

This seems a little weird.   Could it be that with Fuji, setting update sets in prod to ignore would be causing this issue?   Maybe the update sets coming in from dev to test aren't "smart" enough to "see" the ignored ones already in test????

Thanks,

Laurie

[Chuck Tomasi]

Hi Laurie,

Interesting use case. It seems that Ignore in test should not retrieve the completed ones from dev. That's a bit odd. While I don't have an answer for you, it sure makes me want to add another bullet list to 'reasons for using scoped apps.'