Skip to content
Documentation

PowerTSM 4.13

This release lets time series searches and single time series requests include attributes, list attribute units and list attribute value descriptions, adds a changedSince filter and bulk loading of time series, and fixes bulk requests, custom functions on Linux and vulnerable OS packages in the Docker image.

[TSM-8862] HTTP API and .NET API: Custom Functions From .csx Files Failed to Compile on Linux

Section titled “[TSM-8862] HTTP API and .NET API: Custom Functions From .csx Files Failed to Compile on Linux”

On Linux hosts, e.g. in Docker containers, custom functions provided as .csx files could not be compiled, so formulas using them failed. This has been fixed.

[TSM-8928] HTTP API: Docker Image Contained Vulnerable OS Packages

Section titled “[TSM-8928] HTTP API: Docker Image Contained Vulnerable OS Packages”

The HTTP API Docker images up to 4.12.x contain OS packages with known vulnerabilities, e.g. CVE-2026-86145, CVE-2026-89157, CVE-2026-89161 and CVE-2026-103111 in PCRE2, that newer versions of their .NET base image have fixed. Release images are now always built on the latest version of the base image, which itself is unchanged (mcr.microsoft.com/dotnet/aspnet:8.0), and the image build installs the Debian security updates available at that time. Building the image from the Dockerfile in the deployment package therefore needs access to the Debian package mirrors (deb.debian.org).

[TSM-8938] HTTP API: Bulk Requests Fail for Endpoints That Differ by API Version

Section titled “[TSM-8938] HTTP API: Bulk Requests Fail for Endpoints That Differ by API Version”

Bulk requests (POST /automation/bulk) targeting an endpoint that is served differently depending on the API version, such as /repositories/{repository}/timeSeries/{timeSeries}/assignments/attributes/{attribute}/data, failed for every item with an error stating that the endpoint matched multiple registered endpoints. Such bulk requests now resolve to the endpoint of the current API version, as does a bulk request without an api-version. Selecting an older API version for a bulk request is not supported yet (see TSM-8971).

[TSM-8947] HTTP API: Bulk Request Items Ignore Serialization Parameters From the Accept Header

Section titled “[TSM-8947] HTTP API: Bulk Request Items Ignore Serialization Parameters From the Accept Header”

Items of a bulk request (POST /automation/bulk) whose target endpoint has no dedicated bulk handler were always written with the default serialization parameters, ignoring parameters such as casing, timeFormat or numberFormat in the bulk request’s Accept header. Each item is now written with the same parameters as the bulk response itself, just like the same request sent directly.

[TSM-8952] HTTP API: Include Attributes, List Attribute Units and Value Descriptions When Getting a Single Time Series

Section titled “[TSM-8952] HTTP API: Include Attributes, List Attribute Units and Value Descriptions When Getting a Single Time Series”

GET /repositories/{repository}/timeSeries/{timeSeries} now takes the include query parameter of the time series search, with the same values attributes, attributeUnits and listAttributeValues, for time series addressed by name and by id:. The response then equals the matching element of the search result, including the usedValues of each list attribute assignment with listAttributeValues (see TSM-8970), and without include it is unchanged.

[TSM-8953] .NET API: Load Many Time Series by Name or by ID in One Call

Section titled “[TSM-8953] .NET API: Load Many Time Series by Name or by ID in One Call”

Custom implementations of ITimeSeriesStore should implement the new TryLoadBulk method. Without a proper implementation, there will not be any performance gains from the new bulk handler for time series.

ITimeSeriesStore gained TryLoadBulk / LoadBulk overloads that load many time series by name, and ITimeSeriesStore<TIdentifier> overloads that load them by identifier, both with a TimeSeriesResultContent. Every distinct requested value gets exactly one result keyed by that value - the same result TryLoad would return. The values are loaded with one database query per 1000 values. A null name, or one longer than the database’s name column can hold, is answered as not found without failing the other values. Custom implementations of ITimeSeriesStore inherit default implementations that call TryLoad for each value.

[TSM-8959] HTTP API and .NET API: Filter Time Series by Last Change With changedSince

Section titled “[TSM-8959] HTTP API and .NET API: Filter Time Series by Last Change With changedSince”

GET /repositories/{repository}/timeSeries accepts the new query parameter changedSince, e.g. changedSince=2024-05-01T10:15:30Z, and GET /repositories/{repository}/calculations/aggregation accepts it as search.changedSince. Both then only consider the time series whose definition, attribute assignments, attribute data or time series assignments were changed at or after that time. A request that modifies any of these may also be counted if it fails part-way or changes nothing, while writing time series data does not count as a change. PowerTSM 3.x HTTP clients that send changedSince no longer receive HK09008. In the .NET API, ITimeSeriesSearchParametersFactory.CreateWithAttributeCollection and the deprecated ITimeSeriesSearchParametersFactory.Create have a new optional parameter changedSince, which the new read-only property ITimeSeriesSearchParameters.ChangedSince returns. As before, saving a time series definition through the .NET API with an explicit historicDateTime sets its last-changed time to that point in time, even if it is earlier than the previous one, so a changedSince later than that point in time no longer finds the time series.

Also fixed: when IAttributeDataStore rejects a single list attribute value or node, it no longer deletes the attribute data that is already stored.

[TSM-8962] .NET API: Load List Attribute Units and Value Descriptions When Searching Time Series

Section titled “[TSM-8962] .NET API: Load List Attribute Units and Value Descriptions When Searching Time Series”

[BREAKING] Only for custom implementations of ITimeSeriesStore: the new TryFind overload taking a TimeSeriesResultContent has to be overridden to return units and value descriptions. Its default implementation serves None and Attributes through the includeAttributes overload and fails with HK09002 (a NotSupportedException) for any content with units or value descriptions instead of silently omitting them!

ITimeSeriesStore.Find and TryFind have new overloads taking a TimeSeriesResultContent instead of the includeAttributes flag. None and Attributes behave like includeAttributes = false / true. AttributeUnits additionally returns the list attribute units already resolved, and ListAttributeValues returns list attribute assignments as IAssignedListAttributeData, whose UsedValues holds the resolved list attribute value reference of every distinct value their data uses, keyed by the raw value; like the references of the list attribute value store, they refer to their unit unresolved even when AttributeUnits is requested. A value the effective list attribute unit (see TSM-9012) does not list gets a null entry instead of failing the time series, and the store logs a warning naming the time series, the attribute, the unit of the assignment, if it has one, and the values. The overloads taking includeAttributes are now deprecated. They remain in every 5.x release and will be removed in a major release, 6.0 at the earliest. Starting with 5.0, the default implementations for the new TryFind overloads will be removed.

[TSM-8965] .NET API: Load a Single Time Series With Attributes, Units and Value Descriptions

Section titled “[TSM-8965] .NET API: Load a Single Time Series With Attributes, Units and Value Descriptions”

[BREAKING] Only for custom implementations of ITimeSeriesStore: the new TryLoad overloads taking a TimeSeriesResultContent have to be overridden. Their default implementations only support TimeSeriesResultContent.None and fail with HK09002 (a NotSupportedException) for any other content instead of silently omitting the attributes, units and value descriptions!

ITimeSeriesStore and ITimeSeriesStore<TIdentifier> gained TryLoad / Load overloads that take a TimeSeriesResultContent. Loading a time series by name, by reference or by identifier can now include the assigned attributes, their unit names and the used list attribute values in a single call. The existing overloads are unchanged.

[TSM-8970] HTTP API: Include List Attribute Units and Value Descriptions When Searching Time Series

Section titled “[TSM-8970] HTTP API: Include List Attribute Units and Value Descriptions When Searching Time Series”

The new include query parameter of GET /repositories/{repository}/timeSeries replaces the deprecated includeAttributes and takes the values attributes, attributeUnits and listAttributeValues. attributeUnits resolves the list attribute units, and listAttributeValues adds a usedValues object to each list attribute assignment, keyed by every distinct value its data uses (written verbatim, whatever the casing), whose values have the shape of an element of GET /repositories/{repository}/lists/units/{unit}/values. A value the effective list attribute unit (see TSM-9012) does not list comes back as null instead of failing the time series. includeAttributes remains in every 4.13+ and 5.x release and will be removed in a major release, 6.0 at the earliest.

[TSM-8980] HTTP API: Include the Values of Every List Attribute Unit When Listing the Units

Section titled “[TSM-8980] HTTP API: Include the Values of Every List Attribute Unit When Listing the Units”

[BREAKING] Only for custom implementations of IListAttributeUnitReferenceFactory<TIdentifier>: the new TryCreate overload taking the IReadOnlyList<IListAttributeValueReference> of the unit’s values has no default implementation and has to be implemented. It must return a reference implementing IResolvedListAttributeUnitReferenceWithValues<TIdentifier>, otherwise GET /repositories/{repository}/lists/units?include=values fails with HK15147!

GET /repositories/{repository}/lists/units takes the new include query parameter with the value values. Each unit then carries an array values next to value with all of its list attribute values, each in the shape of an element of GET /repositories/{repository}/lists/units/{unit}/values, ordered by sort order (a missing sort order counts as 0) and then by id; a unit without values carries an empty array. Without the parameter the response is unchanged except that the units are now ordered by id, and the per unit endpoint now returns its values in the same defined order and is served by a fixed number of queries whatever the number of values. On .NET, IListAttributeValueStore.TryFind returns resolved references in that order, and the new IResolvedListAttributeUnitReferenceWithValues with the matching IListAttributeUnitReferenceFactory.TryCreate overload carry a unit together with its values.

[TSM-8982] HTTP API: Dedicated Bulk Handler for Getting Time Series by Name or ID

Section titled “[TSM-8982] HTTP API: Dedicated Bulk Handler for Getting Time Series by Name or ID”

POST /automation/bulk against GET /repositories/{repository}/timeSeries/{timeSeries} is now served by a dedicated bulk handler. It loads the items with one database query per repository, include value and kind of addressing (name or id:), and per 1000 values, instead of one request per item. Items with an invalid include value, an unparsable id: or a query parameter the endpoint does not accept fail with the new error HK01014 (instead of HK09006, HK09007 or HK09008). Results arrive in completion order, not input order; correlate them by identifier.

[TSM-9012] HTTP API and .NET API: Resolve the List Attribute Values of Assignments Without a Unit

Section titled “[TSM-9012] HTTP API and .NET API: Resolve the List Attribute Values of Assignments Without a Unit”

With ListAttributeValues (include=listAttributeValues) the values of a list attribute assignment without a unit are resolved like in the PowerTSM App: in the only list attribute unit of the attribute or, if it has several, in its default unit. A value that still cannot be resolved comes back as null and is logged with a new warning stating that the assignment has no unit. An attribute that is not of type List no longer gets a unit or used values, even if its assignment stores one.

© 2026 Volue.Version v0.6.38017 November 2026