Windchill Creo Drawing regeneration Issue.

[KR_1012184030]

In Windchill, the Creo assembly drawing is not reflecting the latest updates made in Creo Parametric. After publishing, Creo View still shows the old dimensions. When opening the drawing directly from Windchill in Creo Parametric, it also displays outdated dimensions until regenerated. However, if I open the assembly first and then the drawing, the dimensions appear correctly.

[avillanueva]

If you are publishing "as-stored", this is likely the case. Easy way to check is add drawing to a workspace but show the full list of objects before you commit the action. Here, toggle the configuration from "as-stored" of the drawing to "latest". You should see the model flipping iterations. Publishing as-stored, which is not wrong in any way, takes the fixed iterations of the dependents, as it was when the drawing was checked in, and uses that to create the representation. In this mode, you should always check in the drawing last or at same time as its models.

[vnamboodheri]

Hello @KR_1012184030, 

It looks like you have a response from a community champion. If it helped you solve your question please mark the reply as the Accepted Solution. 

Of course, if you have more to share on your issue, please let the Community know so other community members can continue to help you.

Thanks,
Vivek N.
Community Moderation Team.

[joe_morton]

There's a Creo setting that controls where dimensions added in the drawing are actually saved. I believe the default is that when you add a dimension in the drawing, that dimension actually gets stored on the model itself. This is different from displaying an existing dimension in the model on the drawing. That could be at play here, although I'm not sure of what the exact interaction would be.

For the immediate issue, I'd try checking out model and drawing, fully regenerating both, then checking both in. I would think that that should resolve the immediate issue.

For your publishing, you can specify that the publisher regenerate the objects before publishing. We have this turned on. That might help address the issue, just expect that it can significantly increase your publishing times.