Create an overrideable conflict when deleting latest iteration, if it is the only iteration.

[jwagh]

We accidentally updated one of our screw generics and created 2 new screws in a newer version of Creo than production. All users were failing when opening their assemblies. We did a work-around, but it would have been easier to just select the generic and the 2 instances and delete while using the option "Delete latest iterations of each object included in the table". However, the event manager throws up an error and says that it can't do that because the instances have only one iteration. It would be great it there was an overrideable method to tell the system to do it anyway (just as it does it an item is in someone's workspace). 

[pkepinski]

In addition to this, Windchill also allows users to delete an instance even if it is being used in assemblies. This will cause users with those assemblies to constantly have out of date generics in their workspace and the server will not let them update out of date because latest is missing the required instance. There is a lot of error checking Windchill is missing related to generics/instances.

[lhoogeveen]

This would be a great improvement for allowing much easier removal of instances that were added over time.

The workaround is a pain. Windchill seems to have 2 delete actions: one that opens a delete menu (when deleting from the object info page/tabs) and one that deletes the revision of the selected objects (when deleting objects in a list - search results, folder view, etc.). The 2nd one is the only way I've found to remove instances added at a later date but it's tedious to collect all instances beforehand on large family tables.

PTC could also improve the verbiage and include some examples in the delete menu. I made this cheat sheet for myself:

[LawrenceS]

I see the PTC Support article saying this is currently intended functionality, but I really cannot get past the FACT that "Delete latest iterations of each object included in the table" cannot actually do what it is saying.  It cannot delete the latest iteration if it is the only revision remaining.  If I said delete the last bullet point, would you tell me that you cannot do it because there is only one bullet point?  WC clearly is not doing what it is saying it can do, and besides that, this is functionality that we need!

• Article - CS43073 - Unable to delete latest iteration of Family Table object in Windchill PDMLink (ptc.com)

[BenLoosli]

Why can't you use 'Delete all iterations of each object included in the table' to get rid of that last version when it is the only one left. I have done this when a user revised a part by accident. Selected version C.1 and used the first option and it deleted that version. 

Not sure of it works the same with family tables as there are many 'objects' to be included for a deletion.

[LawrenceS]

It is hard to explain but basically one of the FT objects is new and only exists at Ver.5.1 (no previous versions.  While the existing FT object went from 4.2 to 4.3.  Someone might say, well that is stupid why didn't you just revise the exiting object before changing it? Great question, I am glad you asked! 🙂

• Model revisions must match family drawing revisions so we demoted the exiting 4.2 (RFP --> In Work) so they could add it to the FT.
• We don't revise the models nor the individually controlled part revisions shown on the drawings in order for them to match so as not to increase purchasing/mfg costs (revising often forces requotes outside of our company, even if no engineering changes)
• In the end there are no engineering changes and this is a background change so it really shouldn't be revised, especially with the above realities.

Now the problem is that after several months of going back and forth with changes, the Change Notice got canceled and we need to return all the objects to how they were as if it never happened!

So if we delete all iterations it will actually delete what was already released on an existing Change Notice and has been used to make parts.  This is obviously unacceptable.

On our TEST server, I just tried deleting the iterations from the folder in WC, and it succeeded but deleted all iterations without explicitly prompting it would do that ...so we cannot do this in our production environment!

(WC said "Are you sure you want to delete the selected 2 object(s)?"...but it deleted the entire revision!  Glad this was on test!)

[LawrenceS]

Correction, see below...I am going to ask the moderator to correct this...

• We don't revise the drawing revisions in order to not rev the part and increase purchasing/mfg costs (revising often forces requotes outside of our company, even if no engineering changes).
• We don't revise the models nor the individually controlled part revisions shown on the drawings in order for them to match so as not to increase purchasing/mfg costs (revising often forces requotes outside of our company, even if no engineering changes).

If anything changes on the drawing we always revise the drawing...Since these family drawings have more than one part/model represented on them in table format we carefully control the revisions.