Intralink file overwrite, help required

[nTops]

I checked out an assembly into the wrong workspace this morning, overwriting 3 days of work (un-checked in).

Is there any way to revert a workspace to the condition it was in the previous day?

I can see all the files I need in the .proi directory, just can't get at them through intralink.

Thhanks in advance

 

[dufferinco]

Use the frame manager to select an appropriate time from the previous day. This will do what you want, however, unless you want to loose all of the work that was done after that time, do not attempt to save any changes from Pro/E.

 

[nblylyddy]

We have reported to PTC that in IntraLink, the check out to workspace box should by default be blank. This would force a user to have to select the workspace of interest (minimizing these kinds of mistakes). If this would help you also, then mention it to PTC.

Highest regards,
NbLYLYDdy

 

[nTops]

Thanks for the input. Unfortuatly we had frames disables as default. Anyway around that?

It would be a great help if PTC left the checkout workspace blank, that exactly why I made the mistake. I am going to recomend to our design team to have a workspace called 0000 or somthing similar to help catch these errors.

 

[peppinu]

nTops
Have you tried "importing from disk" under the"object" menu and working up through the directory structure?

Joe Borg

http://www.methode-eur.com

 

[cehall]

Intralink is a great tool. But, we all make mistakes and overwrite once in a great while. Or just need a copy of the part a couple of files ago.

Go into MyComputer and into the back door of file management.

You can fine the Intralink WorkSpace, list files, and remove files or copy files just like any other computer file. Just remember to copy files with higher numbers if you want it to be the one checked into Intralink.

 

[peppinu]

Cehall
I do not know if I understood you or not. NEVER remove or delete files via explorer or any other file manager in the operating system below the workspaces directory. This will
corrupt your "local.ddb" file wich keeps track of all files.


Joe Borg

http://www.methode-eur.com

 

[cehall]

We have never had a problem with "local.ddb" becoming corrupt. You must clear out of workspace ram the file first. Then, open the "file renamed" thru file directory path. After pulling it in ram, save the file and it shows up in Intralink workspace correctly. You can also import the file while in Intralink workspace with the new name.
It is a work around ... not a normal work flow! Don't do this often and I don't keep workspaces long.