cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
Showing results for 
Search instead for 
Did you mean: 

File Vault Move

snellutla
1-Newbie

File Vault Move

Hi,

We moved one of file vault to a new location successfully. After the file fault
move, we made couple of changes to some of the existing files and checked them
into commonspace.
The information window on newly checked-in files showd proper information.

But when we ran object report through DSMU, it showed folder lcoation for the
files checked-in before the move but showed emplty space for newly checked-in
files.

Please find the attached jpeg file.

Please let me know If I need to change any settings to show proper object
report.

Thanks,
Sharath


3 REPLIES 3

Were the files checked-out before the vault was moved?
If so, that is your problem.
The workspace keeps track of which fileserver where the file came from.
Unfortunately, the client attempts to send the file back to the same fileserver during check-in.
This should be a bug, but PTC never addressed it.

The workaround is to delete the file from the workspace, check-out a feresh copy and continue from there.
Do not simply Update the file. You must delete and check-out fresh.

Gerry

After we moved file vault I re-checked the same file and made modifications.

This is what I found when I checked in the same file in 2 different ways

scenario - 1

1check-in the file to your workspace
2modify intralink attributes
3check-in

In this scenario after we ran the object report, intralink did not assigned the
folder to the newly checked-in component.

Scenario - 2

1check-in the file to your workspace
2launch pro-engineer
3modify part file
4check-in

In this scenario, intralink assigned a folder name to the newly checked-in
component.

It looks like it is intralink behavior.

Thanks for your response,

Sharath




When you change only the attributes and check-in, only the meta-data is updated in commonspace.
Intralink knows that the file itself has not changed and does not upload it during check-in.
The result is that the new version (commonspace object) uses the same file as the prior version.
This is intentional behavior to minimize disk usage.

Gerry

Announcements
Learn more about how we are using our browser poll here