Imports have several limitations affecting usability and functionality, which steepen the learning curve and/or generally prevent ease of use: Revision, Lifecycle State, Release Date parameters have different names when exported from a view or report (Release Letter, Lifecycle, Version Timestamp) so always need to be mapped manually. Please make these parameters have consistent names across the system. Descriptors of linking pick list items where the last field has no data are displayed across the interface as ending with " -", this is sufficient for a successful match, but data is only imported if the string ends with " - ". The "Done with Errors" report when an import fails is hard to view (xml file) and never contains useful data. If an import times out, this is not communicated to the user. "Message" and "Row" columns in the Errors/Problems list must be adjusted to display their content on every import. When Running an import, the user needs to close the page to return to the import list to see if it was successful The Imports list is sorted by ascending order, so the user has to scroll to the end of the list every time to see the status of the latest report It is not possible to filter the Imports list On an import with a large quantity of columns, the column headers and column data become slightly misaligned Date format for Release Date/Version Timestamp is sometimes not automatically converted to yyyy-mm-dd format Import column widths don't automatically adjust to content Excel files directly exported from Reports are in html format, which can't be used for imports until saved as xlsx files. Surely it's possible to export an xlsx format file automatically. Descriptor format is inconsistent for revision controlled items in linking picklists; custom views and import format is "descriptor REV:w" while "descriptor [REV:w]" is the format in links. Why can't this be consistent? Imports to latest versions do not update working versions automatically, there should be a setting to enable this, otherwise the import needs to be run twice, once for the latest and once with the Revision, Lifecycle State, Release Date parameters deselected for the working version. BOM imports are only possible when parent and child items are from the same workspace Solutions to any or all of the above would represent a significant improvement in usability. Forum, please feel free to add to this list below. Show More

We have the need to produce a BOM that can have the same item used multiple times at the same level rather than increase the quantity, see below:   Imagine a simple assembly with two children as per fusion can currently produce: Machine Assembly                                                        x1 Bracket                                                                 x2 Plate                                                                     x3 With the above it is only possible to increase the quantity of each item.   What we require is: Machine Assembly                                                        x1 Bracket                                                                 x2 Plate                                                                     x1 Plate                                                                     x1 Plate                                                                     x1   Adding further child items can be included as new lines not increasing the quantity. I’m imagining a toggle (or similar) on the place component dialogue that allows the user to pick either increase quantity (the default option) or add new line item as above. The reason for this is to add extra property information to a BOM view such as location ID’s or similar for the individual components, If the quantities are grouped then this information cannot be accurately maintained. I have seen workarounds that use the grid to maintain this data, but this makes the syncing to ERP and ongoing maintenance of the BOM overly complex. Show More

In our User Acceptance Test, our key users run into error when trying to Approve a Change Request (CR) and generate Change Order (CO), because the Affected Item(s) they added were already part of an active CO. We have managed to somewhat overcome this issue by returning a meaningful message to users through scripting, but it would be useful to have a visible indication when we 'Add' Items in the 'Affected Items' dialog box of the CR, to shows the Item(s) we are selecting are already Pending Change and are part of an active ECO. This could be achieved by listing these items with different font colour, or by exposing relevant properties / fields as Columns in the 'Add' Affected Items dialog box (See screenshot). The Items should still be selectable in the list, but user would know that they need to review active COs and potentially associate their CR with an already active CO. Show More

My request is two-fold.    1. Currently, Transition titles jump around erratically when moved. Instead of always going where you want them to, they will shoot across the page in an unpredictable manner. I would like this to be fixed so getting titles to where they need to be is not an arduous process.   2. I would like to see formatting options for the text within the Workflow Editor. We have clients with very complex workflows and having the ability to rotate text to follow the transitions, or having the ability to adjust the size of text would clean up the appearance.  Show More

Currently on the attachment page, the download button only appears when you hover over the attachment in question. I would like to see this either be visible all the time or an option to make it so that you can make it visible all the time. I have seen some confusion when immediately looking at the attachment tab you can't immediately see that you can download anything.  Show More

Please extend the list of options how a picklist link can be rendered. Instead of just “Item Descriptor” to link to the item details, I want to link directly to other tabs.   Currently user is forced to navigate via the Item Details.   This is not just about saving the user some clicks, it helps understanding.   Two examples 1. A grid column (or item details) with picklist to “Document”. I want the user to navigate directly to the attachments tab of that record.   2. Imagine a grid with table of “Part Options” links. The “Part Options” column is a picklist to the “Part Options” workspace. But this workspace contains no real meta on Item Details, the main data is on the grid.   When the user is forced to navigate via Item Details, it is confusing and does not help his/her understanding of the data model.   If the link could directly navigate to the Grid of the Part Options record, the relationship would be easier to understand.     I know I can create my own link with a computed field, but I cannot do this in combination with “Latest Version” option.   Please extend the list of the options available to render the picklist. Grid and Item Details picklists please, as an option on the field definition, not inside the picklist definition itself.       Show More

We recently had an issue discovered by a client that any user that can add items to the managed items tab can see all the items in the related workspace. This is a problem because the user can see items that they do not have permission to see. All that they can see is the descriptor of the item but that alone can contain sensitive information like the part number may be recognizable as a competitor's part. The response from Autodesk Support was: While adding items to any tabs, all relevant items in the chosen workspace will be displayed. The list in the Add pop-up window is not filtered by user permissions. This includes adding to the Managed Items tab also. This response implies it is not just affecting the managed items tab.  I think this is a major security flaw that should be fixed as a critical bug as soon as possible. Our largest client opened an emergency support request with us when they discovered this with a supplier. This could pose a legal problem for them which could have revealed competitive intelligence between suppliers. I can see it becoming a problem for other clients as well and I recommend warning those who are at risk. I think it is reasonable to say that user permissions should be respected/enforced everywhere on the site. User security is a critical aspect of multi-business collaboration. Fusion Manage is marketed as a collaborative platform and Change Orders as well as Supplier management are selling points for manufacturers. Show More

The file types should only be visible to certain groups. For example: The "Viewer" group can only see PDF files The "3D Manufacturing" group can see PDF, STEP and DXF files The "2D Manufacturing" group can see PDF and DXF files. ------------------------------------------------------------------- Die Dateitypen sollen gewissen Gruppen nur sichtbar sein. Zum Beispiel: Gruppe "Viewer" darf nur PDF- Dateien sehen Gruppe "3D-Fertigung" darf PDF, STEP und DXF Dateien sehen Gruppe "2D-Fertigung" darf PDF und DXF Dateien sehen. Show More

In Modern, it can be hard to see which items line up with the rest of the row in the Where Used tab, but if there was filtering on the columns on the Where Used, like on the Items and lifecycles, it would be useful.    There are times when the Where Used tab becomes too difficult to decipher without considerable effort because an item has been used on multiple assemblies, and those assemblies have been updated various times, leading the list in the Where Used tab to grow incrementally with these changes. In many situations, users may be looking to see where an item is used to account for forecasting inventory or other procurement reasons. This is especially hard for users with no BOM information in their ERP systems.   Consider adding filters to the lifecycle and item columns to save our procurement users much hassle. Show More