Skip to main content
D
didriek1-Visitor
1-Visitor
February 20, 2013
Question

family tables and windchill modifying/checking them in/out

  • February 20, 2013
  • 2 replies
  • 7756 views

When I work on a family table generic or instance I notice that windchill doesn't automatically check out en modify ALL instances and the generic?

What results in conflics when I want to check back in....

Are there settings you can configure that:

no mather what you do to a falily thable, ALL gets checket out and ALL gets 'modified' so I don't have troubles with instances that are not checket out and not displayed as 'modified'

I don't even understand why he doesn't check out all and modify all if it's needed to check back in???

It give's me extra work figuring out the conflicts while he knows all relations...

Thanks in advance,

Didriek

2 replies

GregoryPERASSO
GregoryPERASSO16-Pearl
16-Pearl
February 20, 2013

There's some preference to control checkin under Site/WorkGroupManager Client/Indenendently modify instances

But if you're in Creo / proE, by default .

If you change something in the generic that will impact all the instances (geometry, add a column in FT ...), when saving the generic, all the instances will be proposed for checkout

if you change something only in one line in the family table (ie modify a particular instance), when saving the generic, it will checkout the corrssponding instance. No need to checkout all the instances ...

You should not have conflict or missing "non checkout" instances ....

D
didriek1-VisitorAuthor
1-Visitor
February 20, 2013

We have been working on a large assy full with family tables.

Now, I verified, regenerated a lot to reduce all the conflicts when opening the top assy...

What resulted in a huge modified workspace, but when I try to check in now I get the following conflicts for a part or 30 instances:

All checked out family table member have to be checked in together.....

And I recognize a lot of sheetmetal 'flat states' .... do I really have to open them one by one and make sure I modify them and check them out or are there some options to avoid this or do this quick?

Add to workspace does check them all out, but some of them are not modified and windchill wants them to be modified before checking in. However, since windchill knows the generic/instance relations I expected winchill to set them all to modified when working in the table... but as I have unmodified flatstated I don't understand, especially using a mapkey; verify-regenerate-save-close

Busy 2 hours now trying to check in these ***ing tables

GregoryPERASSO
GregoryPERASSO16-Pearl
16-Pearl
February 21, 2013

If it can help, in the checkin windows, you can force checkin for parts that are check outed , even if they are not modified. ... So you're able to checkin all the FT, but you will have iterations on "non realy modified" parts ...

Or you can sort, or filter in a custom view, your workspace, display only checkout and non modified parts instances. And then undo checkout of these instances. You will then be able to checkin your FT, as only the generic and only the modified instances remains checkout

anyway, I prefer adding to workspace without checking out. and then let ProE propose the part to check out on the fly when I modify it.

regards

D
didriek1-VisitorAuthor
1-Visitor
February 28, 2013

I need to read and verify all you have been posting... thanks for the info and insights!

What I did to be able to check in and update again is opening all the instances that gave coflics in Creo.

I opend the generic, modified it someway (surpressing a base feature for example) so Creo asked to check all out, veryfied all and that way I ended up with all instances and all genericas as 'checked out' AND 'modified' so I was able to check in...

Time consuming, but at that moment the only way...

Now I'll read your insights and see if this can be avoided or done differently...

(working in Creo 2 M040)

Terms & ConditionsAccessibility statement