# Save a DMN decision

As with BPMN, the modeller batches changes and a save flushes them before writing. The stored file is DMN XML.

The practical advice is the same: commit the cell you are editing before saving.

---

## What this is for

* Understanding what a save actually does.
* Diagnosing a save that appears to have missed the last cell.
* Knowing what is stored and in what format.

---

## How it works

| **Action**           | **How**                                 |
| -------------------- | --------------------------------------- |
| Flush                | Pending modeller changes are applied.   |
| Write                | The DMN XML is written.                 |
| Version              | Each save creates a restorable version. |
| Close without saving | Discards the session's changes.         |

---

## A few things that catch people out

* Press Escape or Tab out of a cell before saving, so the value commits.
* The close button is a cancel.
* Saved files are standard DMN and open elsewhere unchanged.

---

## Related

[Fix DMN editor problemsDefault tables, thumbnails and imports.](https://help.gocapable.com/diagrams/fix-dmn-editor-problems.html)

[DMN viewsThree views of the same model.](https://help.gocapable.com/diagrams/dmn-views.html)

[DMN editorBack to the editor overview.](https://help.gocapable.com/diagrams/dmn-editor.html)

---

_Draw the map before writing the rules._