Locking Components to avoid losing attribute data

I work for a cabinet company and we’re developing a library of components to create 3D models of our layouts. I have standard components that can be drag n dropped into the models. It’s very quick to use. The components have data embedded info in them that we use to generate quotes and production lists. Here’s my issue: If a component is brought into a model and exploded, the data is lost and the item will not be included in our quote. This has potential to be a very expensive problem. I’m hoping someone out there has a solution. Thank you for taking the time to help.

Unfortunately what you described is very similar to, “If a component is brought into a model, placed but then it’s deleted, its data is lost !”
The user exploding an instance is not different from the user choosing to delete it…
The data is lost.

Why would a user want to explode [or delete] an instance - and then still expect it to be reported on ?

I think it’s an “education-of-your-users” matter…

1 Like

That’s what I thought, but I wanted to reach out to see if there was a way to do it. I have trained on it, but I’m worried that it could happen by accident. Just looking for a failsafe solution.