Hello Community,
We are migrating engineering part information into an existing implementation and have a need to create separate engineering part structures and hierarchies that utilize the same components. For instance, Parts A and B may both utilize Part C as a child component, but the Part B hierarchy would have further children parts that Part A would not have.
What we do not want is when looking at the structure and hierarchy for Part A, to see the child components related to Part B. Further, we do not want modifications made to a parent/child to affect the structure of another part.
Is this supported in Apps10, and if so, is there a recommended practice to implement this? Looking at the engineering part structure data, it seems like this may be possible by delineating a structure ID, but I can’t find how to set that on the front end or through the migration documentation.