Repository navigation
Same Named Scenarios handling during Backup import #964
Closed
vibhor1102
started this conversation in
General Feature Requests
Replies: 1 comment
|
I vaguely remember seeing someone bring it up first, but i can't find them to credit despite my search efforts... :( |
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
While importing a backup, if same named scenarios are found (both to be checked against existing scenarios, and previously restored scenarios by the same backup restoration process), the user should be presented with an option for each of the conflicting ones individually:
(1)or- Copysuffix added.Potential user error could be that they somehow get a corrupted backup, and decide to replace the existing scenario with the corrupted one. That'd cause an irreversible damage. There could be a small "number of events" check while selecting the replace option. And, if the number of events of the backup-being-imported is found to be lower, then an additional warning popup is shown before replacement occurs. Informing them like "Your existing scenario xyz has 9 events but the backed up scenario only has 4. Are you sure you want to replace it? This action will be irreversible." with buttons provided to duplicate, replace or skip provided once again.
All reactions