Question
Can't delete the latest version of a family table when one instance has only one version.
As many of you may already know, in Windchill it is not possible to delete the latest version of a family table if any one of the instances in that family table has only one version - the reason being that you are deleting ALL versions of that instance. (see example below)
This is an "old" issue with family tables, but I issued a call on it recently just to see if there were any improved workarounds. Suffice it to say, there are not. (CS21661 is not a very good workaround at all.) And I was not pleased to hear from TS that even though they see this issue from customers and have raised it will R&D, it is generally dismissed for some unknown reason.
Do others have issues with this? This would seem to be a simple exception to allow in cases where the A.0 object is not related to any object other than the most recent family table version.
Just wondering,
John Frankovich
Consider the following example:
You have a family table object X [A.4] with instance X1 [A.3]. A user incorrectly adds instance Y1 to the family and checks it in, yielding X [A.5], X1 [A.4], and Y1 [A.0].
Deleting the latest version of X [A.5] would delete the latest version of X1 [A.4], but would require WC to delete ALL versions of Y1, which it will not do unless you select 'delete all versions'. But selecting that will obviously delete all versions of X and X1 as well!
This is an "old" issue with family tables, but I issued a call on it recently just to see if there were any improved workarounds. Suffice it to say, there are not. (CS21661 is not a very good workaround at all.) And I was not pleased to hear from TS that even though they see this issue from customers and have raised it will R&D, it is generally dismissed for some unknown reason.
Do others have issues with this? This would seem to be a simple exception to allow in cases where the A.0 object is not related to any object other than the most recent family table version.
Just wondering,
John Frankovich
Consider the following example:
You have a family table object X [A.4] with instance X1 [A.3]. A user incorrectly adds instance Y1 to the family and checks it in, yielding X [A.5], X1 [A.4], and Y1 [A.0].
Deleting the latest version of X [A.5] would delete the latest version of X1 [A.4], but would require WC to delete ALL versions of Y1, which it will not do unless you select 'delete all versions'. But selecting that will obviously delete all versions of X and X1 as well!