PowerTSM 4.12
PowerTSM 4.12
Section titled “PowerTSM 4.12”[4.12.3] - 2026-09-18
Section titled “[4.12.3] - 2026-09-18”This patch release fixes database connections not being returned to the pool when a data read is abandoned early, and a silent data loss when writing to a compressed time series across a block that held no data yet.
[TSM-8716] Database Connections Are Not Being Returned to the Pool
Section titled “[TSM-8716] Database Connections Are Not Being Returned to the Pool”The way we enumerate data after reading it during certain operations was leading to some connections not being returned to the pool, if the enumeration was aborted for any reason. This has now been addressed and connections are returned correctly.
Collections obtained via ITimeSeriesDataCollection<T>.Memoized() now replay an error of the underlying read instead of silently ending the series, re-read the data when every enumerator was disposed before the read completed, and throw an ObjectDisposedException when a disposed enumerator is advanced.
Custom storage providers are affected in two ways: a failure while creating the database command is now reported through the result yielded by TrySelect instead of being thrown out of the enumeration, and providers which manage connections themselves can use the new ReleaseConnectionQuietly method to release a connection without surfacing a failure of that release.
[TSM-8899] Compressed Time Series: Data Loss When Writing Across an Empty Block
Section titled “[TSM-8899] Compressed Time Series: Data Loss When Writing Across an Empty Block”Writing to a compressed time series without preserved historic data could lose stored data points: a write which began in a block that held no data yet and reached into an already populated block replaced the data points of that block outside the written period with missing data points. This has been fixed.
[4.12.2] - 2026-09-09
Section titled “[4.12.2] - 2026-09-09”This patch release brings the database fixes released for PowerTSM 3.11.3.1 and 3.11.3.2 to databases that are already on 4.x, and makes formula evaluation await the asynchronous setup work of custom functions.
[TSM-7716] .NET API: Custom Functions’ Asynchronous Setup Work Is Now Properly Awaited Before Evaluation
Section titled “[TSM-7716] .NET API: Custom Functions’ Asynchronous Setup Work Is Now Properly Awaited Before Evaluation”For custom functions (ICustomFunction) whose Initialize or PerformBeforeCalculation perform genuine asynchronous work (e.g. reading from a database), formula evaluation could previously call Evaluate before that setup had actually completed, producing incorrect or incomplete results. Both methods are now properly awaited before evaluation proceeds, for every custom function invocation.
[TSM-8872] Database: Fixes From PowerTSM 3.11.3.1 and 3.11.3.2 Brought to 4.x Databases
Section titled “[TSM-8872] Database: Fixes From PowerTSM 3.11.3.1 and 3.11.3.2 Brought to 4.x Databases”[BREAKING] On SQL Server (when using the 3.x stored procedures directly), when attribute values are saved inside a transaction that the caller opened, a database error now aborts that entire transaction instead of failing only the individual statement!
The database fixes released for PowerTSM 3.11.3.1 and 3.11.3.2 are now also available for databases that are already on 4.x, as database patch 4.12.2. The scripts are re-runnable and may be applied safely even when the matching 3.11.x scripts were installed before. The patch contains:
- Oracle, PostgreSQL and SQL Server: Deleting quotations in bulk could report success even though the deletion had actually failed: a database error — for example one caused by an oversized
BulkDeleteBlockSize— was swallowed and reported to the caller as “nothing left to delete”. Such errors now surface as errors. Separately, the chunked deletion could stop early and leave archive rows behind when more quotations were affected than fit into a single block; it now works through every affected quotation. - SQL Server: Saving attribute values from several connections at once no longer fails with a deadlock (error 1205); such saves are serialized instead. If the serialization lock cannot be acquired within 15 seconds, the call fails with a dedicated error rather than waiting further.
- SQL Server: Deleting a time series no longer takes an exclusive lock on the entire time series table, so it no longer blocks unrelated reads and writes for the duration of the deletion.
- SQL Server: Reading the last spontaneous value of a versioned time series consulted the non-versioned audit table and could return a wrong value. The versioned audit table is now used whenever a version is given.
[4.12.1] - 2026-07-30
Section titled “[4.12.1] - 2026-07-30”This patch release restores the bulk request endpoint, which was unusable in the 4.12.0 release, and extends it to accept free-form placeholders and values written directly into the endpoint. It also aligns sub-interval data aggregation with PowerTSM 3.x and includes fixes for SQL Server installation and XML documentation, plus a security dependency update.
[TSM-7510] .NET API: Aggregation of Sub-Interval Data Brought in Line With 3.x
Section titled “[TSM-7510] .NET API: Aggregation of Sub-Interval Data Brought in Line With 3.x”Writing data points spaced closer together than the time series’ interval now aggregates them using time-weighted-average consistent with the behaviour in PowerTSM 3.x.
[TSM-8646] Database: SQL Server Warning About Maximum Key Length During Installation
Section titled “[TSM-8646] Database: SQL Server Warning About Maximum Key Length During Installation”On SQL Server, installing the database scripts produced the warning The maximum key length for a clustered index is 900 bytes, indicating that some audit entries could fail to be written. This has been fixed by removing the affected key through the database update.
[TSM-8667] .NET API: Missing XML Documentation for Generic Result and Paging Members
Section titled “[TSM-8667] .NET API: Missing XML Documentation for Generic Result and Paging Members”The XML documentation files delivered alongside the .NET API assemblies were missing the entries for the implicit conversion operators of Result<TValue>, Failure<TValue> and Success<TValue> as well as for Order<TResult>.Equals and Range<TResult>.Equals, so no IntelliSense help was shown for these members when referencing the assemblies directly. The delivered documentation is now complete; the XML files inside the NuGet packages were never affected.
[TSM-8671] HTTP API: Bulk Requests Accept Free-Form Placeholder Names
Section titled “[TSM-8671] HTTP API: Bulk Requests Accept Free-Form Placeholder Names”[BREAKING] Bulk handler implementations (IBulkHandler<TResult>, IBulkHandler<TBody, TResult>) now receive route and query parameters as two separate dictionaries instead of one merged dictionary.
Placeholder names in the endpoint of a POST /automation/bulk request no longer need to match the target endpoint’s parameter names: each <placeholder> is replaced as plain text by the equally-named (case-sensitive) key of the item’s parameters, so it may also cover part of a path segment (/timeseries/id:<id>) or a query value. Item parameters that resolve no placeholder are appended as query parameters. Items that leave a placeholder unresolved receive a per-item status 400 naming the missing placeholder(s).
[TSM-8674] HTTP API: Bulk Requests Accept Query Parameters Hard-Defined in the Endpoint
Section titled “[TSM-8674] HTTP API: Bulk Requests Accept Query Parameters Hard-Defined in the Endpoint”Query parameters written directly into the endpoint of a POST /automation/bulk request (e.g. /repositories/<repository>/timeseries/<timeseries>/data?from=2024-01-01&to=2024-01-02) were silently ignored, so the values had to be repeated in every item’s parameters dictionary. Hard-defined query parameters now apply to every item of the bulk; when an item defines the same key, the item’s value takes precedence.
[TSM-8676] HTTP API: Bulk Requests Accept Hard-Defined Path Segments in the Endpoint
Section titled “[TSM-8676] HTTP API: Bulk Requests Accept Hard-Defined Path Segments in the Endpoint”Fixed values can now be written directly into the path of a bulk endpoint where the target endpoint expects a parameter (e.g. /repositories/<repository>/timeseries/a); previously such requests failed with a per-item 404. The hard-defined value applies to every item and — unlike hard-defined query parameters — cannot be overridden by item parameters.
[TSM-8677] HTTP API: Bulk Requests Failed in the 4.12 Release
Section titled “[TSM-8677] HTTP API: Bulk Requests Failed in the 4.12 Release”In the 4.12 release, every request to the POST /automation/bulk endpoint was rejected with 400 Bad Request (“Each parameter in the deserialization constructor … must bind to an object property or field on deserialization.”). The fix replaces the reflection-based JSON binding of the bulk request envelope with hand-written JSON serializers that are immune to obfuscation by construction. Bulk requests now deserialize correctly.
[BREAKING] A bulk request whose endpoint or method field is missing, null, or not a string is now rejected with a single HTTP 400 response for the entire request, instead of returning HTTP 200 with one error object per item.
[TSM-8679] HTTP API: Bulk Requests Reported an Error Despite Successful Execution
Section titled “[TSM-8679] HTTP API: Bulk Requests Reported an Error Despite Successful Execution”Bulk requests (POST /automation/bulk) targeting endpoints that return a Location header reported a per-item status 500 with the message “Could not find an IRouter associated with the ActionContext…” even though the operation itself had succeeded. Affected items now report their actual result, e.g. status 201 for a successfully created resource.
[TSM-8702] HTTP API: Bulk Requests Reported the Wrong Status and a Malformed Body for Missing References
Section titled “[TSM-8702] HTTP API: Bulk Requests Reported the Wrong Status and a Malformed Body for Missing References”On the fallback path of POST /automation/bulk — endpoints without a dedicated bulk handler — items whose route referenced a non-existent attribute or attribute node reported a per-item status of 400 instead of 404, and their body contained two concatenated JSON documents: the correct problem details followed by a spurious “the field is required” error. Affected items now report the correct status and a single problem details document. Direct (non-bulk) requests were never affected.
[TSM-8711] HTTP API: Bulk Item Responses Use the Result Dialect
Section titled “[TSM-8711] HTTP API: Bulk Item Responses Use the Result Dialect”[BREAKING] The per-item objects streamed by POST /automation/bulk changed from {identifier, status, body} to the Result dialect: successes are {"$successful": "true", "identifier": …, "status": …, "value": …}, failures are {"$successful": "false", "identifier": …, "status": …, "error": …} with an RFC 7807 problem details object as error.
On obfuscated (release) builds, failed bulk items lost their error detail and returned an empty body. Per-item bulk results now use the same wire format as other endpoints returning Result objects, and every failed item carries a full problem details document (error code, message, status) instead of a plain message text.
[TSM-8752] HTTP API and .NET API: Updated System.Security.Cryptography.Xml to Address Known Vulnerabilities
Section titled “[TSM-8752] HTTP API and .NET API: Updated System.Security.Cryptography.Xml to Address Known Vulnerabilities”Updated the System.Security.Cryptography.Xml dependency from version 8.0.3 to 8.0.4 to address four newly published high-severity security advisories. As with the previous update of this dependency (TSM-8446), PowerTSM itself is not affected because encrypted XML files are not used, but the update eliminates security audit findings.
[4.12.0] - 2026-06-26
Section titled “[4.12.0] - 2026-06-26”This release introduces bulk request support, dedicated health check endpoints, a dedicated attribute data format, and extends time series search with attribute data. Includes improved API version routing, localization support, and several bug fixes across the HTTP and .NET APIs.
[TSM-5881] HTTP API: Route Parameters Are Single-Decoded by Default
Section titled “[TSM-5881] HTTP API: Route Parameters Are Single-Decoded by Default”All parameters bound from the route via [FromRoute], regardless of type, now have percent-encoded characters automatically decoded exactly once before reaching the action. Previously plain string parameters surfaced the encoded form (abc%2Fdef) and reference-type parameters had + incorrectly converted to spaces; both inconsistencies are resolved.
[TSM-6927] HTTP API: Bulk Multiple Requests into a Single Call
Section titled “[TSM-6927] HTTP API: Bulk Multiple Requests into a Single Call”The HTTP API now exposes a POST /automation/bulk endpoint that allows multiple API operations of the same type to be submitted in a single HTTP request. Each item independently specifies its route and query parameters and, for POST and PUT operations, a per-item request body. Results stream back in completion order and carry the optional identifier from the corresponding request item so clients can correlate responses regardless of arrival order. A failure on one item does not abort processing of the rest of the bulk.
[TSM-8296] HTTP API: Dedicated Health Check Endpoints
Section titled “[TSM-8296] HTTP API: Dedicated Health Check Endpoints”Two new endpoints are now available for monitoring service health: GET /health/ready returns 200 OK when the service is ready to accept traffic and 503 Service Unavailable during shutdown; GET /health/live returns 200 OK as long as the process is running and not shutting down. Added a new TSM:Http:HealthChecks:ShutdownTimeout setting to control the graceful shutdown timeout (default: 10 seconds). A graceful shutdown aims to complete requests that have already been made, without accepting new ones.
[TSM-7857] HTTP API and .NET API: Dedicated Attribute Data Format
Section titled “[TSM-7857] HTTP API and .NET API: Dedicated Attribute Data Format”Attribute data endpoints (/timeSeries/.../assignments/attributes/.../data) now use a simpler dictionary-based JSON format in API version 4.12 and above, mapping timestamps directly to string values (e.g. { "2024-01-01T00:00:00Z": "value" }). The previous time-series envelope format (with unit, interval, and flag fields) is still served to clients requesting API version 4.11 or earlier.
In API version 4.12 and above, the from and to query parameters on the GET /data endpoint are now optional. When omitted, all stored attribute data is returned.
The .NET API introduces IAttributeDataCollection and IAttributeDataFactory as dedicated types for attribute data, available via the new ITsm.AttributeData facade. The IAttributeDataStore methods taking ITimeSeriesDataCollection<string?> are deprecated and will be removed in a future major release.
Previously, writing attribute data with non-neutral time-series envelope properties (cyclic flag set, function other than step-right, a non-null unit, or a time zone differing from the assigned time series) failed with error HK15092 (WritingAttributeDataCollectionWithConfiguredPropertiesNotSupportedException). Since these properties were never persisted, such writes now succeed and the metadata is silently ignored. The exception class is deprecated and will be removed in a future major release.
[TSM-7762] HTTP API and .NET API: Handle Time Series Data Deletion Independent of Historic Time Series Definition Changes
Section titled “[TSM-7762] HTTP API and .NET API: Handle Time Series Data Deletion Independent of Historic Time Series Definition Changes”[BREAKING] Custom implementations of ITimeSeriesDataStorageConfigurationReader<TStorageProvider,TConfiguration now need to provide their own implementations of the new methods TryLoadBasicConfigurations(CancellationToken), TryLoadQuotationConfigurations(CancellationToken) and TryLoadCompressedConfigurations(CancellationToken).
Deleting a time series previously failed with an internal server error whenever its history contained entries with differing storage shapes — for example, when quotation was enabled or disabled after creation, or when the compression mode was changed for a time series with preserveHistoricData set. All such time series can now be deleted normally regardless of historic changes to their settings.
[TSM-8371] .NET API: Database Errors Are Now Logged With Full Diagnostic Detail
Section titled “[TSM-8371] .NET API: Database Errors Are Now Logged With Full Diagnostic Detail”Database errors are now logged at Error level with SqlState, ErrorCode and the failing query.
[TSM-8375] .NET API Examples: Solution Does Not Compile
Section titled “[TSM-8375] .NET API Examples: Solution Does Not Compile”This fixes faulty configuration in the Directory.Build.props file included with the examples solution, which caused an error (MSB4020) in Visual Studio when attempting to build it.
[TSM-8390] HTTP API: Incorrect Response Type in Swagger Documentation
Section titled “[TSM-8390] HTTP API: Incorrect Response Type in Swagger Documentation”The 200 response in the Swagger/OpenAPI documentation was incorrectly specifying the response type, causing the generated API documentation to be invalid. This has been corrected to accurately reflect the actual response structure.
[TSM-8401] .NET API Examples: Examples reference obsolete functions
Section titled “[TSM-8401] .NET API Examples: Examples reference obsolete functions”Updated obsolete function calls in an example program that demonstrates the basic usage of the .NET API.
[TSM-8397] HTTP API and .NET API: Correct Error Code for Cannot Delete Referenced Attribute Exception on German Operating System
Section titled “[TSM-8397] HTTP API and .NET API: Correct Error Code for Cannot Delete Referenced Attribute Exception on German Operating System”On German operating systems, the error code of the exception that is thrown when trying to delete an attribute that is still used in attribute to time series assignments without using force deletion, incorrectly had the error code HK00000. This has been fixed.
[TSM-8446] HTTP API and .NET API: Updated System.Security.Cryptography.Xml to Address CVE-2026-33116
Section titled “[TSM-8446] HTTP API and .NET API: Updated System.Security.Cryptography.Xml to Address CVE-2026-33116”Updated the System.Security.Cryptography.Xml dependency to version 8.0.3 to address CVE-2026-33116. This vulnerability does not affect PowerTSM as encrypted XML files are not used, but the update eliminates potential security audit concerns.
[TSM-8426] HTTP API: Support Localization In HTTP API
Section titled “[TSM-8426] HTTP API: Support Localization In HTTP API”The HTTP API now supports configurable localization via the new setting TSM:Http:Hosting:SupportedCultures, provided as a comma-separated list of culture identifiers (e.g. de,en,fr). If the list is empty the behavior remains unchanged, thus will use the service host culture. If exactly one culture is configured that culture is always used (Only falling back to the invariant/default culture if the configured culture isn’t available, e.g. fr). If multiple cultures are configured, the first entry is treated as the default and requests can be localized based on the client’s Accept-Language header.
[TSM-8557] .NET API: Constant Unit Conversion Load Now Matches Find
Section titled “[TSM-8557] .NET API: Constant Unit Conversion Load Now Matches Find”Loading a single constant unit conversion could return a different result than the same conversion returned by Find: the integration interval was populated on Load even though Find returned no integration interval for that same conversion. Both methods now return identical conversions.
[TSM-8564] .NET API: Optionally Load Assigned Attributes When Searching Time Series
Section titled “[TSM-8564] .NET API: Optionally Load Assigned Attributes When Searching Time Series”ITimeSeriesStore.Find and TryFind have new overloads taking an includeAttributes flag. When set, each result is an IResolvedTimeSeriesReferenceWithAttributeData exposing every attribute assigned to the time series together with its unit and values (IAssignedAttributeData), all loaded in a single query instead of one query per time series. The previous overloads without this flag are now deprecated and will be removed in a future major release.
[TSM-8574] HTTP API: Optionally Include Assigned Attributes in Time Series Search
Section titled “[TSM-8574] HTTP API: Optionally Include Assigned Attributes in Time Series Search”The GET /repositories/{repository}/timeSeries endpoint accepts a new optional includeAttributes query parameter (default false). When true, each returned time series additionally carries an assignedAttributeData array listing every assigned attribute with its unit and values; when omitted, the response is unchanged.
[TSM-8583] HTTP API: Improved API Version Routing and Documentation
Section titled “[TSM-8583] HTTP API: Improved API Version Routing and Documentation”The HTTP API now reflects the negotiated API version in the Content-Type response header (api-version=X.Y.Z), making it explicit which version was served for each request. The Swagger/OpenAPI documentation now provides a separate specification document for each supported API version, allowing clients to browse the exact API surface available for a given version. Individual endpoints can be version-constrained, so only the operations relevant to a requested version are exposed.
[TSM-8618] HTTP API: Support Requests Without an Accept Header
Section titled “[TSM-8618] HTTP API: Support Requests Without an Accept Header”HTTP API requests that do not include an Accept header (or send an empty or whitespace-only one) are now treated as Accept: application/json by default, returning a valid response instead of 406 Not Acceptable. This improves compatibility with clients such as health check probes that cannot set request headers. The default value can be overridden via the TSM:Http:Hosting:DefaultAcceptHeader configuration key.