topic Re: Re-Write FileBom with "SetBomByFileId" throws error code "1145" in Vault Customization Forum

Re-Write FileBom with "SetBomByFileId" throws error code "1145"

Patrick.Gruber — Tue, 08 Jan 2019 16:12:31 GMT

Hi community,

I have used SetBomByFileId to re-write the FileBom.

The new FileBom is the same like the old one but I have removed just 1 component from the CompArray.

The function "SetBomByFileId" throws the error code "1145", but I can nowhere locate the appropriate error message for this code. Where can I find it?

Real Problem

GetBOMByFileId returns Components with XRefIds which do not exist in Vault anymore.

After running the Autodesk Job autodesk.vault.extractbom.inventor on the affected Assembly doesn't write a new FileBom like mentioned in this blog post

The API documentation for SetBomByFileId (which the job should use) says "File cannot have a BOM already associated with it."

Does this mean the job fixes the FileBom only in case there is NO bom at all?

Is there a better way in my case where only some XRefIds are wrong without making a check-in with Inventor?

Had somebody else a similar case? Any help is very appreciated thanks!

Re: Re-Write FileBom with "SetBomByFileId" throws error code "114

Markus.Koechl — Tue, 08 Jan 2019 17:53:21 GMT

Hi Patrick,

I'd like to clarify the base concept first, even I can't quickly all your question details.

The Job "Extract Item Data" (User command in Vault Professional, Actions->Extract Item Data) runs only if no BOM data exists for the component. It is NOT applicable to update/correct existing BOM data. The only supported path to update existing BOM data in Vault Professional is checking in the file using Inventor.

Re: Re-Write FileBom with "SetBomByFileId" throws error code "1145"

ThomasRambach — Wed, 26 Apr 2023 17:51:51 GMT

@Markus.Koechl In all the example code I've seen for checking in a file through the API it uses:

public override File CheckinUploadedFile( System.long fileMasterId, System.string comment, System.bool keepCheckedOut, System.DateTime lastWrite, FileAssocParam[] associations, BOM bom, System.bool copyBom, System.string newFileName, FileClassification fileClassification, System.bool hidden, ByteArray uploadticket )

Where the BOM is set to NULL and copyBom is set to True. This works well. However, we have part of our code instances where the Inventor BOMStructure is updated from Normal to Purchased as part of the Job Processor job. So, we've discovered that now that we're utilizing Items, some of the BOMS do not match what the file really is set to.

My question is, I haven't seen any examples of code where when you check-in a file, how do you read in the latest BOM information from the file that was uploaded? Is there a way to manipulate the BOMStructure value for a component in a BOM and then associate the manipulated BOM to the file being uploaded?

Re: Re-Write FileBom with "SetBomByFileId" throws error code "1145"

Markus.Koechl — Thu, 27 Apr 2023 22:48:10 GMT

Hi @ThomasRambach,

creating/updating the BOM object is reserved for the Inventor-Vault Addin. The Add-In does not provide an API that we could leverage.

Re: Re-Write FileBom with "SetBomByFileId" throws error code "1145"

ThomasRambach — Fri, 28 Apr 2023 10:51:30 GMT

@Markus.Koechl What's strange is you can read the info but not change it. Do you think this is something the API may provide in the future?

// Get the File BOM ACW.BOM fBOM = DocSrvc.GetBOMByFileId(fFileID); // Read the parent assembly BOM Structure ACW.BOMStructureEnum fCompBOMStruct = fBOM.CompArray[0].BOMStruct; // I can even change the assembly BOM structure fBOM.CompArray[0].BOMStruct = ACW.BOMStructureEnum.Purchased; // I just can't reassociate the modified BOM back to the file

Re: Re-Write FileBom with "SetBomByFileId" throws error code "1145"

ThomasRambach — Tue, 02 May 2023 13:18:58 GMT

I actually was able to get this to work. So, you actually can manipulate the Vault underlying BOM using the API.