Hello
I have a higher-level assembly with a child assembly. When I click on a part that is included in the child assembly, delete it (delete/delete), the part is removed from the child assembly.
What I would like is for the whole child assembly to be erased and not just the part.
Can we set it to default?
Here is a screenshot
Thank you and bon appétit
Hello
No configuration to my knowledge, you have to delete the parent by clicking on it in the tree or with a right-click in the 3D, select the assembly, then delete it.
Edit it's a new feature of SW 2013, and there is no solution, an SPR (improvement request) has been created at SolidWorks under the reference:SPR 697503
you talk about a children's assembly but you show on your screenshot
a pieceto select who she has no children if I'm not mistaken
you can delete a complete subassembly
by clicking on it and deleting and checking the Remove Children
@+ ;-)
The problem is that a person can erase a part in a child assembly without realizing it.
While by deleting the child assembly, in its entirety, it is much more visible but above all does not modify the child assembly ;o).
@gt22: On the capture, part 4401-0034 is in child assembly CI 2161. I am working on the CI assembly - to be inserted into ASM. By clicking on component 4401-0034 and clearing it (delete/Delete), I modify the CI 2161 assembly.
If I understand correctly, you want to be able to remove
your support and the relay that is on it
In this case I think the best is to create relay sub-assemblies with support
when you delete a relay the support will be removed
nothing will prevent you from changing the relay on the said support if necessary by changing the name
Did I understand your problem?
@+ ;-)
A PDM allows you to have some files in read-only, but without it, no protection except when closing, SolidWorks now offers a list to choose the files to save!
This is a known issue at SolidWorks that will be fixed in version 2015:
https://customerportal.solidworks.com/eservice_enu/start.swe?SWECmd=InvokeMethod&SWEMethod=GotoRecord&SWEService=SWGotoRecord&ViewName=SW+All+Defects+List+customerportal+-+Search&BusObject=Product+Defect&BusComp=Product+Defect&Id=1-1MTL1LN&SRN=
Personally, and to follow the idea of @Lucas, I put my libraries of commercial parts in read-only mode (without PDM).
I don't know if this would be applicable for you?
It doesn't answer the basic question (delete the subset instead of the part), but it avoids making mistakes (no unintentional registration of the subset with one less part).
Yes, it depends on the architecture, but if all your standard subsets are in a folder (or tree), then it's easy to give write access only to certain users by the domain controller.
When you click on a part, it should select the assembly and not the part.
There was a question about this not long ago where someone was looking for the reverse functioning.
This is an option of the feature manager "scroll object in view"
I don't know if it just unrolls the tree and the part is selected no matter what...
This may be an avenue to explore.
Thank you for your answers.
@gt22: the primary goal is that you can't delete a PRT from a child assembly without realizing it.
On older versions, deleting a PRT in a child assembly would cause the entire assembly to disappear. It was very visible ;o)
@ s.leitao
Do you have two drawings of two different versions and don't know what's different? Come and discover two tools that will help you on a daily basis. The first is Design Checker, which is a tool for checking your drawings. Scoring standards, cheated dimensions, correct formats, etc. it's like a corrector in Word but for drawings. Also, Draw Compare is another tool that will allow you to find the differences between two drawings.
See this tutorial
http://www.lynkoa.com/tutos/3d/design-checker-et-draw-compare
__________________________________________________________________________
Thank you for your answers.
@gt22: the primary goal is that you can't delete a PRT from a child assembly without realizing it.
On older versions, deleting a PRT in a child assembly would cause the entire assembly to disappear. It was very visible ;o)
Why once the sub-assembly is done controlled and accepted
Do not save it in part with its own ref
which would be the same as removing a part in this sub-assembly to remove it completely
@+ ;-)