I want to save an assembly that has multiple configurations and parts with multiple configurations in a pack in go fasion were it only save the it in the configuration its in and saves the parts in the configuration there in. is this possible.
Not that I'm aware of, but that's a great idea! I frequently use multiple configurations, but usually require them when I Pack and Go. I'd say do a Copy As of each part with multi configs to make a new top level assy with only one configuration, but that could be very tedious depending on how many subassembly and assembly part configurations you have.
What do you plan to do with it aftewards? Can you change the format and get away with it? (i.e. save it as a different format and import it again so it becomes an orphan)
I'm moving a prototype design (with multiple senerios configured into it) into a contract in which the only design i need is the sold contract design (configuration)
I'd be inclined to try saving it as a parasolid and opening that and running feature recognition. From my experience it seems like the best chance of having the feature tree available (not just dummy solids), but when you save it to parasolid it only saves the active configuration (IIRC).
If you are okay with losing the feature tree (i.e. you never want to change this assembly or don't want the customer to be able to modify it) you can skip the feature recognition step.
Joe, since you're going from development to production, maybe you should take your assembly and save it under a different name. Then go through it and delete the suppressed components and unused configurations.
If this is a technical data package for a contract, it becomes pretty crucial that it not be changed inadvertantly and as such, managing it under a different number is the way to achieve that seperation.
that is what i have been doing it i have been resaving all the parts and ass'ys and deleted out all the configurations manually
Maybe this is what you mean, but instead of resaving all the parts you could save the assembly under a different name and delete all un-wanted parts and configurations, as John suggested, then Pack and Go this assembly.
Retrieving data ...