Design Table - Unwanted Part Update

[rjl007]

Hello,

I'll try to explain by steps:

1-Create a catalog part with a design table
2-Part is inserted into a Product in one of its configuration
3-Product is finished and part should not change
4-Catalog is changed, for example, one configuration is added
5-Reopening the old Product the part updates to new configuration - THIS can be an issue

One possible solutions is after the part inserted in desired configuration, design table is deactivated (human error can ocurr if one forgets)


What I've tried to do:
1-Create a Parameter in CATIA: 3D_Design_rev=A
2-Create two separate Excell design tables
3-In one of the Excell, there is two rows, Part_Ref, and Excell_Design_rev
4-In the other Excell, there is all the dimensions necessary for the design
5-Added a rule in CATIA, to check, if 3D_Design_rev <> Excell_Design_rev, then the design table with dimensions would deactivate

This works when you edit the rule, but when you close the part and CATIA, and open again, it won't work, one needs to edit the rule (not necessary to modify, just enter it, and exit), and then it's working again.

Any suggestions?

 

[Little Cthulhu]

Hi.

Ypu should add part in a catalog as fully resolved. This will generate multiple independent CATParts, one for each configuratiom row.
Check CATIA documentation about how to do it.

 

[rjl007]

Hello,

Thanks for your answer, that may be an option, but during design one may want to change configuration, and in this way it means to replace the part by a new one, if you were still able to modify the configuration it's much faster

 

[rjl007]

Just had an idea that will do the trick, not a "elegant" one but it should work:
Everytime the catalog parts suffers an update, the corresponding Excell file should be renamed to something like rev_A, rev_B, etc...
This way when an old product is open and updated, it will not recognize the Excell file and part remains with same dimensions.

 

[Little Cthulhu]

I believe this will lead to update errors and this ia not what you want to deal with in a long time perspective.
Your desire to have the flexibility of dynamically changing parts is understandable, but there's no way to have part both dynamic and yet isolated. Those are two opposite requirements that don't live together. It may be a good idea to reconsider why on earth your configuration can change. Maybe such part families should be treated as completely independent ones?

I suggest you stick with one scenario and suffer from it's downsides, BUT gain greatly in administering your parts in a long term. The more parts you'll have, the more profit you'll get from keeping your catalog and parts "clean". So the final solution is more of the organizational one, not technical.