Skip to main content
K
KA_146204473-Newcomer
3-Newcomer
June 30, 2026
Question

Does saving a model clear the Undo stack in Creo Parametric?

  • June 30, 2026
  • 2 replies
  • 59 views

Hi everyone,

We are currently developing a Creo TOOLKIT-based connector that synchronizes Creo models with an external system.

As part of the synchronization workflow, the connector needs to detect changes made to the model (such as newly added parameters or geometry modifications). Before these changes can be synchronized, the model must first be saved so that the latest state is available. To avoid requiring users to manually save after every change, the connector automatically saves the model when necessary.

However, we've observed that once the model is saved, the Undo history appears to be cleared. As a result, the user can no longer perform undo operations on the model that were enabled before the save.

In some other CAD applications (e.g., Autodesk Inventor), saving the model does not clear the Undo history, allowing users to continue using Undo even after an autosave.

I'd like to understand whether this behaviour is expected in Creo.

  • Is it by design that File → Save (or ProMdlSave()) clears the Undo stack?
  • Is there any recommended TOOLKIT workflow to save the model while preserving the Undo history?
  • How do other Creo TOOLKIT developers handle this scenario when implementing autosave for update/publish workflows?

Any clarification or recommended approach would be greatly appreciated.

Thanks!

2 replies

Dale_Rosema
Dale_Rosema23-Emerald III
23-Emerald III
June 30, 2026

The undo stack is cleared, but after the save there is an iteration created. (filename.prt.1, filename.prt.2, ...). One can always go back to a different iteration if so desired.

    Michael_Bourque
    Michael_Bourque13-Aquamarine
    13-Aquamarine
    June 30, 2026

    Because the undo icon is right next to save icon, I sometimes click save instead of undo and it drive me crazy. :)

    Michael Bourque
    RPN
    RPN18-Opal
    18-Opal
    July 1, 2026

    From the Toolkit Manual:

    All Creo Parametric TOOLKIT calls running in either synchronous (DLL or

    multiprocess) mode or asynchronous mode always clear the Undo/Redo

    stack in the Creo Parametric session. The Creo Parametric user interface

    reflects this by making the Undo and Redo menu 

     

     

     

    But if you get the feature list, why this has an impact on the Undo/Redo Stack?
    So I don’t believe that statement, I guess this can be true on changing something with Toolkit.

     

    Next, File → Save is NOT equal to ProMdlSave(), the User Interface provides the Pre/Post Notification Functions on top.

    For example, if you have setup a pre model save trigger in toolkit, you get called if you press the button in Creo, but not if you call ProMdlSave() in Toolkit.

     

    Terms & ConditionsAccessibility statement