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.

3 Comments
BenLoosli
23-Emerald I

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.

JamesAvis
13-Aquamarine

The problem is that when someone uploads something in their workspace, it occupies the file name.  It's true that other users may not be able to see that it exists, but they can determine it exists by trying to check theirs in and getting a surprise error.  This leads to confusion because they had the Compare Status column shown to prevent this sort of thing.  To them, it's clearly not working, or the error is wrong, so they call me.  This is poor design in Windchill.

olivierlp
Community Manager
Status changed to: Archived

Hello,

We are archiving your idea as part of a general review. This action is based on the age of your idea and the total number of votes received, as per this announcement.

You can always post a new idea with all the details required in the form.

Thank you for your participation.