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

"CAD part is not unique"

Re: "CAD part is not unique"

Haris,

What do you have set for the following preference in Preference Management:

Operation > Upload Operation > Upload > Upload Drop Number File Extension

If set to Yes, then the error could be caused because you have CAD Docs that end up with the same number.

Example:

Test.prt, Test.asm, Test.drw

When these files are uploaded they will all try to have the same number, "Test". This can cause the uniqueness error.

Alternatively, the CAD part has been uploaded within a workspace, but not checked in. You can try using the attached SQL scripts to find out which workspace(s) have CAD Docs with the names causing the trouble.

Re: "CAD part is not unique"

Thanks for your reply.

By default upload operation set to no.

Since I am a beginner I dont know how to run the script

Re: "CAD part is not unique"

You need to run them on the Oracle database machine.

Example:

C:\>sqplus {wc_schema_username}/{wc_schema_user_pw}@{Windchill_SID} @{Path_to_SQLScript}

C:\>sqlplus guest/guest@wind @c:\temp\wc7_find_download_caddocs_cadfilename.sql

When prompted you would need to specify the filename of the CAD Doc.

Re: "CAD part is not unique"

Haris,

Were you able to get past the error?

Re: "CAD part is not unique"

Hello Haris,

Just today I received same error what you were getting and got solution too.

Basically it is a question of upload. I tried to checked in from my local work space & uploaded but checked in error shows that xx.prt is not unique due to another person uploaded same part number in his respective work space & still same part in his local work space.

I request that person to clean up uploaded work space and tried same part to checked in and it is successful.

Hope this will help you and mark correct answer if you agree the same.

Thanks,

Jitu Thakor

Re: "CAD part is not unique"

Got the same error again and again, despite there isn't any other cad file or document called the same way.

The more I go along using this software, the more I worsen its reputation. It is just making you lose time in such stupid problems (and so many other happened! like "workspace corruption" for example...shameful).

And their development team? they say they don't know what's caused by....like what they say about people not recognizing their own calligraphy!!

Re: "CAD part is not unique"

One way to force this error to occur is to have a drawing and a part and give them both the same 'number' by removing the .prt and .drw suffix. This will be flagged as 'not unique' when the user tries to check them in.

Re: "CAD part is not unique"

Tommaso,

when ever we have this error it is always related to the Number not ending with the file extension and that too in upper case.

Ex: TEST.PRT is ok and not test.prt

Try to rename the number to include extension in uppercase and checkin.

Re: "CAD part is not unique"

Hi David Schenken ‌and Manjunath RV‌,

thanks for your replies.

In the meantime on Wednesday I found what the problem was and the workaround.

I already knew the error coming both in the case of "same number for prt and drw", and in the case of the upper case text.

But these were not my cases (unfortunately, cause I would have fix the problem sooner).

I discovered instead this issue:

-I retrieved, from the local disk, a step assembly which, together with all of his components, was already named on the disk. (the filenames);

- For reasons that I don't include here for easiness of description, upon retrieval one of his subassemblies took the default name that Creo gives to brand new unnamed stuff (it was asm0001);

- The problem was that there already was a asm0001 in another workspace, so when I firstly tried to save and upload the asm, it gave me the "CAD part is not unique" error;

- "no problem" I told myself, I just have to rename the asm0001 to, let's say, b.asm, and the problem is solved, as often done before.

- but no, the software told me again the same error as if even the new name b.asm was around somewhere (I renamed both file name and number)..

- with absolutely no idea of what the cause was, I solved the thing by simply erasing the asm from the WS, then I re-uploaded the asm and did, as first thing (before uploading), a local rename of the assembly so that there wasn't any asm0001 around. Then, I uploaded it and without any problem.

So, during the first retrieval it seemed like the software remembered that the previous name of b.asm was asm0001 (which had a conflict) and so "extended" somehow this conflict to b.asm (even if there wasn't any b.asm around!).

I think it might have been a problem lying "undergound", at level of the core machine-code (don't know how to call it) of CAD parts. (as if this core-machine-code associated to the cad part hadn't been renamed together with the "surface-level" name b.asm).

I hope to have been clear enough and maybe to have helped also the original poster Haris Surya, if this was his case too.

Bye