Default properties/preferences in Windchill don't copy forward epm document representations in the new iteration of the owned wtpart.
There are some properties to have this beaviour but if the epm document is republished the new iteration of the wtpart remains old.
I would like to have always equal the representation viewable in the epm document and in the owned wtpart.
Steps to reproduce the issue:
1) Create a epm assembly with some components and a owned wtpart.
2) Publish epm --> representation viewable in epm and in wtpart (the same)
3) Iterate wtpart --> wtpart without representation or with a copy of the original representation (dependes of copyforward and restrict options)
4) Edit a component of the assembly
5) republish epm --> representation of the epm changes, new iteration of the wtpart remains old (or empty), old iteration of the wtpart is upgraded correctly.
In my system this beaviour is wrong.
And in yours?
(PTC Case C12879050 + C12812021 + C11049803. Articles CS61223, and SPRs 2097075, 2186339)
This was solved in 11.0 M020, if I understand your concern correctly, with the property publish.representable.owner.usefirstiteration (set this to false to get the behaviour you're missing). See CS223752. See also my own post on this very subject https://community.ptc.com/t5/Windchill/Is-PTC-s-spec-faulty-Publish-EPMDoc-updates-non-latest-WTPart... .
I don't understand what does it mean "usefirstiteration" but I will try. I think that a better name could be "uselastbuilt".
Now I have 10.2 M030 yet.
I agree that the naming could have been more obvious but their default (according to original spec) is to use the iteration of As built. If you want to diverge from that practise setting it to false kinda makes sense. From a PTC perspective. Probably.
I've tested this on 11.0 and can confirm that it works, and for me that is all that matters. 🙂
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.