Hello
I have a problem when I do the step of my final assembly, one of my sub-assemblies changes configuration by itself and also wraps what has changed, so my step is not at all in the right configuration. What can I do?
Hello
In which version? Do you manually export the step? Is it recurring/random or only with this s-set?
Happy to welcome you to the forum! 
I hope that we can help you solve some problems, but also that we can benefit from your knowledge and experience.
Kind regards
We will find you a solution to the question asked.
Hello
Thank you for helping me find the solution to my problem.
It's under SolidWorks 2022 and it's only under this subset but recurring all the same.
Happy with your welcome and yes if I can also share my experiences and my knowledge I would share them willingly.
Sincerely, JB
Hello
Simple and effective solution, delete unnecessary configurations, do your step and then close your ASM without saving to find the configurations you have deleted.
may the force be with you.
3 Likes
Hello
Variant of the @OBI_WAN solution: export the assembly in .prt (this one should be OK normally since we stay on native SW), then export the .prt in .step
1 Like
Hello
Thank you for this solution unfortunately my assembly still crashes
Hello
I would like to keep in . SLDASM because my end customer wants to be able to generate an assembly but it could be an alternative indeed.
Is it possible to share your s-assembly?
Maybe an unsupported character in the names, or a corrupted component!
Unfortunately I can't share it but I'll continue to dig (I still managed to do a step thanks to a lighter version where I only kept the carcass)
How does the OS behave when it changes configuration if you export this asm only?
If you put this asm in another asm, does it keep the same behavior?
If you rename the config that appears unexpectedly, does the problem persist?
At the PRT record level, if you export each of the OSs, does one or more of them crash?
Is there a correlation with the asm that changes configuration?
1 Like
The big problem is that it generates me by itself when converting envelope parts into a step and it changes a config for me.
Unfortunately I think you're going to have to do a lot (I imagine there are a number of parts in this OS) to figure out which component is causing the problem.
Are there any sub-SEs in this SE?
Make a config with all the components removed, activate the first one, do an export, it works, activate the second one, etc
Another solution, if there is no sub-SE:
integrate the SE into an ASM, decompose the SE, try to export the new ASM.
if it works, replace the SE with the new ASM