Version Information

Deprecation Notice

TSM-7930 Convert MaxDbConnection Setting to Connection Pooling

The <MaxDbConnection> setting is hereby considered deprecated and should not be used. Its support will be removed in a future version. To limit access to the underlying database, please use connection pooling settings in the connection string as described by the databases manufacturer.

Fixed Bugs

TSM-7765: Error on Data Endpoint

The endpoint /api/repositories/{repository}/timeseries/{timeSeries}/data would behave unintuitively if a request is sent before the authentication is fully complete. This problem is now handled in a way that provides the user with enough information to act accordingly.

TSM-7446 PowerTSM App: Attributes Are Not Updated in Sheet When Column Is Copied

When copying and pasting a column in an existing data template, which has custom attributes such as TS-MODTIME specified in rows 2-8, the respective rows were not updated for the newly pasted column upon refreshing the sheet. This has been fixed.

TSM-7731 Duplicate Data Access on SQL Server

When accessing time series data on an SQL Server database, some complex queries previously had to be executed multiple times in order to get all the requested data. This was due to an implementation detail in Microsoft's driver. By refactoring how those queries are executed on our end, we were able to fix this for most affected operations. This should cause some performance improvement when using SQL Server, as well as a lighter load on the database overall.

TSM-7853 WebTSM: Incorrect Caching of Exchange Units and Conversion Time Series for Multiple Connections

When using WebTSM Services with multiple database connections (repositories), only exchange units and conversion time series from one connection were cached, leading to faulty conversions. This issue has been resolved, and the WebTSM Service now caches this data individually for each connection.

TSM-8170: TSM App: Prevent Inconsistent Saving Of Overly Long Formulas

When a time series formula exceeds the maximum allowed length, the system now blocks saving and displays a clear validation message instead of silently truncating the formula. This prevents inconsistent or corrupted formulas from being stored and makes such issues immediately visible to the user.

TSM-8178: TSM App: Consistent Validation for Overlength Fields in TSM App

When saving time series definitions, the TSM App now consistently validates the maximum allowed length of affected fields (such as table name, archive table, description, and unit). If a value is too long, saving will now fail with a clear error instead of silently truncating data depending on the database.