Upchain should provide an additional “Canceled” status for Tasks, allowing discontinued or terminated tasks to be properly identified within the project lifecycle. This enhancement would improve operational clarity and more accurately reflect real-world project execution.   Justification: Currently, Upchain offers the following Task statuses: Draft, Pending, In Progress, and Completed. However, in real project scenarios, tasks are often canceled due to scope changes, strategic decisions, or external dependencies. The absence of a dedicated Canceled status forces users to mark tasks as Completed even when they were not executed, which compromises traceability, reporting accuracy, and overall data integrity.   By introducing a Canceled status, Upchain can: Improve the accuracy of Task tracking and reporting. Better reflect the actual state of project activities. Prevent the improper completion of tasks that were never executed. Increase transparency and governance across project workflows. Suggested Implementation: Add Canceled as a standard Task status with behavior distinct from Completed, ensuring that canceled tasks are excluded from completion metrics, reports, and performance indicators. Optionally, allow the Canceled status to be configurable through administrative settings or workflows, including audit logging to support traceability and compliance requirements. Show More

It would be helpful to have a toggle to allow viewers to see unreleased product structure items.   We want to use product structure items as folders (as recommended by Upchain tech support), but in order for it to work, they have to stay in development. This means that our viewers can't see the projects, as they can only see the latest released.   Having a toggle means other companies that use product structure items differently can continue to do so without viewers seeing them. Show More

Hi, We currently manage multiple products within the same series, and to make it easier to visualise in the BOM window, we’ve set up a separate project for each model. This setup is primarily due to the different accessories, spare parts, packaging, and documentation that are specific to each model. However, many of our items are common across the series, and having them split across multiple projects is becoming increasingly difficult to manage. It creates unnecessary validation steps and makes updates more time-consuming and prone to error. If we had the ability to create a folder structure within the BOM tab, allowing us to group model-specific BOMs under a single parent project, it would significantly improve readability, simplify updates, and reduce administrative overhead.   Let me know if this is something that could be considered.   Thanks  Aaron Show More

Use Case. When clicking on a part in SolidWorks, the part is highlighted and displayed in the feature tree. In the cBom plug-in, the selected part is not selected and must be searched for by scrolling. Since the part numbers are not identical in SolidWorks and Upchain PlugIn, searching for a part is very tedious Job. having large Assemblies with big cBOM trees this is a time consuming Job and  prone to errors. currently only the Item view is changed and highlighted but not the position in the cBOM. this is needed to find in what cBOM/eBOM position the item is located and to better work on the Assembly. the same goes for. selecting in cBOM.  If a part is clicked in the cBom plug-in, it is not displayed and selected in the SolidWorks feature tree. this is needed to easier work on the Cad File and edit it in context. this feature would also help when editing multiple items in the cBOM. the user can click on the checked out item and it must be highlighted and selected in the feature tree. Show More

A SOLIDWORKS drawing generated during initial Item creation and subsequent check-ins retains the document font, PNG images, and all colors; however, when an item is released, its PDF translation loses the document font (converting to a new font), PNGs in the drawing convert into a black box, and all colors are lost. This can negatively impact my ability to communicate specifications to my suppliers, to the point that these translations are unusable. This translation automation is one of the main selling points of Upchain, but these formatting problems kill that point. I would like to suggest that in a future update, the PDF translations retain all of the font, image, and also document color formatting from the original SLDDRW file. Show More

We use project documents, because of the issue with item documents incrementing as described in this post. However, when a document is linked to an item that document is not included in bulk export. For ECOs and programmatic BOM releases, it is very time consuming to individually download each document. There is also a large element of risk that the user will need to check every BOM item for a linked document. In a BOM that is over 3000 lines, this is unrealistic for us to brute force our way through.  Show More

We use item documents to support our solidworks drawings in the following cases.  Purchased assembly manufacturer owns the CAD & drawing of the assembly. Pneumatic/Cable Harnesses that are drawn in lucid chart and due to existing issue of PNGs being black after translation we cannot paste into solidworks drawing so we attach a PDF from lucid chart and refer to the document number in the solidworks drawing.  Our current workflow Put document in “general documents” section of item Write document number in SolidWorks drawing w/ the anticipated rev # change (ex: if currently at A → B) Publish document Release item   The problem w/ the current method is that the document # is not maintained throughout our process. Document number changes when the document is published ahead of the item’s release and then again when the item is released. Even if the document isn’t published ahead of the item’s release, the doc # still changes at item release.   I am requesting that the document number does not increment when an item is released.  Show More

Use Case. adding the following to the Bulk Export function Grid. the columns “Spare part” and “PC/WP” to the Grid. the values must be extracted from the eBOM that is in the Project where the Bulk Export is started. This would simplify the export of data for customers who only need spare and wear parts and save a lot of time. this should be a simple enhancement that added great value to users. Show More

Create a Tenant property that allows users to Check in CAD if item is in a CR and in Development State when properties drawing.create.pdf is also on.    Currently it is not possible to check in CAD when drawing.create.pdf is on and the item is in CR, even though the item is in development state.   It makes no sense to me that updating a drawing is allowed but a translation of that drawing is not allowed. My only solution at the moment is to cancel CR or give all CAD users administration privileges.   Having a tenant property or a toggle in the drawing.create.pdf setting will fix this issue.   Related to limitation: https://help.autodesk.com/view/UPCHN/ENU/?caas=caas/sfdcarticles/sfdcarticles/Operation-Blocked-These-files-cannot-be-checked-in-because-they-are-currently-part-of-a-Change-Request-message-blocks-check-in-of-item-in-Upchain.html   Show More

As user creates an item with an item type Manufactured Item. The user fills all values, including the dropdown Picklist Manufacturer. During development the user decided that the item must be a manufacutred item. The values that the user has added includeing Manufacturer, Manufacturer item number must be removed by him. The user must have the possibility to remove this attributes from the item. This is currently possible for attributes that the user added manually but not for dropdown lists(picklist). The user must have the possibility to clear a picklist. This is also important in case the user has made a mistake and he wants to correct it themselves. Or if requirement change during development, etc. A proper system must allow the user to make such modification. The modification must be captured by the DB history functionality. Show More

Currently the where Used eBOM Tab is showing the eBOM As Saved. the where Used Project Tab the eBOM in Effective Date. this is confusing for users. Both Views must be sync. both Views must show the same results. the eBOM Tab should show the where Used Buttom Up. the Project Tab should show the Where Used Top Down.   Use Case. reducing confusion and enhancing readability.    Show More

Please add search and filter for items within the CN window.    User Case. when working with large assembly CN's. Navigating and scrolling between all Requisitioned items to find one specific item is extremely difficult and time consuming, sometimes resulting in errors and typos. A search box  or just "Strg + F" will help in finding the items more efficiently resulting in more user friendly CNs.  another possibility would be to add filter capability to the item number row. where the user can write the Item number and the CN grid would only show the filtered items.   Show More

An item can be used multiple times within single project and have different tree paths.    User do need to find items under specific tree path or end items depending on multiple use cases.    Where used tab shows bottom up tree path on where item was used. however when clicked on item it always opens the tree path which is shortest. (If same item X is nested 5 parents down and same item X is nested 2 parents down, when clicked on item in quick search or where used tab, it opens eBOM with 2 parents.)   Some items get used more than 50 times and its very difficult for users to find the tree path from top down approach always.  Show More

the advanced search returns a large amount of data. this is sometimes confusing. add standard filters to the results table. This should filter the results based on selected criteria. Latest released newest version Status "Released" and "Released External" the filters should be added as buttons that the user can activate and deactivate after the search result is displayed. this should not affect the search query and only change the presentation of the results. Show More

Upchain should provide Admins with the ability to define which user roles are permitted to add or remove users from a Project Team. This enhancement would allow for more granular control over team composition and access rights, tailored to the unique needs of each project.   Rationale: Currently, any user with a Professional license—even if assigned a Viewer role within a project—can add other users to the Project Team. This behavior undermines permission integrity and poses a risk in environments requiring strict access controls, such as those subject to SOX Compliance or other external audits. By enabling Admins to configure role-based permissions for team management, Upchain can: Strengthen internal governance and security. Prevent unauthorized user additions. Align with compliance requirements and audit expectations. Support diverse project structures with varying access needs. Suggested Implementation: Introduce a setting under Admin controls to specify which roles (e.g., Project Manager, Lead Designer etc.) can manage team membership. Provide additional logs for user additions/removals to Project teams for traceability. Show More

The default automatic selection in the CN should select any item where the difference between the P and H quantity is not equal to 0, regardless of whether it is positive or negative. Currently, the behavior of Upchain is not consistent. When a CN is created, all items with a positive difference between P and H quantity are automatically selected. However, items that have been reduced in quantity and have a negative difference between P and H quantity are not selected, so they are usually forgotten. these leads to errors in Large CNs. further a visual dynamic marking, with a different color(pref. RED) for the row should be added if P Qty - H Qty is not equal to R Qty + Move Qty. Show More

The Cost attribute should be hidden for the 'Restricted Role' in Upchain. This role is designated for Contractors and Customers, who should not have visibility to the Cost field. If necessary, this can be controlled via a Feature flag or Tenant Property Show More

Exporting a BOM report has a limit of 3,000 items.  Trying to create to report on any item greater than 3,000 items generates an error and no report.  Please increase the limit to 50,000 items so a large multiple assembly report can be generated.   While the quantity requested might seem excessive, large assemblies often exceed the current 3,000 item limit.   Show More

Custome CR and CN-Reports should be added to the Workflow Primitive. this allows the organisation to setup Automatic CR or/and CN Report Creating mechanisms in the Workflow.  when created the Report must be attached to the CR or CN as a General Document. the attachment should be allowed even if the Organisation wants to Print the Report. the Report must allow PDF, Office or XML formats to be created and attached to the CR or CN-Workflow.   the Use Case. Eliminate the E-Mails and links that are sent when a user is creating a Custom Report. Garantie: that all Project Memelers have access to the Report without the need to send copies with E-Mail. Version control the content of the Report.  Singel source of information in the PLM system.     Show More