RWS Community
RWS Community
  • Site

Trados Studio

Trados Team

Trados Accelerate

Trados Enterprise

Trados GroupShare

Trados Business Manager

Passolo

MultiTerm

RWS AppStore

Connectors

Beta Groups

Managed Translation

MultiTrans

TMS

Trados Enterprise

WorldServer

Language Weaver

Language Weaver Edge

Language Weaver Connectors

Language Weaver in Trados Studio

 

 

Tridion Docs

Tridion Sites

Contenta

LiveContent

XPP

Trados Studio Ideas

Trados GroupShare Ideas

Trados Team Ideas

Trados Team Terminology Ideas

Trados Enterprise & Accelerate Ideas

Trados Business Manager Ideas

MultiTerm Ideas

Passolo Ideas

RWS Appstore Ideas

Tridion Docs Ideas

Tridion Sites Ideas

Language Weaver Ideas

Language Weaver Edge Ideas

Managed Translation - Enterprise Ideas

TMS Ideas

WorldServer Ideas

Trados Enterprise Ideas

XPP Ideas

GroupShare Developers

Language Cloud Developers

MultiTerm Developers

Passolo Developers

Trados Studio Developers

Managed Translation Developers

TMS Developers

WorldServer Developers

Tridion Docs Developers

XPP Developers

Language Combinations by Language Services

RWS Training & Certification

Style Guides

RWS Campus

Trados Approved Trainers

ETUG (European Trados User Group) Public Information

Nordic Tridion Docs User Group

Tridion West Coast User Group

Community Ops

demospace

RWS Community Internal Group

AURORA

Internal Trados Ideas

Linguistic Validation

Mercury

XPP Cloud

Recognition & Reward System

RWS Community Platform Related Questions

Community Solutions Hub (Trados)

Events

RWS Training & Certification

To RWS Support

  • Search
  • Translate

    Detecting language please wait for.......


    Powered by
  • User
  • Site
  • Search
  • User
  • Products
  • Trados Portfolio
  • Trados Business Manager
  • More
  • Cancel
Trados Business Manager
  • Products
  • Trados Portfolio
  • Trados Business Manager
  • More
  • Cancel

Trados Business Manager > Wiki

Upgrading from version 5
  • Home
  • Blog and Product Updates
  • Forums
  • Wiki
  • Ideas
  • Docs
  • More
  • Cancel
  • New
Show Translation Options

Detecting language please wait for.......


Powered by
Trados Business Manager requires membership for participation - click to join
  • Wiki
  • +Licensing & Installation
  • -TBM 6
    • +Release Notes
    • -Basic Information
      • Introduction
      • System requirements
      • Demo version limitations
      • Internet connection
      • Installing SDL Trados Business Manager Team/Enterprise
      • Installing SDL Trados Business Manager Essential
      • Moving the TBM Essential to a new computer
      • Launching the application
      • Application update
      • Upgrading from version 5
      • Config file (appsettings_global.json)
      • How to report about issues
    • Quick Start
    • +Database engine
    • +Software configuration
    • +List views and data entry forms: usage and customization
    • Dashboards
    • +Reference data
    • +Documents
    • +Security system
    • +Service functions
    • +Data export and import
    • +Reports and analytics
    • +Invoice templates and custom reports
    • API
    • +Portal for customers
    • +Portal for Vendors
    • +Integrations in Business Manager
    • +CV
  • +Trados Business Manager Connector plugin
  • +Trados Business Manager plugin
  • +FAQ
  • TBM 5 documentation
  • Download links for older versions

Upgrading from version 5

Trados Business Manager 6 brought a lot of new functionalities comparing to version 5, and upgrade to new version isn't as straightforward as just installing a new version over an old one. There are some breaking changes that require manual actions. However, there are not so many breaking changes, and the whole process isn't very complex.

Please note that these instructions only relate to managing the upgrade of the database that was implemented with Version 5.  It's important to follow all the instructions in the installation of Version 6 that are provided in the installation wiki article.

Prerequisite.

Backup your database to be able to safely return to v5 if something goes wrong.

Breaking change 1. File storing mechanism.

In the new version, mechanism of storing files was completely rewritten, and now files are stored on a hard drive, not inside database, as it was before. This solves few problems:

  • Database won't grow too much when files are uploaded to entities, which makes it easier to backup databases (leaving file backup task to be solved separately on your own) and safer use, for example, Microsoft SQL Server Express, without worrying to exceed database size limit
  • You can view/add/delete files using regular file explorer

Before installing update to version 6, it is required to install most recent update of version 5 and do the following:

  1. Open application settings and switch to the Files and folders tab:
  2. At the bottom, you will find a Migration to version 6 group. In this group, fill names of folders where you want to store files from your quotes, jobs, invoices and other entities.
  3. Check folder template names for quotes, projects, jobs and assignments above the Migration group. Ensure that template names do not create similar parent folders as specified in the Migration tab. For example, if folder name for jobs is Jobs, then if folder template name for translation jobs is Jobs\{1}, then another folder named Jobs will be created inside jobs folder. In this case, remove parent folder name from the job folder template and make it just {1}.
  4. Click Prepare migration to v6. Application will go through all your entities and extract files stored inside database to your hard drive.

Breaking change 2. New database engine in desktop version.

This is applied only to local (freelance) versions. If you use team version and network database engine (MS SQL Server or PostgreSQL), please skip this section.

Version 5 used SQL Server CE as a database engine. In TBM 6, we switched to SQLite, as it provides more reliable database solution, better performance, and it is cross-platform. This means that full database conversion is required for switching to v6. Overall procedure will be as follows:

  1. Open application settings and click Export all data to json file. This will export all your database into text file, which can be imported to v6 later.

  2. Open all your custom reports and templates and export them into repx format. To do this, open a report in the designer and export it:
      or 
  3. Open all your custom QuickReports and save them into xml format:
  4. Install version 6 and run it. Login as Admin (default password is User@TBM). You can't have blank passwords for Admin user anymore, but if you just close application and launch it again, you will still be logged as Admin. But if you logout before exiting the application, then logon form will be displayed upon next launch.
  5. If you have custom fields in TBM5, please open settings (  in the navigation menu), click Custom fields, and create the same custom fields as you had in v5. The same means that names of custom fields must be identical. Otherwise, data won't be imported correctly into these fields. Don't forget to logout and login again to process created custom fields.
  6. Open application settings and import exported json file.
  7. Go to reports, create new reports and import your templates. Old templates (invoices, quotes, etc.) should work as they worked before, as database structure wasn't changed too much. However, it is recommended to test them in advance, to avoid bad surprises when you start generating your actual invoices.
  8. Go to QuickReports, create empty reports and load saved xml files. Again, reports should work correctly without any additional changes.
  9. If any error appears at any of these steps, please contact us using forums, Submit idea button, or privately.
Important! All your custom dashboards, list view customizations and data entry form layouts will be lost, as new version uses completely new approach to such customizations. However, thanks to new implementation, you now have more control over customizations, and such situations as lost customizations after installing new application update could not happen anymore.
  • Share
  • History
  • More
  • Cancel
Related
Recommended
  • Our Terms of Use
  • Copyright
  • Privacy
  • Security
  • Anti-slavery Statement
  • Cookie Notice
  • YouTube