The department could not have been "deleted by itself" — in the database, it is impossible to delete a data field that is used in documents. If it is used in at least one document, the system simply will not allow such a deletion.
In the situation described, the issue was not deletion, but renaming. Checking the registration log showed that the department was accidentally renamed, which created the impression that it had disappeared — the familiar name vanished from the list, while the data itself and its links to documents remained in place.
How to figure out a similar situation:
1. Open the registration log — this is a built-in 1C tool that records all user actions in the database: who changed what and when.
2. In the log, find operations related to the department in question for the suspicious time period.
3. Check whether there was a renaming instead of a deletion — this is often the case: the catalog item remained, only its name was changed.
4. If renaming is confirmed — restore the previous name manually via the department's card in the catalog.
Frequently Asked Questions
Can a user accidentally delete a department if it is used in documents?
No, the system protects against this — if a data field is used in at least one document, it cannot be deleted.
How can you find out who made the changes?
The registration log records the user, date, and time of each action in the database — it makes it easy to reconstruct the timeline of events.