When using the following API for data migration - /api/bom/v1/file-versions - it does not work properly when a single DWG file is being added to the item. The API is placing the DWG file in the drawing section of the item. Later when a customer tries to work with the DWG file, the CAD plugin cannot work with the file in this location. It errors b/c it expects to find/work with it in the cBOM section. Furthermore, support states, "we agree that it is a best practice that the API should behave the same as the UI. In this instance, regrettably it does not." Also that "there is a workaround to get the dwg files correctly checked in, by using the AutoCAD(Generic) plugin." Reference CaseNo:21921525 This API needs fix. The workaround suggested by support is not a proper workaround at all. This API is one of many that are used in succession during a migration - to create new items with metadata (common + custom attributes), categorization info, supplier info, upload CAD and related documents, BOM structure, etc. This is done programmatically - in bulk - by the thousands. Using the CAD plugin to manage this after the fact is not practical. Either the API should be updated to place a singular DWG file in cBOM area of the item, or the CAD plugin should be updated to work with that DWG file that the API places in the drawing area.
Show More