---
title: "Andrew B (@abowden) | Hashnode"
description: "IT Deployment Manager. Read the latest articles by Andrew B on Hashnode."
url: "https://hashnode.com/@abowden"
---
@abowden
# Andrew B
@abowden · Australia · Joined March 2022
IT Deployment Manager
## Comments
[Hi Danny, are you trying to determine the BOM using the fileassociation table? See my above answer to Joshi about fetching the BOM data from the FileIteration table in the BOMBlob field. Processing the XML data from that was the only reliable way I found to get the data matching up against what Inventor showed (You'll likely need to look at the XRefId for the child record) This is an example of the Components section of the XML from an assembly: This translates to: -BOM item #2 (CompId) -ChildID (FileIteration.FileIterationId from DB) of 868932](https://hashnode.com/posts/data-migrationextraction-from-autodesk-vault/6242a0a5db84f8c50fa5ba53/comment/642ab53183927af52f35c11a#reply-643f911163692ff13574951c)
Reply · Article · Apr 19, 2023 · [Data Migration/Extraction from Autodesk Vault](https://hashnode.com/posts/data-migrationextraction-from-autodesk-vault/6242a0a5db84f8c50fa5ba53)
[Hi there, we had cases where a component of an assembly wasn't available in the new Windchill location but not for any renamed ones showing an issue that I'm aware of. We had to ensure that the search paths in the Inventor project were set to the Windchill Commonspace/Project folder so that it would line up This is for cases where the raw ipt file names were still kept the same, I think you would have to open the assembly in Inventor and correct the missing items one by one as the CAD BOM is stored inside of the IAM file](https://hashnode.com/posts/data-migrationextraction-from-autodesk-vault/6242a0a5db84f8c50fa5ba53/comment/63bd713955c009e4115858ba#reply-643f901d63692ff1357494e7)
Reply · Article · Apr 19, 2023 · [Data Migration/Extraction from Autodesk Vault](https://hashnode.com/posts/data-migrationextraction-from-autodesk-vault/6242a0a5db84f8c50fa5ba53)
[Hi there, here are my answers to the questions: 1) Unfortunately our team didn't make use of family tables, so I'm unsure where it might be stored. One method I've used for something similar is to dump the entire DB to an SQL file and do a text search for a sample value that you're expecting and try to find which table/column it's located in 2) We filtered down the file counts to only include ipt, dwg and iam as we had as those were the only file types that were needed to migrate. There was a lot of other miscellaneous files (png, log, pdf) that weren't needed 3) The main use of the CTE was for us to determine the depth of the folders (which was needed by the destination system team and also aided in sorting) by counting the parent/child links. It could be done by counting the "/" character in the query but having the CTE didn't make a major performance difference: -6 seconds to execute with the CTE -3 seconds to execute without](https://hashnode.com/posts/data-migrationextraction-from-autodesk-vault/6242a0a5db84f8c50fa5ba53/comment/63a44fe53916c9c9a801cf29#reply-63a4f504490dd1c9cd9c3c55)
Reply · Article · Dec 23, 2022 · [Data Migration/Extraction from Autodesk Vault](https://hashnode.com/posts/data-migrationextraction-from-autodesk-vault/6242a0a5db84f8c50fa5ba53)
[Hi there, I found that the BOM data is stored in the FileIteration table in the BOMBlob field. It's encoded as XML so you'll need a way to expand and link that data. This is an example of the Components section of the XML from an assembly: This translates to: -BOM item #2 (CompId) -ChildID (FileIteration.FileIterationId from DB) of 868932](https://hashnode.com/posts/data-migrationextraction-from-autodesk-vault/6242a0a5db84f8c50fa5ba53/comment/636258f91a6e287db7286b04#reply-6369c946a1ce83db6fb7209a)
Reply · Article · Nov 8, 2022 · [Data Migration/Extraction from Autodesk Vault](https://hashnode.com/posts/data-migrationextraction-from-autodesk-vault/6242a0a5db84f8c50fa5ba53)