Introduction

This article guides you through the migration process from Typical Manager 2024 to Typical Manager 2024.1 and addresses the impact on existing Typical Manager data.

To ensure a seamless transition, please review this article thoroughly before starting the migration. For details on the new functionality available after the upgrade, see the What's New article for Typical Manager 2024.1. For a complete list of all changes (including bug fixes), see the Release notes article for Typical Manager 2024.1.

Important: Yellax always strives to ensure that new versions of Typical Manager remain as familiar as possible. However, due to new features or changes in vision/strategy, some functionalities may be changed or replaced.

Table of Contents

  1. Change in operation of Relationship Attribute with Source Attribute
  2. Supported SQL Server versions

1. Change in operation of Relationship Attribute with Source Attribute

Although the explanation below is quite technical in nature, it is important for understanding what changes during the migration.

How it worked before (Typical Manager 5.1 and older)

When establishing Attribute Relationships in the Library, the Attribute values in the Projects were visually cleared, allowing the new Attribute Relationship value to be entered.

It was possible to specify which Attribute is the "Source" Attribute within the Attribute Relationship:

  • Setting a Source made all other Attributes read-only, with values manipulable only through the Source Attribute.
  • Without a Source Attribute, every Attribute in the relationship could manipulate the value.

How it works from Typical Manager 5.2 onwards

From Typical Manager 5.2 onwards, this functionality has changed:

  • When a Source Attribute is set, the actual value of this Source Attribute is used and displayed.
  • The relationship does not have/use a separate "Relationship value".
  • The other Attributes in the Attribute Relationship remain read-only, and the value can only be manipulated via the Source Attribute.
  • However, any manipulation now changes the actual value of the Source Attribute.

Impact on existing data

During the update procedure, the existing Relationship values are written into the Source Attributes. As a result:

  • The values do not change for end users.
  • This prevents the situation where a former hidden Source Attribute value would suddenly be visible instead of the Relationship value.

No manual action is required for this change — the migration handles it automatically.

2. Supported SQL Server versions

To provide the best possible experience and ensure the highest level of security, the supported SQL Server versions for Typical Manager have been updated to those that are currently under official support and not considered End of Life.

Currently supported: Microsoft SQL Server 2019 and 2022.

Why upgrading SQL Server matters

  • Security — SQL Server updates often include important security patches and fixes that address vulnerabilities. Upgrading helps keep your data secure and protected from potential threats.
  • Performance and stability — Newer SQL Server versions bring significant performance improvements and enhanced stability, resulting in faster query execution times and a more reliable database environment.
  • Feature enhancements — Microsoft regularly introduces new features, functionality, and enhancements in newer SQL Server releases, enabling improved data analysis and decision-making.
  • Vendor support — By using supported SQL Server versions, you can rely on continued support from both Yellax and Microsoft, helping to minimize downtime and maximize system availability.

Please note: Continuing to use an unsupported SQL Server version poses potential risks to your data security, system performance, and overall stability. We strongly recommend upgrading to a supported SQL Server version at your earliest convenience.

If you have any questions or require further information, please contact the Typical Manager Support Desk.