Use this page while you edit a report and want to keep your work: how saving works, what the save states mean, how to resolve a save conflict, and how to go back to an earlier version. To build and arrange reports, see Build a report.
The save menu offers the fix for the current state: Retry after a failure, and Overwrite or Revert when there is a conflict.
While the conflict is open, saving stays paused. A failed step reads Save failed, Overwrite failed or Revert failed with the reason under it; when a revert cannot load the other version, the message reads "The newer version could not be loaded."
If this tab runs an older version of the app than the one that last saved the report, saving stops and a message says "Reload to save - this report uses a newer visual type". This is not a save conflict: there is no Overwrite or Revert to choose. Click Reload to continue; edits made since the last save cannot be kept.
Restoring writes the version you picked back as a new version; nothing in the history is overwritten. The message reads "Version restored" with "Saved as version N. Nothing in the history was overwritten.", and the restored copy appears as the newest version, labelled "Restored from version N".
A report with no versions yet says "This report has no saved versions yet. Versions appear with the first save." When a comparison finds nothing, it reads "No differences from the previous version." or "No differences from the current version."
Previews run against live data, so the figures can differ from when the version was saved: a version keeps the layout, not its numbers.
The status describes what is not written down yet, not the outcome of the last save. Edits made after that save put it back to Unsaved changes; when the newest edits are written, it reads All changes saved.
It is disabled while a save is running, while there is nothing to save, and while a save conflict blocks saving. With a conflict, choose Overwrite or Revert first; the tooltip reads "This report changed elsewhere - overwrite or revert first".
No. Saving runs when you ask for it or on the autosave interval you choose; nothing writes on every change.
No. Overwrite writes your edits as the newest version; the version saved elsewhere stays in the history.
The tab runs an older version of the app than the one that last saved the report, so no retry can succeed. This is not a save conflict: there is no Overwrite or Revert to choose; click Reload to continue, and note that edits made since the last save cannot be kept.
Exit asks "Exit edit mode without saving?" with Save and exit, Discard and exit and Keep editing, and leaving the report asks "Leave without saving?" with Save and leave, Leave without saving and Stay here. Save and leave writes a version first and leaves only once that save succeeds.
Switching pages happens inside the editor, so the leave guard does not ask, and your edits stay open in the tab. The guard asks when you leave the report; nothing is saved or lost by moving between pages.
A failed save reads Save failed with the reason under it, and your edits stay in the tab. Choose Retry in the save menu, or save again with Ctrl+S. If Overwrite failed, try again or use Revert; if a revert failed with "The newer version could not be loaded.", try again in a moment. For more message-by-message fixes, see Troubleshooting.
No. A version keeps the layout, not its numbers: previews run against live data, so figures can differ from when the version was saved.
The newest one, marked Current. Every restore button is also disabled while a restore is running.
vs previous compares the selected version with the version saved just before it, and vs current compares it with the newest version. Only diff shows the changed parts and Full shows the whole document.
Anyone who can edit the report. Version history is an editing action, so a report shared with you as Can view does not offer it. See Who can do what in DataPrism.