Hello.
Deriving components is a good thing. Unfortunately, there is no way (at least that I know of) to derive the material fields from the source object. It's a little more complex when deriving sheet metal objects. In that situation, you not only cannot derive the material, but you also cannot derive the sheet metal styles; but you can the thickness.
Does anyone have a solution, either something I am missing through the "derivie component" command, or an iLogic rule that would work?
Thanks!
Unfortunately, this is not supported directly. The appearance style is copied/derived only when it is used by an object which is derived. For example if you derive a solid body which uses some styles then the derive command will derive the given styles too.
Generally the derive command is used to drive a model, if you change the source component the derived side is updated. It can be tricky if the target document contains more derived parts - they can overwrite the styles. Do you need to derive only the active style of the part? It would be nice to have some workflow when this is needed.
Thanks,
Csaba
There was a long discussion in the past - it is tricky to derive material styles :-(. The problem is that a document can contain several derived parts. Even more the target document can contain material with the same name. In such case we could either overwrite the material or create a new material e.g. Gold_01. Material has to be consistent within a design environment per customer. Gold, Aluminum etc. materials have to be consistent across parts within the company.
As a workaround I recommend to save the given style to the global library and then use it in the new part. By this you can use the style without deriving it and it is consistent accross parts. Is this workflow acceptable for you, or do you have other workflows where the style derive is required?
Thanks, Csaba