Removing old iteration in WC?

[ocorten-2]

Simple question with hopefully a simple (positive) answer:



How does one delete an old iteration of an object in Intralink 9.1?



I've got the following

test.drw B.0

test.drw A.1

test.drw A.0



Now I want to delete iteration A.0. Only A.0. (don't ask me why, it just
needs to go)

How does one do that?







Olaf Corten

CAD/PLM Manager, Besi Competence Center - Other Business Applications

Fico BV, Ratio 6, 6921 RW Duiven, The Netherlands

Tel.: +31 26 3196215

Fax: +31 26 3196200

Mobile: +31 644548554

www.fico.nl

[SteveVinyard]

See if Site>Utilities>Purge Manager will do what you are looking for.

Try going through the help page there (the "?" icon on the page) to help with the little details.

Steve Vinyard
Application Engineer

[cid:image003.gif@01CAFB1B.F82EDCF0]

[ocorten-2]

Thanks for the tip.,Steve.

But for all I can see it's not possible to make a query to look for all
iterations of only test.drw.

I can only select the following:







Olaf Corten

CAD/PLM Manager, Besi Competence Center - Other Business Applications

Fico BV, Ratio 6, 6921 RW Duiven, The Netherlands

Tel.: +31 26 3196215

[SteveVinyard]

Yeah easiest way to do this will be to create a specific folder in PDMLink called "Purge Stuff". Then copy/paste your objects in question into that folder. Once that is done, create a general query that only includes that folder. Then run the purge on that folder.

[cid:image005.png@01CAFB26.2FBA54B0]


Steve Vinyard
Application Engineer

[cid:image001.gif@01CAFB26.18612870]

[RandyJones]

On 05/24/10 10:29, Olaf Corten wrote:
>
> Simple question with hopefully a simple (positive) answer:
>
> How does one delete an old iteration of an object in Intralink 9.1?
>
> I've got the following
>
> test.drw B.0
>
> test.drw A.1
>
> test.drw A.0
>
> Now I want to delete iteration A.0. Only A.0. (don't ask me why, it
> just needs to go)
>
> How does one do that?
>
> Olaf Corten
>
> CAD/PLM Manager, Besi Competence Center - Other Business Applications
>
> Fico BV, Ratio 6, 6921 RW Duiven, The Netherlands
>
> Tel.: +31 26 3196215
>
> Fax: +31 26 3196200
>
> Mobile: +31 644548554
>
> _www.fico.nl <_">http://www.fico.nl>_
>
>
> ----------

This is one piece of functionality that is still missing from Intralink 9.1.
From the previous replies you have rec'd you have found out you can't do
this. Instead it becomes an exercise in Purging.

So in Intralink 3.x what was a simple select the objects(s), and then
select Object | Delete Selected (10 second process) becomes a complicated
ordeal in Intralink 8.x, 9.x.

Try this scenario:
1. add a new instance to an already existing family table
2. check in
3. now attempt to delete the just checked in family table and instance
4. In Intralink 8.x+ this is impossible. In Intralink 3.x simple.

--
------------------------------------------------------------------------
Randy Jones
Systems Administrator
Great Plains Mfg., Inc.
1525 E North St
PO Box 5060
Salina, KS USA 67401
email: -
Phone: 785-823-3276
   Fax: 785-667-2695
------------------------------------------------------------------------

[amansfield]

Randy:

I just went through a convoluted purge exercise with PTC tech support because of the situation you described: assembly model at iteration 3, someone adds an instance, then realizes it should be a separate model with a different number. I want to remove the latest iteration of the now generic assembly model and the only iteration of the instance.

Easy in IL3.x, impossible in WC9.1 except by checking out and splitting up the family table, checking it in, using purge to get rid of the previous instance and generic, then regular Delete to remove the now independent objects.

Just wondering if anyone's found a better technique just using Delete

Intralink 9.1 M020

[amedina]

Change companies? But actually, maybe if you back track all your steps up
to the point of that new fam table iteration then you should be able to do
it. Specifically the step where you used that new family table member in an
assembly or drawing. The assembly and drawing iteration cannot exist unless
that generic+instance exist. Thus you must delete the assembly as well as
the drawing iteration that includes the new family table member.

They should really make it so that you can have broken dependencies like
that. I bet PTC forced you to delete from the past up rather than from
today down by doing a purge. Its like building a sand castle and removing a
rock by taking all the sand from under the castle. Then again the sand does
take up space on your HD. Its probably a bad analogy.

[amansfield]

The other option is to delete the entire revision of the model + drawing including the instance and reload it. Waste of time and there will be situations where the dependies are too widespread to be able to do it without backing out a lot of stuff.

Just wanted to find a simple way.. I guess simple is not a word you can use when discussing Windchill 🙂