I want to be able to add a shortcut to the search feature of the document control window on the start up home page when I open datastay. Currently its a few extra steps to get there and page loading can take a bit. I'd like a faster way to get to what I need to see.
it would be very helfull and more "secure" to be able to manage a library of Attributes and sections that would ease the use of common attributes between different workspaces without having to clone a workspace.
In workspace creation, we should be able to pick an attribute or a section (with its attributes) for such library. All information shall be kept (eg: Picklist for attribute or Advanced permission for Section).
Such library should have a "where used" function for each of its item (as for scripts) in order to track impact before any change. If a change is done on the library, it shall be cascaded to lall item using this attribute or section. (Question: do you propagate it only to latest working version or to all? it could be an option when saving....)
What are the chances that the Autodesk team could come up with a solution to change future Field Data Types and not lose all previous saved data.
I have come across this a number of times. I am wanting to keep the same data, but learning the system and its capabilities I have found more efficient ways to pull the data along. The current way is running a report and using an excel spreadsheet to re-populate the fields (which is a strenuous process, for me)
It would be great to have a matrix built based on a dynamic data set, like color and size; You could specificy sizes across the top and colors along the sides and allow the user to enter values at the intersection of both values, like indicate if this combination is offered or not. This would eliminate the need to hard code the values in a matrix every time new valuse are added and make the matrix more useful over all.
A use case came up to compare two BOMs using the flat version of the BOMs. Basically we are going to start importing quoted (flat) BOMs into PLM 360 to compare to the structured/level BOMs created in our custom configurator application. The team is looking a quick way to verify totals in PLM 360, exporting to excel is possible but sub-optimal. Ideally you would mimic the Nested Views and features for the flat view.
It would be a time saver to be able to configure a custom BOM view for the Flat view, Similar to the nested view. This could possibly be implemented with a checkbox for and Applies to Nested, Flat or Both.
We have set up custom BOM field that is used to trigger spawing of tasks to perform action on the item in the BOM Row, I.E. Generate an RFQ request where the item info is copied via script to the RFQ Record. The issue is that in the nested view the quantity shown is the unit quantity not the project rolled up quantity. To get that you need to switch to the flat view get the rolled up quantity and switch back to the nested view and enter the quantity to Request for Quote.
This is just one use case, but feel that functionality would make the BOM View for useful.