As the use of CreoView increases in our processes our CAD team gets repeating questions of why the CreoView viewable does not match the Creo Parametric model? Upon investigation we learn that a lower level component was edited and checked in to PDMLink which created the new as-stored image for that component. When the parent assembly is viewed in CreoView they expect to see the latest lower level component like they would if they added the parent to a workspace and opened in Creo Parametric. This is not the case with CreoView since it creates the collection of viewables associated to the checked in file. Whereas Creo Parametric builds the parent/child dependancies based on a preference to use "latest" versions.
If I may ask, how are other companies dealing with this scenario?
To pose a simple question with a hard answer. Why can't CreoView build its viewable image using similar function to Creo Parametric where it pulls the latest image files from the components to build the parent image ? This would certainly slow down the growth and maintenance of millions of image files and present what most users expect to see when looking at the lite weight file.
Kind Regards, Jim