Hello Upchain Team, Could we add DXF format in the translation format. Customers and partners are requesting this file format due to the fact their subcontractors do not want to add any tools to convert DWG to DXF. Have a great day, -Bertrand     Show More

In our CR workflow, we use the CR WF System primitive "Break SW attributes" after items are updated to the 'Released' state. When the "Break SW attributes" primitive opens items that have Solidworks version mismatch between the Model and drawing files(eg. SW 2020 version for model and SW 2018 for drawing file), the task fails. At this point, we can't allow the designer to checkout items as they could accidently change the BOM. So instead we notify the user about the issue and ask him to fix it in the next release of the item. In most cases, users move on to different jobs and will forget to fix the SW future version issue.  If there was a Primitive available in workflow to identify such items, we can use it to notify the designers to fix it before it reaches the final stages of the workflow.  So the ask here is get such a workflow primitive that is capable of identifying a solidworks file version mismatch between the model and drawing files for an item.  Ideally this can be done by just looking at the file attributes of the items in the vault to compare the SW file version(without opening the file).  If that's not possible, this could also be achieved through an altered version of the 'Break SW Attribute" primitive where the files are opened in a GPS node to run the Break SW attributes task on the files, but doesn't upload the files at the end of the task. It will only return an error if it identifies files that cause the error or if it successful, it will proceed to the next step in workflow.  This way if CR gets stuck, user can checkout the necessary files, fix the version difference and continue with the workflow.  Show More

When we submit our drawings to governing bodies we only require the front drawing page of our parts. Currently, we use different software that takes our drawings, saves the front page, and can add a prefix or suffix to each drawing. The only problem is it is only setup to save the active sheet in the drawing and when we check-in with Upchain it always ends on the last page and saves it there.    It would be great if we could either have: Upchain to save back to front so it always saves the top sheet last Upchain offers the option to bulk export all the 1st sheets of a drawing document in parts/assemblies Show More

We occasionally have issues that go somewhat like this:  An item has a BOM qty of some number, say 6, in our overall assembly During an early stage of the design process, we release the AA revision and then do a partial requisition of qty 1 (out of the total 6) AA doesn't work as-is, so the design is modified to AB, which is then requisitioned fully  Later on, revision AC is made, I go to requisition and click Redistribute, but I see the Move qty is only 5 on that item, and I have no idea why because I wasn't directly involved in the earlier AA req or it was simply a long time ago. If this happens on a large assembly and the requisitioner isn't paying close attention, the issue could get missed entirely. IF someone catches the issue, then the fix is to send that req for 5 of the new rev through, wait for workflow completion, and then create another Change Notice and click redistribute, which only then will capture the last qty 1 of the part that was revised.    This currently seems like a design flaw in the system because it is very difficult to understand why a partial Move qty is showing up and catching it at all is completely dependent on the creator closely examining the qtys.    Ideally, there would be a way for a CN to all a simultaneous rev of all the requisitioned items. But at least if this scenario occurs, there should be some warning or obvious notification that the CN is not behaving as a user would expect and that to get a full requisition another CN will be needed.      Show More

Electrical items are imported into Upchain via XML import. XML file have spare flag details which is getting transferred to Upchain. We need same with REF only flag.  If an item is set as REF only in XML, item should be created in Upchain with REF only flag. If item already exists in electrical package eBOM, it should update the REF only flag as necessary.  Show More

Some times we use engineering changes and we find a mistake, then we need to edit the item inside. If this item is the last one on the engineering change, we need to completely delete the engineering change just to edit the item, and create a new one with another number.   This creates confusion as sometimes we have already shared internally the engineering change number which later was changed as we had to delete it to be able to edit the item. Show More

Enhance the Where Used CN tab and the Business Process CN Tabs with the Project Number. the Business case. User wants to search an exiting Items Change Notices. Opening the Business Process or where Used can result in a very Large number of CNs. if they want to search the Projects where this part was requisitioned they have to open each and ever CN individually. add the Project Number to which the CN belongs helps the user extremely. this Information is available in the System and needs to be presented in a column beside the CN number. screenshots of the a possible suggestion.   Show More

If an investigation request is created from a released item and a change is needed an engineer is expected to check out the item make the required change and check in the item. This puts the item in a development state. The engineer then wants to utilize the investigation request to create a change request and release the latest change made to the item. However, Upchain adds the older released version of the item to the change request not the latest version of the item in development. My request is to have Upchain add the latest version of items to a change request that has been created from an investigation request. Currently, this functionality only works with an item that started the investigation request in a development state. This idea is being added from support case 20353644. Show More

I would like to update the Item.Maturity status of ONLY the parent item in an assembly with multiple children. My use case is designating specific item versions as "obsolete" via Item.Maturity. In this case, I want to mark the parent "obsolete" not any children.   For example: Changing the maturity of 100363-AA-00.000 Toy Box. This Item is an assembly made up of 8 other Item, it’s a toy box with 8 different toys in it. I want to change the maturity of the 100393, the parent (toy box), but not any of the children. Perhaps I want to change the maturity status of 100363 to “Obsolete” but need to maintain all of the children as Prototype or Production. Show More

Hello to all Upchain support,   I have an open point because when we would like to create a new (end) item in a project, we have this following window that appears (picture named "Window for item creation"). As we can see, we have some stars like that " * " informing the user that fields are needed for the (end) item creation. My concern is regarding the "Description * : " field. Here it is marked as mandatory for the creation. After all field filled, (end) item is created. When I would like to modify the attributes of this new component, I am able to remove the "item description" added just before. I am able to remove the decritpion when the item is in development state. When I save the change added on the item, I press F5 in order to refresh the website. But the modification is not taken into account. So remove description is not possible But update it by keeping information in description is allowed. The question is : Why the description is mandatory for the item creation? Why we couldn't keep it as empty? For our usage, sometimes, no description are needed.   Thanks for your feedback, Best regards, Robin Février, products engineer at SFC-Solutions and Upchain Administrator Show More

Hello to all,   For some categorizations, we have attributes with bad naming. I would like to rename some of them. But even if I am tenant administrator, I am not able to do it by my own. I created a support ticket but Upchain support are not able to do it. In order to have more flexibility, it could be interesting to manage categorizations attriubutes as we want. A simple modification can be better than creating tickets and tickets. As it is only attribiutes names, there is no issue for the workflows or for anything else for the program. I guess. So thank you to take into account this request for the next update of the software.   Thanks   Robin Février, products engineer at SFC-Soltuions and Administrator Upchain Show More

Differences in the EBOM and CBOM just aren't clear enough. In the plugin you can see (red hi-lite) when there is a discrepancy but, especially for quantity differences you can't tell exactly what is going on. On the BOM wizard you can scroll through and compare numbers but there really should be some place where you can just look at the ebom and quickly see what the adjustments are.     Request in the Web App a column that shows the Qnty difference between the eBoM and the cBoM if the eBoM view is created from a CAD import.  if the ebom=cbom show blank.   Show More

For more background, please see my forum post on this issue:  https://forums.autodesk.com/t5/upchain-forum/no-way-to-globally-attach-linked-documents-to-parts/td-p/11850995   It appears that Upchain currently does not support adding Documents that exist outside of a project to BOM Items within that project. I am able to Link these documents to the project by using the "Share" feature, which then makes the document available to the project... however I cannot go a step further by adding these Linked documents to BOM items.   A Global scope for documents is crucial for my PLM usage. Being able to reference documents globally prevents duplicates and confusion.  Show More

In order to manage the limited number of item type rules and allow for the many prefixes we use, I need to have our prefix rules set up as free text. This puts the responsibility of the user to remember dozens of existing prefixes we use. I cannot set the prefix as Fixed Text because we would run out of item type/rules real quick. Could a drop down be added to pick from list of predetermined prefixes that would then populate the Free Text. It would be even better if the options in the list were filtered by the Item type selected and managed by the Picklists! I would want it in the Plug-in too.           Show More

Please create an orphan report at project end item level. Report to include relevant info from orphan tab within the CN. Component, item name, status, kitting (revision tag to be at the end), full tree path, H qty, R qty, Move QTY, Total, Unit cost, Extended cost, Notes.    As of now users were starting CN to review orphans under an end item which is time consuming. As the orphan tab have nested view, user cannot do component sort. If item was part of that assy previously, it will show up in the filtered list. If it wasn’t, then it will not show up in the filtered list and you need to manually search in the full list.  Show More

Hello to all,   I am working in Jaspersoft software to create new custom reports for Upchain. We can "only" put attributes coming from the item creation, not the categorization attributes added after creation. It will be very interesting to have this possibility. It could be a good improvement from Upchain side to give us the possibility also to manage Attributes from categoriation. Please have a look on the following screenshots.   Thanks you to let me know for the status of this improvement needed Show More

Changes made to columns in BOM Wizard should save for user. Video attached showing the current behavior. Show More

The BOM wizard, when it opens, is not wide enough to show all columns. Users would have to expand the BOM Wizard window every time to see all of the information. I understand that this can’t be considered a bug. But I believe that users would get frustrated quickly if they have to change Column widths every time that the Bom Wizard opens, just to view the information that they are looking for. Remember that they are used to the old BOM Wizard and that would be the benchmark. I'm attaching image of what the original BOM wizard columns looked like. It has the cbom and ebom qty shown clearly. If the user wants to see the Item name, they could just expand the column as required.    For the new BOM Wizard, if you could set the ebom and cbom qtys (along with Item Name, filename and status) to auto-fit width by default,  that would be acceptable. Show More

Expected behavior: Date required field is editable by "Project manager" or "Lead Mechanical Designer" Actual behavior: Cannot edit date required field unless workflow is in draft Workaround Currently in cloud, the CN will allow editing only while the workflow is in a draft state. As a workaround, you can change the workflow back to a draft state when the required dates need to be changed. Show More