OK. I have part with configuration "Base" I want to have three configurations based on the features in "Base". I add configurations "A", "B" and "C". So I create "Base" and then add A, B and C. The problem is that when I do this all the features I add in A show up in it's siblings (B/C) and vice versa. It is tedius to add features and then have to go to all the previously existing configurations that are siblings and supress/hide them.
What an I doing wrong???
Go to the properties of each config and check the box to Suppress features. This "locks the gate" on that config and any features added to the file are suppressed in that config.
You can also go to http://www.kcswug.com/programs/macros/ and grab the file SuppressFeaturesLoop.swp. This is a macro that goes through all the configs and checks or unchecks that box. It also works basically the same on an assy for features and mates.
WT
Wayne,
How does that website work. I'm trying to get the SuppressFeaturesLoop macro. When I select it and try to save in comes in as an HTML file.
Regards,
Hmm, that is a bit interesting. But I just tried the save and then changed the ext back to swp and it worked fine. Give that a try.
WT
Wayne
Changing the extention to .swp when saving worked.
The macro works well also
Thanks
Now, I also should have added that if your configs are derived, then the situation will be a bit different, but it didn't sound like they were.
WT
Does your configuration manager look like the one lableled normal or derived?
If it is derived, the behavior you're describing is the purpose of derived configs.
If it is normal, you can right click on each config, and hit the suppress new features button towards the bottom.
That's a bad family tree, man!
Seriously, I've never got derived configs to do what I want either. Design tables and normal configs are the way for me.
derived configurations start off as "linked" - all changes propogate to all of the children and parent configs. this can be over-rode on a case by case basis. ie each dimension + feature you want to be different. I personnally like using "configure feature" and "configure dimension" for this.
Jeremy
General statement...
Having any configuration that can change it's parent is hosed. In my humble opinion having any child configuration that can change it's siblings is hosed. Using "configure feature" is tedius but worked.
derived configs have their uses- though they are limited. I usually only use them when I want to use the "tree-like" structure it gives the config list to organize the configs.
Jeremy
PS - the one way control you are looking for almost sounds like "derived parts" which are often used for castings or molded parts that get secondary operations - holes added or tapped, etc.
I agree, this shouldn't be happening. If it is then SW needs to be aware of it.
Eric,
In a derived configuration, you have the choice under Feature Properties to "Link to Parent Configuration" available as a choice for the suppression state, along with the normal "This Configuration", "All Configurations", "Specify Configuration(s)". When you are defining the feature you also have the same choices available, except the names are slightly different ("Link to parent" and "Specify configurations"). I find that this makes it a bit easier to handle the various possibilities. I don't need to open up the parent configuration to make a change that I want to propagate to all of the derived configurations.
Jerry Steiger
I have also been having problems with derived configurations not being linked to the parent. Jerry I have looked for the "Link To Parent" but the only one that I find on my machine is for the Bill of Material Options which has nothing to do with suppression state. Where is the choice located?
Dan Miel
SW 2009 SP4
Dan,
Open up one of the derived configurations of your part. Right click on a feature in the Feature Manager Tree. Select Feature Properties. You should have the choice "Link to Parent Configuration" next to the Suppressed check box. This choice won't show up in that feature if you are in a configuration that is not derived. Similarly, if you edit a feature like an Extrude, then the choice "Link to parent" shows up in the Feature Manager if you are in a derived configuration.
Jerry Steiger
If you are in a active derived configuration where you have just created feature 'Base',
Go to 'Base' feature>>Right click>>Feature properties>>Check Suppress with 'All configurations' option>>Hit 'Ok'>>again Go to 'Base' feature>>Right click>>Feature properties>>UnCheck Suppress with 'This configurations' option
This will keep the feature 'Base' unsupressed in the current configuration and suppressed in all other configurations irrespective of the fact that it is a normal configuration or a derived configuration.
And this method will help to save your time in case there are many number of configurations in your part or any of the other configuration structure, because you need not to go to each configuration any way.
Message was edited by: saurabh godbole
I have played with the "Supress Features" when a configuration is part of a family of derived configurations. As long as you have "Supress Features" selected on all the siblings then a feature on one configuration will be supressed on all the others. This seems no different than using multiple standard configurations. Frankly, I don't see any advantage to derived configurations at all...just confusion.
Question:
Is there any way to automatically supresss features added to a child configurations in its parent? In other words...when I add a feature to a child is there a way to automatically supress that feature in the parent? Using the "configure feature" on the right button menu is cumbersome, time consuming and confusing at best.
What I would expect is to be able to create a parent configuration and children configurations of that parent. Any feature added to the parent would be unsupressed and show up in the children. Any feature added to the children would be supressed automatically in the other siblings and supressed automatically in the parent.
derived configurations start off as "linked" - all changes propogate to all of the children and parent configs. this can be over-rode on a case by case basis. ie each dimension + feature you want to be different. I personnally like using "configure feature" and "configure dimension" for this.
Jeremy