Add "Reload from Disk" or "Discard In-Memory Changes" Command for Assembly Components

[ryan_murphyKSEE3]

Product and Version

• Autodesk Inventor Professional 2025.3
• Autodesk Vault Professional 2025.4
• (Issue observed in multiple prior versions as well)

---

Summary

When a user makes temporary, experimental edits to a part or subassembly within the context of a parent assembly—without checking out and without saving—there is no way to discard those in-memory changes and reload the component from disk without closing all parent assemblies that reference it.

This significantly impacts productivity for users performing "what-if" analysis or exploratory design changes.

---

Detailed Description Use Case

Engineers frequently need to test design ideas before committing to them. A common workflow is:

1. Open an assembly from Vault (all files in Released state)
2. Edit a component to test an idea, declining checkout prompts since this is temporary
3. Evaluate the change in the assembly context
4. Decide to discard the experimental change and revert to the released version

Current Behavior

• The experimental changes exist only in RAM (not saved to disk)
• The following Vault commands do not discard in-memory changes:
  • Refresh File — compares local disk timestamp to Vault; since nothing was saved, disk file is already "current"
  • Get Revision — same issue; local copy already matches Vault
  • Revert to Latest — designed for disk-level discrepancies, not in-memory state
• Closing the part window does not release it from memory because the parent assembly still holds a reference
• The only current solution is to close the entire assembly (and all of its parents), losing any valid work in progress at the assembly level

Technical Root Cause

Inventor's document management keeps referenced documents in memory as long as any parent document references them. The Vault add-in's refresh commands compare disk timestamps, not in-memory state. Since unsaved experimental changes never touch the disk, these commands see nothing to refresh.

From Autodesk's own API documentation:

"If a document is closed, the document is not really closed unless that was the final view and the document is not referenced by any other open documents."

---

Business Impact

Impact Area Description

Lost productivity	Users must close and reopen large assemblies (potentially 100,000+ components) just to discard a small experimental change in one part
Risk of data loss	If the assembly has valid unsaved changes, users face a difficult choice: lose their real work or keep the unwanted experimental changes
Workflow friction	Discourages exploratory design and "what-if" analysis, which are critical for innovation and optimization
Training burden	New users expect "Refresh" or "Revert" to work intuitively; current behavior is confusing

---

Proposed Solution

Add a new command accessible from:

• Right-click context menu on components in the Model Browser
• Right-click context menu in the Vault Browser
• Vault ribbon

Command Name (suggested)

"Reload from Disk" or "Discard Changes and Reload"

Expected Behavior

1. Prompt user to confirm: "Discard all unsaved changes to [filename] and reload from disk?"
2. Internally close the document (with SkipSave)
3. Re-resolve and reload the document from the local workspace file
4. Update all occurrences in referencing assemblies
5. Trigger an assembly update to reflect the reloaded geometry

Integration with Vault

When Vault integration is active, an additional option could be offered:

• "Discard Changes and Get Latest from Vault" — combines discarding in-memory changes with fetching the latest version from Vault in one step

Scope

• Should work on parts and subassemblies
• Should work regardless of Vault lifecycle state
• Should preserve assembly constraints (geometry should be identical if reloading the same version)

---

Workarounds Attempted (All Unsuccessful)

Workaround Result

Refresh File (Vault)	No effect — disk timestamp unchanged
Get Revision (Vault)	No effect — local already matches Vault
Revert to Latest (Vault)	No effect — same reason
Close part window	Part remains in memory due to assembly reference
File → Manage → Refresh (Inventor)	Compares to disk timestamp; no reload occurs
Replace Component with itself	Does not force document reload

---

Related Autodesk Ideas Submission

This request aligns with existing community feedback: https://forums.autodesk.com/t5/inventor-ideas/reload-model-in-assembly/idi-p/12476534

---

Additional Notes

• This limitation has been observed and reported by multiple users across Autodesk forums dating back to at least Inventor 2020
• The issue affects both Vault and non-Vault users, though it is particularly painful in Vault environments where files are often read-only and exploratory edits are common
• A similar "Reload" function exists in other CAD systems (e.g., SOLIDWORKS, Creo) and is a commonly expected feature

[WCrihfield]

Great job documenting this idea.  I agree having this ability would be nice.

One existing Inventor API tool that comes to mind when I read this post is the FileManager.RefreshAllDocuments method, but it supposedly effects all documents in memory, not just a specific one, or specific set of them.

I'm guessing that this would likely be pretty complex for the folks at Autodesk to implement without changing the way certain other systems work too.  For example, users have been asking for the 'UNDO' functionality to be separated out on a 'per document' basis for a long time now, but unfortunately, that is not how it works right now.  If you search the term "UNDO" in the Inventor Ideas forum, you will find a lot of other Ideas posts about that topic, because a lot of people want that system to function differently.  In the Inventor API, it is somewhat related to the TransactionManager, Transaction objects, and the TransactionEvents, which I have used sparingly before in some of my automation tools to 'bundle' lots of small actions into one item in the UNDO list, and/or to undo a whole bunch of small changes, if necessary/beneficial.  Even though they seem to be 'Document' oriented, the problem seems to be that...if a transaction happened between an earlier one and the current one, we can not undo specific transactions earlier in history, without undoing the ones after that point in history too.  And there does not appear to be a way to selectively only undo the actions that effected one specific document, when actions have happened effecting other documents since then, without also undoing the actions to the other documents after those actions.  I can't be 100% sure that is always the actual case, but that's how it seems.  It seems there can be a 'parent/child' association between some of them, but there does not seem to be a modular aspect to them, like with a deck of cards.  We can't just pick a card out of the middle of the stack to get rid of, and leave the rest of the cards alone.  Maybe that would require too much 'memory' the way things are currently structured, not sure.

[tkramerP3NMU]

Agree that a "Get Latest" (Solidworks terminology) should natively exist in the Inventor Vault Add-in. "Refresh" is a joke. Inventor treats local edits, intentional or not, as gospel.

Currently the only solution I've found is to close the files containing the affected parts in Inventor and then go into the Vault application and perform a "Get..." and ensure the "Force Overwrite" is enabled.

I find Vaulted files easily become dirtied which worsens the problem.

Honestly coming from Solidworks, Inventor is years behind. For example, it took AutoDesk about 15 years to add parametric patterns to assemblies. The Inventor weldment creation process is laughable at best too.

Once our subscription is up for renewal, we're transitioning to Solidworks, who by the way sell perpetual licenses still. We evaluated the cost and Solidworks is cheaper in the long-term as well.

/End Rant