This method of rollback is generally used when developing and performing a lot of test analysis runs with data that you do not need to keep:
Open the model Channel Package Check
Keeping your left mouse button pressed down, drag your cursor over all the tables in your model – it doesn't matter if you include other components.
All tables and any other components you included should now be highlighted.
Right-click anywhere in the model window, but not on any modelling component, to display the context menu.
From the menu select Rollback Selected Objects.
Roll back the tables using the options:
Rollback all data
Untick Keep Old Recordsets
A log entry will be produced telling you what data has been cleared. In this case, all data in all selected components in the model.
Rolling back (and re-running) from the Console
This method of rollback is generally used when testing – in particular, when a run was only partially successful, but you have changed the rules in the parts of the model that were successful (so you want to re-load these).
Open the model Channel Package Check
Run the table Channel List Reconciliation
Open the System Console from the Administrator menu → System → Console
Find the log for the analysis run
Click on this entry
In the bottom section, click on the Recordsets tab.
You will find two buttons:
Rollbackall data...
- Rollback data and run the analysis again...
Use the button Rollback data and run the analysis again... to repeat the analysis run from the previous exercise.
Rollback a single table set (a run)
This method of rollback is commonly used when testing a large model. If a single component has been updated and you want to re-run it without causing the rest of the model to re-run, then this approach is suitable.
Open the model Channel Package Check
Right-click on Latest Package Update
Select Rollback.
Accept the default options (the Keep Old Recordsets flag is ticked)
When the rollback has completed, look at the table set list for this table – you will see a single Recordset (the most recent one) is yellow
Run analysis on this table.
The yellow (incomplete) Recordsets will be rebuilt – but this run will not cause any of the table's predecessors to run.