Selective delete in windchill 10

Welcome to the wonderful world of Windchill.

As you have discoverred, you can only delete the latest version, or all iterations of the latest revision.

Gerry Champoux
Williams International
Walled Lake, MI

In Reply to Ron Rich:

Ok so this was possible in ILINK3.4 how do you do it in WC10. See picture below. I would like to delete 8010-120_mfg.asm version A.1 from the data base. Unfortunately I cannot I can delete A.4 through A.1. Purge is not the answer. I do not want to delete from A.1 through A.3 and leave only A.4 I would like to selectively delete these items from the database.

Has anyone ever received this toolkit deletion patch for Windchill 9.1, and willing to share it?
I've requested it from PTC, but they are stonewalling me.

Gerry Champoux
Williams International
Walled Lake, MI


In Reply to Joe Kent:

Only way I know of doing this is using the wctk DeleteObjects. You can specify a specific Revision and Iteration in a csv file and run the tool.

Here is the patch.
10.0-M0X0_WCTK_2.0 Windchill Toolkit [Seq 05]

[cid:image002.png@01CDBC1E.C95DC960]

Joe Kent
Engineering Systems Administrator
R&D/Leverage(tm)
Structural Brand Development / Mold Manufacturing
"With Us, Ideas Take Shape"

Tel: 816-525-0353 x6527

www.rdleverage.com<
Innovations in packaging design!
Innovations in mold manufacturing!
Learn more here www.rdleverage.com<

Can't argue with that.

But what about deleting unreleased objects?
Windchill still does not allow such.

Simple example:
User inadvertantly rolls the revision of a model to the next letter.
Weeks go by before anyone notices.
By this time, many iterations have been checked-in, but nothing released.
Once notified, I (the admin) try to delete them. Normally, I should be able to do so. (all iterations of latest rev)
However, the model is now in use any many assemblies.
Windchill won't allow me to delete the revision of the model (a part) because it is in use.
Some would say that if I were allowed to delete the model, those assemblies will fail to regenerate.
Yes! That's exactly what I want to have happen, so that the designers will know they need to fix their assemblies with the same model at correct revision.

In short: Deleting stuff like this should be allowed for the admin.

Gerry Champoux
Williams International
Walled Lake, MI

In Reply to alfonso medina:

Intralink 3.4 is a pretend PDM. we pretend we release something then we go
back and delete it and replace it with something better.

windchill is a real PDM. You release something and that's it, there is no
going back to cleanup the trail... especially if you waited several months
to discover something. so what do you do if you need to delete rev A and
rev B is already released? just roll back every single linked item to all
A.X revisions and then delete one at a time as required, then redo all the
work. Or go to C with rev A.4 as the start point then go to rev D with rev
B as the start point. Hey if A is already in someone's hand as paper,
forget about deleting it from your db.