Skip to main content
D
dsalotto10-Marble
10-Marble
November 22, 2024
Solved

Rename part error "part not unique" error during checkin

  • November 22, 2024
  • 5 replies
  • 2144 views

Renaming parts in Creo 9.0 some pointer to old part not released. Can't check in to Windchill without error "part not unique."   Part not in Commonspace or other Workspace.

Best answer by dsalotto

Resolve: 

 

Now in WC12, you no longer can name an assembly and part the same name as you previously could since the conception of Interlink then Windchill.

 

4 months and counting and it's all yours, gang,  I certainly won't miss PTC.        

5 replies

Catalina
CatalinaCommunity Manager
Community Moderator
November 22, 2024

Hi @dsalotto 

 

Thank you for your question! 

 

I’d like to recommend to bring more details and context to your initial inquiry. 

Please consider adding screenshot(s) to better understand what you are trying to do in your process. 

 

Please refer to this guideline to make your questions more likely to receive a quick and useful answer. 

This will increase your chances to receive meaningful help from other Community members. 

 

Thank you for your participation and please let me know if you need further assistance! 

 

Best regards,

Catalina | PTC Community Moderator
T
TDT16-Pearl
16-Pearl
November 24, 2024

Hi @dsalotto,

 

Are you looking to rename or renumber?

Renaming will not cause any errors.

However, when renumbering, you cannot assign a number that already exists in Windchill. This action is not allowed.

 

D
dsalotto10-MarbleAuthor
10-Marble
December 2, 2024

Thanks for responding but not a basic 101 resolve.  I've been a Sys admin Interlink/Windchill user of 33 yrs.   

 

I've identified this as a incredibly disastrous WC 12 issue and not a renaming issue.  WC 12 can't upload or check in harness files without a "part not unique" issue.  Putting in a ticket is as painful as a root canal.  Was looking for someone with the same issue.   

 

Thanks, 

 

 

HelesicPetr
22-Sapphire II
HelesicPetr22-Sapphire II
22-Sapphire II
December 2, 2024

Hi @dsalotto 

Don't be upset.  

Have you identify the root case? Usually it is cased that someone else has the part in the workspace as a new one.

Then another user can not upload own part that has same number/filename .

User can not see the part because it is new in different user workspace. 

 

Only admin can use global search for that number/filename and then he can identify where the object is. 

 

As a admin I would also check a logs . Take a Ida2A2 identification from the error and try to get the direct SQL select in database to get information if the object exists and where it is stored. 

PetrH 

D
dsalotto10-MarbleAuthor
10-Marble
December 2, 2024

Thanks for responding, but please read my last post. 

 

Have a good day,

D
dsalotto10-MarbleAuthorAnswer
10-Marble
December 9, 2024

Resolve: 

 

Now in WC12, you no longer can name an assembly and part the same name as you previously could since the conception of Interlink then Windchill.

 

4 months and counting and it's all yours, gang,  I certainly won't miss PTC.        

B
23-Emerald III
BenLoosli23-Emerald III
23-Emerald III
December 9, 2024

By our company naming rules, we never allowed a part and assembly file to have the same name because it led to WTpart linkage issues. Glad PTC has finally closed that hole in functionality with WTparts.

D
dsalotto10-MarbleAuthor
10-Marble
December 9, 2024

All I can say is this was normal procedure since the early 90's keeping the part and assembly the same name for things like harnessing and inseparable assemblies such as a sheet metal part with pem inserts or plastic parts with untrasonic inserts.    

 

Here's a few of thousands of Windchill examples where we have the same name.    

 

dsalotto_0-1733756675468.png

 

 

dsalotto_1-1733757323665.png

 

 

avillanueva
23-Emerald I
avillanueva23-Emerald I
23-Emerald I
December 13, 2024

When you say renaming in Creo 9.0, do you mean you are opening and using that tool to do the rename. Just know that this creates a copy in the system as if you did a save as. Previous copy still exists. Is it possible that your renames are causing a conflict on the way in. Both filename AND Number have to be unique which is why most use filename=number so that you have only one unique attribute to deal with. Let us know if this has been solved since it was a few weeks old.

avillanueva
23-Emerald I
avillanueva23-Emerald I
23-Emerald I
December 13, 2024

Apologies for not scrolling down. Ignore my last post. 😞

Terms & ConditionsAccessibility statement