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

Flag ALL non-unique file names in the workspace as non-unique in the Compare Status column

Flag ALL non-unique file names in the workspace as non-unique in the Compare Status column

Non-unique file names do get flagged as non-unique in the Compare Status column of the workspace, but not all of them do.  If the conflicting item has been uploaded, thus reserving the file name, but has not been checked in, it does not trigger a flag in another user's workspace.  It will, however, prevent check in for that other user, with the error that it is not unique.

 

PTC has accepted this as correct behavior.

 

Consistency is key.  If the file name or number is non-unique, it must be flagged in the Compare Status column of the workspace, no exceptions.

 

Also, no, we aren't going to use the preference to allow uploading non-unique file names, because it doesn't actually allow uploading non-unique file names.  It really just renames the item to a unique file name, but it causes more problems than it solves.

1 Comment
Sapphire II

Until the file is actually checked-in, it can be renamed in the workspace, thus removing the non-unique status. Since no one can a file that has not been checked-in except the creator, I agree with PTC that it is working as designed. There is some overhead with checking and updating all workspaces in a system, that in this case may not be true come check-in time. A lot of times people create dummy part numbers on their files until it is ready for check-in. 

 

If you want a check on file name creation, put it at creation time. User A has 123456.prt in his workspace. When User B goes to create a new part and names it 123456.prt, this is when it should be flagged as file name already exists.