Issue
- .MTA file not updated
- .MTA file does not show the correct value when exported/imported
- The Menta project does not have the correct value when imported into a new database
Product Line
TAC Vista
Environment
- Vista
- Menta
- Xenta OP
Cause
The upload/download parameter does not save any changes in values to the .MTA file. It only saves it to the device and Vista database. This means that if you export a project and import it to a new database the .MTA file will contain the initial values chosen when you last saved the Menta project. To get the values saved to the .MTA file, you need to edit the Menta project and save it again. However, to trigger the save correctly, you need to change the project. For example, add a comment or move a block, then hit save.
Resolution
Below is the correct way to edit a project in a new database.
- On the client PC, start by doing an upload parameter; this ensures that the values stored in the Xenta are present in the Vista database.
- Edit the Menta project(s) and add a comment (This can be a comment like "John brings the project home to make some changes") now the project can be saved, and all new values will be stored in the .MTA file.
- Export the database/project
- Import the database/project to the new PC
- Make the desired changes
- Edit the Menta project(s) and add a comment (This can be a comment like "John has made the following changes ....") now the project can be saved, and all new values will be stored in the .MTA file.
- Export the database/project
- Import the database/project into the client's PC
- Now make a download parameter; this ensures the Xenta will get updated with the changes you have made.