Improvements to bom-related endpoints ensure that:
When POST /api/bom/v2/item-versions/{itemVersionId}/file-versions-bulk is used to attach new versions of a primary file, each subsequent version of this file is always attached as primary even if the request does not indicate that the new version is primary.
Primary status along with the version of the file ensures that the latest version of the file is always available and associated with the item when it is Released - solidifying data integrity in downstream processes.
The POST /api/bom/v3/file-versions/{FileVersionID}/children-bulk endpoint now assigns parent-child relationship for a drawing and its parts and assemblies, where the drawing is the parent and the parts or assemblies are the children. If the drawing is a child of the assembly a 400-http error is returned. This ensures that the cBOM link between drawing and part/assembly is correct to avoid an unending cBOM reference loop.