Announcements
Attention for Customers without Multi-Factor Authentication or Single Sign-On - OTP Verification rolls out April 2025. Read all about it here.

Thanks WCrihfield, you have provided me with a lot of valuable information, you don't want to know how happy I am with this.

 

I conclude that I have to be very careful with using Parent relations to make certain subdivisions or not, thanks for this insight.
It's also good to see this confirmed, sometimes I doubt whether I'm observing it correctly.
For example, we use a Phantom assembly with Weldments to get all underlying sub-weldment assemblies in a physical folder.
I determined on the basis of the parent relation whether it had to do with such a folder.
I'm going to use a custom property for that that controls that.
Much more flexible too.

 

In response to your question 'I assume you are talking about a BrowserFolder in the model BrowserPane?':
No, I mean a physical Directory.
I think I have enough information to fill that in.
Krieg already advised me to work from the BOMView.
That's what I'm going for for now.

 

With regard to Inseparable assemblies, to date we have not worked there with the argument that parts no longer appear on a total Parts Only list.
This from the point of view/demand from a supplier who wants an overview of all parts to be delivered.
When welding assemblies are Inseparable, in my opinion a simple Parts Only list will suffice to collect the other parts.
How do you view that?