fix: abort reasons
All checks were successful
Publish to docs.datacontroller.io / Deploy docs (push) Successful in 1m43s
All checks were successful
Publish to docs.datacontroller.io / Deploy docs (push) Successful in 1m43s
This commit is contained in:
parent
e172464058
commit
aa4854df14
@ -19,13 +19,11 @@ This approach means that the audit history remains intact - there is simply a ne
|
||||
|
||||
Note that there are some caveats to this feature:
|
||||
|
||||
- User must have EDIT permission to make a submission
|
||||
- It will only work for TXTEMPORAL and UPDATE Load Types
|
||||
- It will only work for changes made inside Data Controller
|
||||
- Changes made **outside** of Data Controller cannot be reversed
|
||||
- User must have EDIT permission
|
||||
- Table must have TXTEMPORAL or UPDATE Load Type
|
||||
- Changes **outside** of Data Controller cannot be reversed
|
||||
- If there are COLUMN or ROW level security rules, the restore will abort
|
||||
- If the model has changed (new / deleted) columns the restore will abort
|
||||
- Only submissions that have actually been loaded, can be reverted (obviously)
|
||||
|
||||
## Technical Information
|
||||
|
||||
|
Loading…
Reference in New Issue
Block a user