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

Family Table.....

Regular Member

Family Table.....

So.....I'm a bit rusty on this I'm sure. Am I missing a way to do Save As from Creo Parametric 2.0 and copy (save as) the family instances at the same time? PDMLink disallows workspace save as for modified/new objects lest I would use it (don't readily recall the rationale behind that). Using the rename can be a royal pain. Thoughts?

Thank you,
Brian Krieger
[75th]

7 REPLIES 7

Family Table.....

What happens when you try to Save As from Commonspace? That's where I recommend all my uses to do it from.

Family Table.....

No, Creo does not give you the chance to rename the instances when saving. Probably easiest to disconnect from Windchill, do the save a copy, then edit the family table to give all the instances new names. Then reconnect back to Windchill again.

From Creo
Save Generic = New Generic + Instances with same names as original
Save Instance = New, stand-alone model

From Windchill
Save Generic = New Generic + Instances w/Option to give instances all new names
Save Instance = New Instance added to existing Generic

Tom U.

Family Table.....

Tom,

That's what I was afraid of. I think that's similar to using Rename. At least keeps the family table intact. We just have to go in and manually change the instance names (2 instance family tables no sweat. 50 instance family tables......).

Donald,
Thanks! Unfortunately, these are modified and/or new files in the workspace or else we would use File>Save As from the workspace (or Commonspace). Sigh. Just a frustrating limitation.

Thanks, guys, I really appreciate it!

BK

RE: Family Table.....



In Reply to Tom Uminn:



"
From Windchill
Save Generic = New Generic + Instances w/Option to give instances all new names
Save Instance = New Instance added to existing Generic
"


In case of 'Save Instance' From Windchill, have you noticed that the generic is updated without extra iteration? It curses with my perception of historical traceability, but that's the way it's implemented.


Regards, Hugo.







<< ProE WF5 - PDMLink 10.1 M040>>

Family Table.....

Two things to check into

First, there is a config.pro setting ALLOW_SAVE_AS_INSTANCE and the default value is NO. Verify the setting you're using and if it's NO, change and try again.

Second, there is another option that may work ... in theory. (And you know what they say about using theory in practice, right?)

It involves tricking a system connected to Windchill by using the Creo Rename function. BUT! Be forewarned: I didn't test it this morning and it may be a complete failure. This is really only practical with smallish family tables. If the FT is large, then you probably don't want to use the method.

Before I type it all out, let me know if you have a small enough FT to make this viable.


Family Table.....

Hi all
Recently I have started to use Rename in Workspace for my "Save As" cases.
It will handle all related objects including family tables. Locally modified objects can be renamed this way too.
The procedure is this (in short form):

1. Export from Workspace the objects you want to Save As. (Tools > Export from Workspace)

2. Create a new empty workspace

3. Import the exported objects. (Tools > Import to Workspace)

4. Click Next to go to the Specify Options step

5. Set all ghost objects status to Reuse and the others to New and click Finish and Yes to add reused objects from Commonspace.

6. Rename the imported new objects in the Workspace (File > Rename)

7. Upload/Checkin the new objects.

This procedure is for Windchill 10.1.

/Bjarne
Highlighted

Family Table.....

We have the option let_proe_rename_pdm_objects set to yes.

Then you can rename everything in the Workspace.

When you save, the renamed objects get saved as new objects.

Best regards

Daniel García

El 16/09/2014 a las #4, Bjarne Frandsen escribió:
>
> Hi all
>
> Recently I have started to use Rename in Workspace for my "Save As" cases.
>
> It will handle all related objects including family tables. Locally
> modified objects can be renamed this way too.
>
> The procedure is this (in short form):
>
> 1.Export from Workspace the objects you want to Save As. (Tools >
> Export from Workspace)
>
> 2.Create a new empty workspace
>
> 3.Import the exported objects. (Tools > Import to Workspace)
>
> 4.Click Next to go to the Specify Options step
>
> 5.Set all ghost objects status to Reuse and the others to New and
> click Finish and Yes to add reused objects from Commonspace.
>
> 6.Rename the imported new objects in the Workspace (File > Rename)
>
> 7.Upload/Checkin the new objects.
>
> This procedure is for Windchill 10.1.
>
> /Bjarne
>
> *From:* Senchuk, Donald [
> *Subject:* [proecad] - RE: Family Table.....
>
> Tom,
>
> That's what I was afraid of. I think that's similar to using Rename.
> At least keeps the family table intact. We just have to go in and
> manually change the instance names (2 instance family tables no
> sweat. 50 instance family tables……).
>
> Donald,
>
> Thanks! Unfortunately, these are modified and/or new files in the
> workspace or else we would use File>Save As from the workspace (or
> Commonspace). Sigh. Just a frustrating limitation.
>
> Thanks, guys, I really appreciate it!
>
> BK
>
> *From:*Uminn, Tom [
> *Subject:* RE: Family Table.....
>
> No, Creo does not give you the chance to rename the instances when
> saving. Probably easiest to disconnect from Windchill, do the save a
> copy, then edit the family table to give all the instances new names.
> Then reconnect back to Windchill again.
>
> *_From Creo_*
>
> Save Generic = New Generic + Instances with same names as original
>
> Save Instance = New, stand-alone model
>
> *_From Windchill_*
>
> Save Generic = New Generic + Instances w/Option to give instances all
> new names
>
> Save Instance = New Instance added to existing Generic
>
> Tom U.
>
> *From:*Brian Krieger [
> *Subject:* [proecad] - Family Table.....
>
> So…..I'm a bit rusty on this I'm sure. Am I missing a way to do Save
> As from Creo Parametric 2.0 and copy (save as) the family instances at
> the same time? PDMLink disallows workspace save as for modified/new
> objects lest I would use it (don't readily recall the rationale behind
> that). Using the rename can be a royal pain. Thoughts?
>
> Thank you,
>
> Brian Krieger
>
> 75th
>