Share & Print
You know what two rare messages about your budget and the server mean and what you do.
Two messages are rare. With both, KOSMA keeps changes that are not on the server yet.
If the server is missing changes to a budget, KOSMA keeps the budget on this computer as it is and shows:
The server copy of this file is incomplete from revision 184, so this device can't load the latest changes. Your local copy is safe. Contact KOSMA support. `KOSMA-E-2032`
Write to support and give the revision number from the message.
If another person worked in a budget on this computer and their changes never reached the server, KOSMA sends nothing more of this budget. When you open the budget, KOSMA opens a **Dataset Version Conflict** dialog with **Keep as a copy**. If it has **Save Changes** instead, it is the other dialog, see [resolve conflicting changes](/kb/article/resolve-conflicting-changes).
Dataset Version Conflict This file holds unsent changes by Anna. Discard drops them. Keep as a copy saves them in a copy, then syncs the file. \[Cancel] \[Keep as a copy] \[!Discard]
Click **Keep as a copy**: KOSMA creates a new budget whose name ends in **(conflict copy)**, with all unsent changes, the other person's and your own. Then KOSMA loads the budget from the server.
**Discard** deletes the unsent changes and cannot be undone.
**Cancel** closes the dialog. KOSMA asks again as soon as you show the budget again or save it by hand.
Markdown