PowerTSM 4.9
PowerTSM 4.9
Section titled “PowerTSM 4.9”[4.9.3] - 2025-10-03
Section titled “[4.9.3] - 2025-10-03”Restores compatibility between 3.x clients and 4.x databases
[TSM-7751] Include Version 3 Database Modifications in Version 4
Section titled “[TSM-7751] Include Version 3 Database Modifications in Version 4”The latest 3.x release included changes to the database. This broke compatibility between version 3 clients and version 4 databases. This patch solves this issue.
For reference, here are examples that demonstrate the interoperability of HAKOM products accross the different versions:
| Application | Version | Compatible 3.x Databases | Compatible 4.x Databases |
|---|---|---|---|
| PowerTSM App | 3.10.6.3 | 3.10.6.3, 3.10.6.4 | 4.9.0, 4.9.1, 4.9.2, 4.9.3 |
| 3.10.6.4 | 3.10.6.4 | 4.9.3 | |
| WebTSM Services | 3.10.6.3 | 3.10.6.3, 3.10.6.4 | 4.9.0, 4.9.1, 4.9.2, 4.9.3 |
| 3.10.6.4 | 3.10.6.4 | 4.9.3 | |
| PowerTSM HTTP API | 4.9.2 | — | 4.9.0, 4.9.1, 4.9.2, 4.9.3 |
| 4.9.3 | — | 4.9.0, 4.9.1, 4.9.2, 4.9.3 |
[4.9.2] - 2025-09-05
Section titled “[4.9.2] - 2025-09-05”Minor bugfix. [Known Issue]: There are issues when accessing a 4.9.2 database using version 3 clients. If this is a requirement, please update to patch 4.9.3
[TSM-7568] - Invalid Response When Attempting to Create a New Time Series With Invalid Settings
Section titled “[TSM-7568] - Invalid Response When Attempting to Create a New Time Series With Invalid Settings”When creating a new time series that had unsupported settings (i.e. function type “StepLeft” on a non-cyclic time series), a bug prevented the error to be reported back to the caller. This has been fixed.
[4.9.1] - 2025-08-29
Section titled “[4.9.1] - 2025-08-29”Improved error handling and ability to write custom functions for formula time series. Added new features to HTTP API.
[TSM-7442] HTTP API: Request all Time-Dependent Unit Conversions
Section titled “[TSM-7442] HTTP API: Request all Time-Dependent Unit Conversions”A new endpoint has been added to the HTTP API, which makes it possible to find all exchange time series: GET /repositories/{repository}/units/timedependent
[TSM-7370] HTTP API: Data Write Time Span Endpoint Supports Quotation
Section titled “[TSM-7370] HTTP API: Data Write Time Span Endpoint Supports Quotation”The endpoint POST /repositories/{repository}/timeseries/{timeseries}/datatimespan now supports the quotationDateTime parameter. Please note that this endpoint is mainly intended for internal purposes.
[TSM-7374] HTTP API: New Endpoint for Data Aggregation
Section titled “[TSM-7374] HTTP API: New Endpoint for Data Aggregation”Until now, the HTTP API did not support data aggregation in a given interval. This feature has been added in the form of a new endpoint: GET /repositories/{repository}/timeseries/{timeseries}/data/total.
The required parameters are:
from- the starting time of the aggregation intervalto- the endpointintervalTransformationMethod- the id of the desired aggregation method
Example: getting the average of all data points in the given interval
GET https://api.powertsm.com/api/repositories/{repository}/timeseries/{timeseries}/data/total?from=2024-12-19&to=2024-12-23&intervalTransformationMethod=2[TSM-6587] HTTP API: Node Tree Operations
Section titled “[TSM-6587] HTTP API: Node Tree Operations”It is now possible to work with node trees in the HTTP API. The supported operations include:
- Create Nodes and Child Nodes
- Modify Nodes
- Read Nodes and Child Nodes
- Delete Nodes For more details check the OpenAPI specification tag “Time Series:Nodes”.
[TSM-7416] HTTP API: Support of Non-Numeric Value in Time Series
Section titled “[TSM-7416] HTTP API: Support of Non-Numeric Value in Time Series”When reading data of a formula time series using the HTTP API, Non-numeric values (such as those that result from a division by zero) are usually returned as 0. This can now be adjusted using an optional parameter in the requested media type: numberFormat This controls the formatting of special numeric values.
string: Returns floating point literals such as “infinity”, “-infinity”, or “NaN” as strings.number: Will return floating point literals as 0.0. Example:
GET https://api.powertsm.com/api/repositories/{repository}/timeseries/{timeseries}/dataAccept: application/json;numberFormat=string[TSM-7397]: Reading Audit Logs of Audit Time Series
Section titled “[TSM-7397]: Reading Audit Logs of Audit Time Series”Previously it was only possible to read the audit logs of quotation time series. The new version now supports this function for plain audit (historic) time series as well. To do this, the time series must be created with the PreserveHistoricData to flag set to true.
- HTTP API: Enpoint /data/auditlogs
- .NET API: Functions ReadAuditLogEntries and TryReadAuditLogEntries
[TSM-7283] .NET API: Service Injection in CustomFunctions
Section titled “[TSM-7283] .NET API: Service Injection in CustomFunctions”CustomFunctions can now directly inject required services (such as configuration or helper classes).
Task ICustomFunction.Initialize<TValue>(ICustomFunctionContext<TValue> context){ var flagProvider= context.TryGetService<IFlagProvider>().GetValueOrThrow(); return Task.CompletedTask;}[TSM-7285] .NET API: Formula Parser now Processes Custom Functions with Variable Parameters
Section titled “[TSM-7285] .NET API: Formula Parser now Processes Custom Functions with Variable Parameters”The FormulaParser now supports custom functions that use the params keyword to accept a variable number of time series arguments. This enables writing functions like BestValue([series1], [series2], …).
[TSM-7284]: Direct registration of CustomFunctions
Section titled “[TSM-7284]: Direct registration of CustomFunctions”CustomFunctions can now be registered directly in code, without needing a separate DLL or .csx file.
[CustomFunctionName("MyFunction")]class MyFunction : ICustomFunction<double,..> { }static async Task Main() { var tsm = ITsm.Create(container => { container.UseCustomFunction<MyFunction>(); });}This makes it easier to develop, test, and use your own functions.
[TSM-5410]: Duplicate Nodes when Updating Child Nodes
Section titled “[TSM-5410]: Duplicate Nodes when Updating Child Nodes”When updating child nodes in a certain way on PostgreSQL, a parent node could erroneously be instantiated multiple times. This has been fixed.
[TSM-7394] .NET API: Incorrect Error Message when Creating a TimeSeriesDataCollection with Incorrectly Ordered Data
Section titled “[TSM-7394] .NET API: Incorrect Error Message when Creating a TimeSeriesDataCollection with Incorrectly Ordered Data”When writing data to a time series which has both quotation and audit set to true, it is not possible to save data to the same time stamp twice in the same transaction. This used to result in a rather unpretty Unique-Constraint error. This has been changed to a more intuitive description of what has gone wrong.
[TSM-6678] HTTP API: Missing Error Message When Writing Quotation Data on Non-Quotation Time Series
Section titled “[TSM-6678] HTTP API: Missing Error Message When Writing Quotation Data on Non-Quotation Time Series”Writing data with a quotation time stamp on a non-quotation time series used to just ignore the time-stamp and write the data normally. This is not intuitive and has thus been fixed. Now the respective error code is returned.
[TSM-7404] .NET API: Error When Reading Certain Time Series Within a Transaction
Section titled “[TSM-7404] .NET API: Error When Reading Certain Time Series Within a Transaction”When reading a time series that has quotation, preserveHistoricData and preserveAuditLog set to “true” within a transaction an error occured. This has been fixed.
[TSM-7393] HTTP API: “No results for query” when requesting a non-existing Attribute
Section titled “[TSM-7393] HTTP API: “No results for query” when requesting a non-existing Attribute”When querying a non-existent attribute, a specific AttributeNotFoundException is now returned instead of a generic “No results for query” exception. This improves traceability and error handling in the client.
[TSM-7418] TSM APP via HTTP API: Time Series with Custom Time Zones Cannot be Used in 4.x
Section titled “[TSM-7418] TSM APP via HTTP API: Time Series with Custom Time Zones Cannot be Used in 4.x”Time Series that are created with a custom time zone in 3.x could not be searched for, opened or edited in 4.. This error has been fixed.
[TSM-7480] NET API: Custom Functions Does Not Work With Generic Types
Section titled “[TSM-7480] NET API: Custom Functions Does Not Work With Generic Types”Fixed a bug where generic types in ICustomFunctions were parsed incorrectly, preventing their use as return values or parameters. This is now supported, allowing custom functions such as:
[CustomFunctionName(nameof(Sum))]public class Sum : ICustomFunction<ITimeSeriesData<double>[], ITimeSeriesData<double>> { ... }[4.9.0] - 2025-06-23
Section titled “[4.9.0] - 2025-06-23”[TSM-7139] .NET API: DateTimeOffsetExtension is Now Public
Section titled “[TSM-7139] .NET API: DateTimeOffsetExtension is Now Public”Following methods are now publicly accessable for DateTimeOffset manipulation:
- AddInterval: Adds a given interval to the current DateTimeOffset.
- SubtractInterval: Subtracts a given interval from the current DateTimeOffset.
- AlignWithNext: Aligns the current DateTimeOffset to the next occuring interval step.
- AlignWithPrevious: Aligns the current DateTimeOffset to the previous occuring interval step.
[TSM-6425] HTTP API: Add OpenAPI Specification
Section titled “[TSM-6425] HTTP API: Add OpenAPI Specification”Added an OpenAPI specification to the HTTP API, available at the URI <baseurl>/documentation/openapi/index.html. Accessing this URI will display a Swagger document that outlines all defined API endpoints and their specifications.
[TSM-7010] Application Insights
Section titled “[TSM-7010] Application Insights”Since 4.9.0 logging to Application Insights is supported. To enable this, the following configuration entry must be added:
<HAKOM> <TSM> <Http> <Logging> <ApplicationInsights ConnectionString="APPINSIGHTS_CONNECTION_STRING"/> </Logging> </Http> </TSM></HAKOM>Replace APPINSIGHTS_CONNECTION_STRING with the full connection string provided by Azure Application Insights.
[TSM-7130] HTTP API: Support X-Forwarded-Prefix Header Name Configuration
Section titled “[TSM-7130] HTTP API: Support X-Forwarded-Prefix Header Name Configuration”ForwardedPrefixHeaderName can now be additionally configured in the ForwardedHeadersOptions:
<HAKOM> <TSM> <Http> <Hosting> <ProxySettings> <ForwardedHeadersOptions> <ForwardedPrefixHeaderName>X-Forwarded-Prefix</ForwardedPrefixHeaderName> </ForwardedHeadersOptions> </ProxySettings> </Hosting> </Http> </TSM></HAKOM>[TSM-7002]: Removed Relative Links in IdentityProvidersController and IdentityController
Section titled “[TSM-7002]: Removed Relative Links in IdentityProvidersController and IdentityController”This fixes issues in IdentityProvidersController and IdentityController by replacing hardcoded paths with a BaseUrl() extension method that dynamically generates URIs. This provides proxy support through X-Forwarded headers configuration.
[TSM-6688] HTTP API: Default Logging
Section titled “[TSM-6688] HTTP API: Default Logging”Previously, if no logging configuration was defined in the HAKOM.xml file, the service would start without producing any logs. This made it difficult for users to diagnose issues or verify that the service had started correctly. This behavior has been improved: by default, the service now logs to the console at the INFORMATION level when no custom logging configuration is provided.
[TSM-6580] .NET API: Attribute Node Management in 4.9
Section titled “[TSM-6580] .NET API: Attribute Node Management in 4.9”In the new version users are able to manage node attributes. This provides a powerful tool for time series and attribute organization and connectivity. Operations on these attributes include the following:
[TSM-6585] .NET API: Reading Trees
Section titled “[TSM-6585] .NET API: Reading Trees”A node attribute tree can be read by accessing individual nodes by searching for their reference, or by the attribute the node is assigned to.
[TSM-6584] .NET API : Creating and Modifying Node Trees
Section titled “[TSM-6584] .NET API : Creating and Modifying Node Trees”Node attribute tree operations have been added to the .NET API. The attribute serves as the root node and can have any number of child nodes. Each of these can have any number of child nodes themselves. Nodes that have the same parent node, need to have unique names among themselves. Only complete tree deletion is supported.
[TSM-6586] .NET API: Writing, Reading and Deleting Nodes To and From a Time Series
Section titled “[TSM-6586] .NET API: Writing, Reading and Deleting Nodes To and From a Time Series”To provide operations for reading and writing node assignments to time series, four new methods have been added to the IAttributeDataStore interface:
async Task<ITimeSeriesDataCollection<INodeReference?>> ReadNodeAssignment(Period period, CancellationToken cancellationToken = default)Task<Result<ITimeSeriesDataCollection<INodeReference?>>> TryReadNodeAssignment(Period period, CancellationToken cancellationToken = default)async Task WriteNodeAssignment(ITimeSeriesDataCollection<INodeReference?> data, CancellationToken cancellationToken = default)Task<Result> TryWriteNodeAssignment(ITimeSeriesDataCollection<INodeReference?> data, CancellationToken cancellationToken = default)
[TSM-7145] .NET API: Added CachingOptions Parameter to ICache<TCacheEntry>.TryGetOrCreate
Section titled “[TSM-7145] .NET API: Added CachingOptions Parameter to ICache<TCacheEntry>.TryGetOrCreate”There is a new parameter in ICache<TCacheEntry> of the type MemoryCacheEntryOptions with a default value of null. This parameter contains several customizable settings that will be applied to the cache.
[TSM-7144] .NET API: Added Caching to Authorization
Section titled “[TSM-7144] .NET API: Added Caching to Authorization”To increase performance, caching has been added to AuthorizationService operations.
[TSM-7146] .NET API: IntervalTransformationOptions not accessable through IDataTransformer Interface
Section titled “[TSM-7146] .NET API: IntervalTransformationOptions not accessable through IDataTransformer Interface”Due to a missing getter in the IDataTransformer interface, the IntervalTransformationOptions class was not accessable, even though it is neccessary for various use cases. This has been fixed.
[TSM-7205] HTTP API: Missing Error Logs for Request With Incorrect Database Connection
Section titled “[TSM-7205] HTTP API: Missing Error Logs for Request With Incorrect Database Connection”Upon sending a request on the /repository endpoint using a faulty database connection definition, a JSON object stating the nature of the error should be returned. This was not the case and instead the HTTP-Statuscode 200 and an empty list were returned. The expected behavior has been reinstated.