Like most modern manufacturing companies, we try our best to standarise parts/assemblies so we can use these in multiple projects, spare parts, assemblies, sub-assemblies to keep inventory, storage space and stock levels down to avoid un-necessary costs to the business. We would really like to see a function where we can run a workflow to change all assemblies where-used at once. It is a massive inconvenience to have to run a workflow on every project that a part or assembly is linked too, ideally we would just check a box in the where used list to update all the linked projects and assemblies at once.    If there is a way to do this already could you please point me in the direction of the help pages.   Thanks  Show More

Hi,    In the "Upchain attributes codes" exists the following: Created by Approved by Drawn by Checked by   In Wbx case, we have the intention of making a commun 3steps release workflow: Drawn by (or created by)-> Checked by-> Approved by   So far, no problem, but in case to keep a revision history we loose the attributed of checked by.   So the Drawn by (created by) -> links to Revised by 1 (2 and 3) Checked by -> no link Approved by -> Approved by 1 (2 and 3)   Would be great to have in the Revision History table the Checked by-> linking to Checked by 1 (2 and 3)   Thanks for the attention, Tiago Araujo Show More

Hey, when uploading, adding, changing files in Upchain. The red text used in the check-in window is very hard to read. A better contrasting colour would be a lot easier on the eyes and makes checking through large assemblies a lot easier. Show More

Problem: When importing a new eCAD electrical package that includes an Excel spreadsheet, Upchain automatically deletes and replaces all BOM items under that package, which results in two issues. First, if the package BOM has an older version of an item and the spreadsheet is reuploaded, Upchain will delete the item and re-import it, automatically upgrading it to the latest version. This causes unintended version changes, even if you don’t want the item to be updated. The second issue is that if an item is marked as REF ONLY in Upchain or if project-specific metadata is modified outside the spreadsheet, those changes don’t carry over. Upchain essentially grabs a new, "blank" copy of the item, ignoring any customizations made to that package’s BOM.   Fix: Instead of Upchain deleting all items and replacing them with the same ones, Upchain should process each item in the spreadsheet individually. It should first check if the item already exists in the BOM under the electrical package. If the item is found, Upchain should keep it and compare any differences (e.g., QTY, Notes, Item Type, etc.) between the BOM version and the version in the Excel spreadsheet. The item should only be updated to the latest version if the version change is in the spreadsheet. If an item is found in the BOM but not in the spreadsheet, Upchain should remove it from the BOM. Conversely, if an item appears in the spreadsheet but not in the BOM, Upchain should add the newest version of that item to the BOM. Show More

https://www.youtube.com/watch?v=Au4eTNBnYZM The platform OpenBOM manage very well the cutlist of solidworks.  It´s very important for all solidworks users have the possibility of make a detailed cut list from a weldment part. Show More