REVERT (Project Administration)
- Last UpdatedMar 22, 2022
- 1 minute read
Function:
Allows the administrator to restore a Database (DB) to a previous session.
Description:
This command is similar to the BACKTRACK command. Sessions are defined as the work done between SAVEWORK commands. The administrator can revert to the date or session number required, or, if the required session has been stamped, they can revert to the Stamp. The current state of the DB will be lost.
Any elements which are claimed out to Users or extracts must exist in the backtracked session.
This command has a different effect from BACKTRACK. Instead of truncating the DB, a new session is added that is a copy of the required session. This means that unlike BACKTRACK, REVERT can always be reversed.
Note:
For DBs which contain external Drawing or Diagrams files (PADD and SCHE) the System
may add an additional session immediately after the REVERT to modify the file names of certain Drawings or Diagrams. This means that the User
will always see a modified version of the original session, rather than the exact
REVERT session; and REVERT is not allowed when Users are modifying these types of DBs.
Examples:
|
REVERT PIPE/PIPE to 10:30 Reverts DB to the session current at 10:30. REVERT PIPE/PIPE to 31 MAY Reverts DB to the session current on 31st May. REVERT PIPE/PIPE to SESS 10 Reverts DB to the session 10. REVERT PIPE/PIPE to STAMP /stamp_012 Reverts DB PIPE/PIPE to the session that has the Stamp /stamp_012. |
Command Syntax:
|
>-- REVERT dbname to <when> ---> |
Related Commands:
BACKTRACK (Project Administration)
MERGE CHANGES (Project Administration)
REMOTE REVERT (Global Project only)