Share ideas for future product features directly with the Fusion Manage (formerly Fusion 360 Manage) team and collaborate on existing suggestions with your peers.
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for
Show only
|
Search instead for
Did you mean:
This page has been translated for your convenience with an automatic translation service. This is not an official translation and may contain errors and inaccurate translations. Autodesk does not warrant, either expressly or implied, the accuracy, reliability or completeness of the information translated by the machine translation service and will not be liable for damages or losses caused by the trust placed in the translation service.Translate
We observed that there is no way to purge the deleted items without purging the entire workspace. As the purge on workspace wipes out (permanently deletes) all the data within it, having an option to purge the deleted items only would be a cool thought.
Interesting ask and potential viable IFF the item is an orphan or top level ie has no relarionships from other items that depend on it. Curious how would you expect the system to handle the cases where relationships exist and point to those archived items to be purged permanently. e.g. Linking picklist of some other item points to the purge-able archived item. Parent bom has a component that is archived that is to be purged ~ even better, bom has been released to production. Or Project mgmt schedule and milestones depend on an archived item that is to be purged. Or a change order is in CCB process when someone with permissions archives and decides to purge an item whilst some and not all people on the CCB board have approved the change, and the goal post moves on the pending approvers. Another point is audit trace ~ should all history about item be wiped too, or would you expect to retain its history that an item existed with process run against it and people collaborated and decision were made before the item was purged.
Interesting ask and potential viable IFF the item is an orphan or top level ie has no relarionships from other items that depend on it. Curious how would you expect the system to handle the cases where relationships exist and point to those archived items to be purged permanently. e.g. Linking picklist of some other item points to the purge-able archived item. Parent bom has a component that is archived that is to be purged ~ even better, bom has been released to production. Or Project mgmt schedule and milestones depend on an archived item that is to be purged. Or a change order is in CCB process when someone with permissions archives and decides to purge an item whilst some and not all people on the CCB board have approved the change, and the goal post moves on the pending approvers. Another point is audit trace ~ should all history about item be wiped too, or would you expect to retain its history that an item existed with process run against it and people collaborated and decision were made before the item was purged.
not sure how @mpasumarti or company handles deleted items but, my suggestion would be to Purge ONLY Deleted Items. because you would typically not delete an item that is used anywhere or was used anywhere. You would only Delete an item that was created incorrectly. Archived Items do not fall into this Category...
Archived/Obsolete items have current History and Audit trails associated to the Item or parent. these should never be deleted or purged.
Archived/ Obsolete Items should never be purged in my opinion for that audit trail reason. but I think any Item that is Deleted should be purged on a selectable purge (deleted items only) button....
another reason would be if you deleted an item that you thought was not needed, then a year from now you want to release the same item code. the system throws an error of duplicate item creation. "cannot create duplicate Item" which is good BUT you wouldn't know it was created because the Item exists on the "deleted" view. ("Show Only Deleted Records for this View") even if you search for the Item before you try to create it.
Not trying to sound obtuse, but I'd just like to understand the underlying requirement.
What's the reason you would like to purge those small number of unrelated and deleted items? Simply to save space? If so, do we have an idea how much space they are taking up? Or, are you wanting to zero/wipe records so that you can be positive that bad ideas never come back to life (i.e., in litigation discovery, etc.)?
users usually don't ever create a view that shows only deleted items so if they are trying to create a new record with the same code as a deleted one it will error with "can not create duplicates" but they cannot see the deleted record because they don't have a view set up.
Thank you for submitting your idea. Have you tried the Modern Interface lately? We request that you review your idea in the context of the Modern interface. If your idea is not addressed, we invite you to create a new Idea in the context of Modern so that it can be addressed accordingly.
Sincerely,
Keri Bender | Global GTM Business Strategy Manager, Product Lifecycle Management
