Purging old WTPart iterations

[avillanueva]

Currently in 9.1 and previous versions, there was a restriction on
purging iterations if it was the iteration from which a new view version
was created. This presents a problem when you have to fix things and
want to remove a component from the system. You would have to delete
the new view version, purge then recreate the new view version. Has
this been changed in 10.0? I am sure development would state there is
an integrity reason for this block but I cannot see the use case. Say
you have a BOM and CAD assembly and you make a new view version at some
point. Then before release you decide to remove a component from the
assembly and you so the same to the new view version. If you later want
to delete that component, since its no longer used in any current
iteration, you have to do a purge of the WTPart history. OK but it does
a partial purge since the iteration that created the new view version
cannot be removed. Therefore, the component you want to remove is
blocked from deletion. I am wondering if this is still that case and if
it possible to pursue a workaround with PTC.

[avillanueva]

Resurrecting this old post I did back in 9.1 days. Looks like same issue exists in 11.1. In my current case, I have a bad Part that a user did a save as on and I want to remove. It was called by a released assembly but by older iterations. The problem is we use View Versions and the iteration exists after the branch was made to the view version.  There are 150+ iterations I cannot purge because of this and therefore, I cannot delete this part. It past conversations with PTC they indicated fixing this would mess up BOM integrity but I cannot see how. I know of others who figured out a DB hack to clear this but not willing to do that. Perhaps I will repost to enhancement requests. 

Summary: Ability to purge older iterations of Parts held only due to branch dependency. Suggestion, alter branch point to latest iteration of the version that was branched off of. 

[MichaelChatel]

It does look like the same limitation exists, and it seems specific (like you mentioned), to the branch point iteration (and affecting iterations after that).

https://www.ptc.com/en/support/article/CS18659

There is this product idea I was able to find:

https://community.ptc.com/t5/Windchill-Ideas/Admin-Ability-to-Break-EPMBuildHistory-Links/idi-p/464246

Which is specific to your need, I believe.  It seems like, the WCTK healer that is mentioned in that product idea thread, can be utilized to accomplish what you want.

I would suggest opening up a Support case, to get a fresh look at your requirement, but it seems like others have utilized this:

https://www.ptc.com/en/support/article/CS211311

Again, I would suggest consulting with Support about this first.

Mike