User Tools


Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
en:adminmanual:faq [2020/06/11 01:30]
joebordes
en:adminmanual:faq [2020/06/11 13:07] (current)
joebordes
Line 166: Line 166:
 ??? How can we rollback a mass edit? ??? How can we rollback a mass edit?
  
-!!! Three ideas come to mind, all rather "​techy":​+!!! Some ideas come to mind, all rather "​techy":​
  
   * Recover from a backup of the database. This is the easiest option with the only downside of losing information/​work since the last backup, but you are doing frequent backups anyway, right? ​ :-)   * Recover from a backup of the database. This is the easiest option with the only downside of losing information/​work since the last backup, but you are doing frequent backups anyway, right? ​ :-)
   * If the amount of work done doesn'​t permit you to recover from the database then you can recover the backup database into a copy, extract the table with the lost data, and copy it into the production database. Now create an update SQL command to update the incorrectly updated fields from the backup table. This option is a surgical backup recovery only of the fields you have updated instead of a full backup recovery.   * If the amount of work done doesn'​t permit you to recover from the database then you can recover the backup database into a copy, extract the table with the lost data, and copy it into the production database. Now create an update SQL command to update the incorrectly updated fields from the backup table. This option is a surgical backup recovery only of the fields you have updated instead of a full backup recovery.
   * Another similar alternative to the last step is using the coreBOS history tracker. If you have ModTracker activated on the module you have mass edited, then you have a register of the old and new value in the ModTracker database tables. So you can manually handcraft update SQL commands to recover the original values. This is like recovering from the backup table but harder and you must have ModTracker active before doing the mass edit.   * Another similar alternative to the last step is using the coreBOS history tracker. If you have ModTracker activated on the module you have mass edited, then you have a register of the old and new value in the ModTracker database tables. So you can manually handcraft update SQL commands to recover the original values. This is like recovering from the backup table but harder and you must have ModTracker active before doing the mass edit.
 +  * If you have Record Versioning active on the module with the mass edit error then it is REALLY simple, you just set the previous version as the active record. I don't remember if that can be done as a mass action but since all the other solutions require going to the database, you can go there also to make the previous version active if it can't be done through the UI.