Family tables with WF4M150 and Creo Element Pro 5.0M150

[cc-2]

Hello

we have just upgraded from WF4M150 to Creo Element Pro 5.0M150 and are still using PDMLink 9.1M050

We came across an issue we did not except. (only one, we are lucky !!!)

We have family tables created in WF4 and with WF4 depending on the nature of the change we want to make either we needed to check out the instance and the generic or the entire family table

When we use Creo Element for the first time with a family table which was last modified with WF4, it appears that we need to check out the entire family table regardless of what we want to do. This is a different behaviour than with WF4. We thought, OK, maybe WF5 wants to put its footpring in the family table. Next time we want to make a change it will be back to normal (ie depending on the change we do not need to check out the entire table). So far, it seems that we must always check out the entire family table.

This is obviously not good as normally some instances are released.

Have you esperienced such behaviour ?

Thanks

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.

[RandyJones]

On 03/26/13 13:22, NacNac MOTT wrote:
>
> Hello
>
> we have just upgraded from WF4M150 to Creo Element Pro 5.0M150 and are still using PDMLink 9.1M050
>
> We came across an issue we did not except. (only one, we are lucky !!!)
>
> We have family tables created in WF4 and with WF4 depending on the nature of the change we want to make either we needed to check out the instance and the generic or the entire family table
>
> When we use Creo Element for the first time with a family table which was last modified with WF4, it appears that we need to check out the entire family table regardless of what we want to do. This is a different behaviour than with WF4. We thought, OK, maybe WF5 wants to put its footpring in the
> family table. Next time we want to make a change it will be back to normal (ie depending on the change we do not need to check out the entire table). So far, it seems that we must always check out the entire family table.
>
> This is obviously not good as normally some instances are released.
>
> Have you esperienced such behaviour ?
>

Yes. See this TAN:

[cc-2]

Hi Randy

thanks for the link. Much appreciated.

However it does not state that once the FT is checked in with WF5, then the next change in the FT will be done in the "normal" way

for instance if I want to change the value of a parameter which is already in the table for one instance, I should not need to check out the entire family table. This was the case with WF4 but so far we cannot do that. It seems that we must always check out the entire family table regardless of what we want to do and even if the previous iteration was already checked in entirely with WF5

Here, when I mention WF5 I am talking of Creo Element Pro 5.0 M150

Thanks