Item Not Assigned to Skeletal Parent (Master Sketch .ipt) File

[dpeters3]

We use skeletal modeling where what we call a "master sketch" .ipt file has all the defining sketch and work geometry for many parts in an assembly.  It is arguably the most important file in the project!

When we assign item to the resulting assembly, all parts in the assembly get items assigned also.  But the "master sketch" file does NOT.  Why not?  Every part in the assembly uses the "master sketch" file.  If I change the state of the assembly to released, I want the "master sketch" file to be released also, but I am surprised to see that it has not even been assigned an item.

If I separately assign an item to the "master sketch" .ipt, it does not show anything in the "where used" tab.  How can this be?

[Radwan-Almsora]

When you Assign an Item in Autodesk Vault, it generates Items based on the Bill of Materials (BOM) extracted from the CAD model.

Because your master sketch is a reference file used to drive geometry, it sits outside the standard assembly structure, so it is not automatically assigned an item or linked in the Where-Used tab.

To resolve your issue, you can enter here. 

File has no Item Data" error when assigning Item in Vault Professional

Associated drawing files cannot be assigned to items. Associate the drawing to the part or assembly ...

Did you find this post helpful? If it gave you one or more solutions,

don't forget to click the Accept Solution button and leave a < like !

[dpeters3]

OK I can understand that the master sketch file is not a participant in the BOM, so that is why it is not being assigned an item.

The master sketch is most certainly not "a reference file".  It is responsible for the entire design.  In the file explorer view in vault, all the daughter files made using the master sketch show it in the "uses" view.  And all the daughter files show in the "where used" view for the master sketch.  So Vault knows about these file links.  Surprised that Items ignore them.  This seems like a glaring omission in the design of the software.  But if that's the way it is, at least I know it now.