What does it do?
Update models feature allows you, by uploading the full set of files (not only the one that has changed), to preserve:
Audit trail entries
Backups
Assumption manager changes
Charts
Steps
Dashboards
Settings of the project
A conflict resolver window will guide you through the process, to match your previous audit trail entries with the new model structure. You will be able to retrieve all the changes by downloading a reusable CSV file for both conflicts and warnings (changes not applied, resize problems, ...).
Upload my models
To update your models, click on the Project management icon, Manage models tab then on the orange button Update existing models.
The next step is quite similar to your first upload of your models: Upload ALL your files, which will be converted and tested. When this process ends, you will need to click on Update models to open the conflict resolver.

Conflict Resolver
The conflict resolver will guide you through the three different conflict types: model, sheet, and grid conflicts.

In sections Models and Spreadsheets conflicts, Mind will find conflicts if the model and/or sheet names are different between your original and target models. If a conflict appears, you can choose (in the Action dropdown) to Update the missing element or to remove it. Click then on Validate, and continue to the next conflict until there is none left. You can then click on the Validate & Go to the next step button.

In the Grids conflicts section, you will find every grid that has changed its name or position between the original and the new model. When Updating a grid, you will need to select a new target model, sheet, and grid for each missing element.
If several grids match the missing grid, Mind will automatically select the first coordinates it has found in the spreadsheet.

Throughout your conflict resolver process, you will have to validate each of your conflicts and types of conflicts in order to finally validate your update.
Conflict resolver summary
When all your conflicts are validated, a summary will show you all your resolutions and differences of flags between old and new models.

You can then download a CSV recap of your conflict resolution, and if everything is fine Validate all conflicts. You can also ignore formula changes between your old and new versions.
Your project will update, then reload. You can then check that all your files have been updated.
Upload conflicts CSV
You can use your conflicts summary CSV file to resolve quickly and easily conflicts.
You can import your conflicts CSV before resolving your first conflict on the bottom left of the conflict resolver. If the CSV file is successfully imported (conflicts in CSV and detected in Mind should be similar), Mind will resolve automatically conflicts.

Resolver and warning files in the audit trail
A new audit trail entry (that cannot be undone) will be added to your updated model.
You will also be able to download the CSV Resolver file, and a Warnings file with all the warnings of your update.

Update to preserve project changes
The update model feature enables you to update the underlying models of a project while preserving as much as possible project content, following the rules below:
Inputs imported to an existing grid are preserved after update if your inputs do not overlap any nearby grid in your new model. Also, the new /input grid must have the same headers and a same number of columns as your input CSV if you want to preserve inputs.
Updated backups (backup launched before the update) are kept after the updated model if the new backup source and destination grids have the same headers and the same number of columns as old backup grids. Moreover, the destination grid must not overlap any nearby grid in your new model.
Dashboards, charts, and steps built to your existing model are kept after the updated model (if their referenced grid/model is not removed). Steps created by flags in your model are updated as well as their grid.
Flags from the existing grids are updated with the flag in your new grid (can be removed if no flag in the new grid). You will find in Conflict Resolver flag changes.
Run-related changes (like grid resizing each run) and formula changes (if option Ignore formulas changes are switched on in Conflict Resolver) are lost after the update model.
Any audit trail entry that was associated with a deleted model/spreadsheet/grid will be deleted after update model.
If a table or a spreadsheet from a workbook with instances is moved to another workbook, any audit trail entry associated with those elements will be deleted after update model.
If you updated instance key table just before update model, Mind will use those instancekeys if you updated models with the same structure (no models added or deleted). Otherwise, it will use /Instancekey grid from your new models.