Skip to main content
7-Bedrock
February 19, 2024
Solved

Master exists more than once

I am using Windchill PDMLink Release 11.2 and Datecode with CPS 11.2.1.8

Hi,

User not able to promote the object.
Getting the error message as:
Error while trying to promote PDMLink objects : Master exists more than once: XXXXX.asm
There is no WT Part availabel for the assembly.
Could you please help to fix the issues.
Thanks in advance.

Thanks & Regards,
Balakrishnan

Here are the errors that I faced
Error while trying to promote PDMLink objects : Master exists more than once: XXXXX.asm

7-Bedrock
February 26, 2024

Hi,

Thanks for your response.
One of the Assembly instance and related drawing present in level 3 of parent assembly has multiple WT Part connections. The issue got resolved after breaking all the associations.

6 replies

avillanueva
23-Emerald II
February 19, 2024

Are there any customizations around the promotion request in use? This is just CAD data right?

Translate
7-Bedrock
February 26, 2024

Hi,
Yes, this is only CAD Object. No promotion request is used in this case. Thanks for the followup.

Translate
joe_morton
19-Tanzanite
February 21, 2024

Can you share a screenshot?

 

Does the assembly contain the same child on two different line items? 

Translate
7-Bedrock
February 26, 2024

Hi,

Thanks for your response.
One of the Assembly instance and related drawing present in level 3 of parent assembly has multiple WT Part connections. The issue got resolved after removing all of them.

Translate
Fadel
23-Emerald II
February 22, 2024

check if you really have duplicate numbers :

select wtpartnumber, count (wtpartnumber) from wtpartmaster GROUP by wtpartnumber ;

select DOCUMENTNUMBER, count (DOCUMENTNUMBER) from epmdocumentmaster GROUP by DOCUMENTNUMBER ;

 

Do you have any Drawing  associated with multiple WTParts of referenced 3D models with Content / Calculated associations ?

 

 
Translate
Buiꓘa
ptc-45508287-BedrockAuthorAnswer
7-Bedrock
February 26, 2024

Hi,

Thanks for your response.
One of the Assembly instance and related drawing present in level 3 of parent assembly has multiple WT Part connections. The issue got resolved after breaking all the associations.

Translate