cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
Showing results for 
Search instead for 
Did you mean: 

Community Tip - Need to share some code when posting a question or reply? Make sure to use the "Insert code sample" menu option. Learn more! X

Welds causing Family Table Instances to become "modified in session" upon retrieval

TL_10036246
5-Regular Member

Welds causing Family Table Instances to become "modified in session" upon retrieval

I've got a family table of an assembly who's components are also family tables. The only thing that changes in the top level generic is the overall size and this is done by selecting the appropriate component instances for said size. We're using Windchill to manage all of our parts and workspaces.

 

I am trying to add welds to the top level generic but when I do, it causes verified instances to become "modified in session" when retrieved. Even if retrieved into a brand new and empty workspace. This is an issue because a modified instance can cause the generic to become modified which in turn modifies all other instances in the table. This particular table is has hundreds of instances and it is simply not feasible us to bring in hundreds of instances and re-verify the table every time we need to use a member of this family table. I've tested this family table without the welds and did not run into this issue which is what leads me to believe that the welds are causing this.

 

What are some of the more niche reasons that an instance would become "modified in session" upon retrieval? And are there any config options that have to do with either welds or family tables that could be causing this?

4 REPLIES 4
TomU
23-Emerald IV
(To:TL_10036246)

Some things to check:

https://www.ptc.com/en/support/article/cs63310

https://www.ptc.com/en/support/article/CS32596

 

Were these family table models built in an earlier version of Creo Parametric?  There was an issue back around Creo 3 or 4 where all family table instances created prior to this had to be regenerated in the newer version of Creo in order to update some internal stuff.  Until that was done they would show out of date every time they were retrieved.

remy
21-Topaz I
(To:TomU)

to add to the list of article to try: https://www.ptc.com/en/support/article/cs309734 

TomU
23-Emerald IV
(To:remy)

We've completely disabled instance accelerators company-wide.  Too many issues with them.

TL_10036246
5-Regular Member
(To:TomU)

All components were created in either Creo 6 or 7.

Top Tags