What triggers a PART to be linked to structure instead of the owner CAD

[RME_DH]

Version: Windchill 12.0

Use Case: When creating a CAD object and checking in to create a associated PART with owner links, sometimes (not always) the CAD object gets a visualisation OK but the PART is not visualising, instead it has a "open default config spec in creo view" instead of the 3D visual.

Description:

I would like to try to get an explanation to this behavior - its a little convoluted to explain, so hopefully this makes sense.

1. create a CAD object and check in via WGM to create an auto association PART as owner
2. the CAD object triggers a visualisation job and creates ok
3. the PART doesn't trigger a job and is listing no thumbnail or visual
4. the PART has "open default config spec in creo view" instead and the content tab just list the structure
5. If you goto the PART and try to republish - it has a different wizard and settings

Some screenshots to help

the PART with owner association

[TomU]

The representation from the non-latest CAD object (shown above) probably isn't going to update the representation for the latest version of the WTPart.  When you look at the 'CAD/Dynamic Documents' section of the WTPart's 'Related Objects' tab, what version of the CAD object does it show the owner link to?  Is it the -.1 version of the CAD part, or something later?

[RME_DH]

Thanks for the Reply TomU,     I think I just had a misleading screenshot for that association, sorry.   the -.1 wtpart and -.1 CAD are associated as owner and exhibit this behavior.    

So after a bit of experimenting with everything i know, setting a manual "rebuild Part from CAD" action from the CAD actions menu, seems to fix the issue for the latest rebuilt versions.    however, 99% of parts and cad are working as expected, its a just a few (maybe about 2000 out of 100's of 1000's) that fail a weekly scheduled visualisation job the seem to have this issue - from the initial check in.       This led to checking the preferences at SITE/ORG and user, and they are all set to auto associate and trigger a build action on checkin and auto associate - which explains why it works majority of the time.

there must be a scenario that I am unaware of that causes this (or a bug?).

[HelesicPetr]

Hi @RME_DH 

It could happen if a user connects the existing WTPart to CAD and then just do a check-in of the  WTPart.

Then the visualization is not be propagated to the WTPart.

Just a Build WTPart function will do it in this case or an another CAD model check-in operation.

I have experience that sometimes the WTPart build process is not 100% successful during the check-in from Workspace and the parts are just connected without successful building and propagating information.  

The reason is usually unknown but you can see it in a Compare to WTPart/Compare to CAD wizard. 

Also there are many others reasons for this behavior. 

Check-out/in just the WTPart without copy forward representation and so on. 

PetrH 

[RME_DH]

Hello HelesicPetr,

---

@HelesicPetr wrote:

It could happen if a user connects the existing WTPart to CAD and then just do a check-in of the  WTPart.

Then the visualization is not be propagated to the WTPart.

I have double checked this, and from what i can tell, both CAD and wtpart were created at the same time.  This would have been via WGM, with build associated PART checkbox checked, as that is our default.

---

@HelesicPetr wrote:

Just a Build WTPart function will do it in this case or an another CAD model check-in operation.

---

In our case, no number of extra check-ins of the cad or wtpart rectify the issue, not until a "build associated part" action is triggered - which does make sense.

---

@HelesicPetr wrote:

I have experience that sometimes the WTPart build process is not 100% successful during the check-in from Workspace and the parts are just connected without successful building and propagating information.  

The reason is usually unknown but you can see it in a Compare to WTPart/Compare to CAD wizard. 

---

I tend to agree with you here, it seems like a bug that the build process does not complete successfully sometimes.  On the surface it all looks ok, with a owner association created and all other linkage between wtpart and CAD working - just the build process and of course visualisation not generating @ iteration 1 - i will do some more knowledgebase searching for build process, and if nothing is found, I will submit to a PTC ticket.   

Till then we will just have to be more vigilant with QA at earlier iterations to fix this before part is released.

Thankyou

---

---

[d_graham]

@RME_DH ,

Is the problem that you want the latest iteration of WTPart to have a representation whenever the Owner CAD object is checked in published?

So C.3 cad has rep —> WTPart C.3

C.3 is checked in and published creating C.4 and new representing for C.4

 Now you want WTPart C.3 to change its rep from cad C.3 rep to cad C.4 rep automatically.

Is that what you’re looking for?

If yes, very doable.

[RME_DH]

Hi D_graham,

no, I don't think this is what this problem is describing.     The best I can describe it as above with discussion with PetrH,  that upon first check in from WGM, with "create associated wtpart" checkbox ticked and all user preferences set to build associated wtpart at check in, SOME wtparts do not get built at this point and therefor do not get a visualisation created properly.

They seem to display an owner association, but they behave differently until manually 'rebuilt' at a later iteration when spotted by a user. 

Is what you describe, "out of date representations"? 

[d_graham]

@RME_DH , no, I’m not describing out-of-date.

After reading you reply I now see that the visualization end of this is only a symptom.

I do see where if a CAD model is a member of an assembly and the assembly has a WTPart structure it does seem like the newly created WTPart should show up the assembly’s WTPart’s structure automatically.

Is this what you’re looking for?