ProductView Combined Current Drawing With Out-of-date CAD Models

[srector]

We recently noted a problem with ProE/ProductView, and I was wondering if anyone else had run across a similar problem.

From a ProE workspace (WF3, m230), a user selected a drawing and it's associated models for check-in. They then logged into PDMLink to verify that their drawing had published correctly in ProductView. However, when they viewed their drawing in ProductView they noticed that the drawing still reflected the OLD version of the model (rather than the version they had just checked in).

We tried deleting the representation and re-publishing, but the error would not go away. Finally, we checked-out the drawing, made a change, undid the change, and checked-in the drawing. That triggered another re-publish job for the drawing. When we checked the drawing this time, in ProductView, the error was gone.

This led us to the following conclusion. When a user tries to check-in a drawing and it's corresponding model files all at once, there is a possibility that the drawing can get checked-in <u>just ahead</u> of the models. If this occurs, the drawing MAY latch on to the older version of the model (at least as far as ProductView is concerned). So, even though the drawing may look correct in ProE, it can end up being published incorrectly.

To prevent this from occurring, we have instructed our users to check-in all of their model changes prior to checking in the corresponding drawing (i.e.: in two separate operations). We hope that this will prevent any "Race Conditions" and force the drawing to always grab the latest version of the part.

We are using PDMLink 9.0 m060, ProductView 9.0 m090, and PV Adapters 9.1 m020.

Has anyone else experienced this condition? Is anyone aware of any system settings we can implement to guard against this behavior?

Thank you!

Steve
This thread is inactive and closed by the PTC Community Management Team. If you would like to provide a reply and re-open this thread, please notify the moderator and reference the thread. You may also use "Start a topic" button to ask a new question. Please be sure to include what version of the PTC product you are using so another community member knowledgeable about your version may be able to assist.

[david.brisson.p]

Hi Steven,

Although my answer will surprise you, this is the expected behaviour. By default, PDMLink publishes with the As Stored configuration. So, if you only update a model and not its drawing, the representation in PDMLink will be the same. I do believe that it is the right behaviour to make sure that your representation is consistent with what was submitted to your database. But, you can configure PDMLink to mark out of date the representation so that the user is notified thatmodelsin the configuration have changed. The only down side is that it does require a lot of Hardware resource to make that validation but if you have a good PDMLink server, this should not be an issue. See TPI 131667 for more information.

David

[MikeLockwood]

It's actually essential that it be like this.

You want and need the drawing to be published as it was stored, ignoring model changes that happened after it was stored, so that you:

- Do development using the latest of all models

- Do business on the as-stored condition of the drawing, ignoring model changes until the drawing has been updated to incorporate them in a managed process

[cc-2]

Hello

we have a different approach where the publisher is configured to take the latest iteration of the model when publishing the drawing.

This allow us to work more quickly as we only need to "manipulate" the model and not the 2D drawings too.

Obviously it depends on the nature of the change.