Skip to main content
C
CHASEONHO18-Opal
18-Opal
January 2, 2018
Solved

Check-In a top-level assembly every subcomponent / assembly modification?

  • January 2, 2018
  • 7 replies
  • 4399 views

In the case of visualization, changes are not made to subcomponents.
For example, all CAD data published on the first server has version A.1, and the assembly visualizes the subcomponents of A.1.
After modifying and verifying some of the following subcomponents, each component has A.2, but the assembly still displays A.1 and does not display the latest appearance of the modified components.
You must also check in the assembly again to see the latest appearance.

 

Do I have to check in every time a subcomponent changes to keep all assemblies in which the component is used up to date?

 

Is there another good suggestion?

 

thanks

Best answer by BenLoosli

Visualization is a snapshot of your assembly. Change a component and you need to take a new snapshot.

Yes, the proper method is to check out the assembly that has changed components, then check it back in to get the new snapshot.

 

7 replies

B
BenLoosli23-Emerald IIIAnswer
23-Emerald III
January 2, 2018

Visualization is a snapshot of your assembly. Change a component and you need to take a new snapshot.

Yes, the proper method is to check out the assembly that has changed components, then check it back in to get the new snapshot.

 

C
CHASEONHO18-OpalAuthor
18-Opal
January 2, 2018

Thanks

 

as result, CAD user has not problem check a data real-time.
but normal user who use Creo view or visualization maybe doesn't check a data real-time.
cause Creo View and Visualization was must check-in when component was modified.

B
BenLoosli23-Emerald III
23-Emerald III
January 3, 2018

Set Windchill to publish on check-in.

Every file that is checked-in gets a new image published, so everything stays up-to-date.

 

T
TomU23-Emerald IV
23-Emerald IV
January 5, 2018

Windchill can be configured to either publish "As Stored" or "Latest".  Some companies like to publish drawings "As Stored" and publish assemblies as "Latest" but unfortunately this mixed approach is not possible without customization.  If you publish everything as "Latest", Windchill will automatically mark all upper level assemblies as out of date when a lower level component changes.  You can then configure what you want to happen next - either automatically republish each of the upper level assemblies, or just leave them marked as out of date.  Realize that automatic republishing ("Rev rolling") can quickly generate a huge number of publishing events.  One possible option is to use positioning assemblies (or extended positioning assemblies).  These can automatically load the current (latest) version of each component without having to republish each upper level assembly every time a lower level component is updated.

    Terms & ConditionsAccessibility statement