Skip to content
Documentation

PowerTSM 4.11

This release addresses a bug in the HTTP and .NET API.

[TSM-8486] .NET API: IListAttributeValue.SortOrder Is No Longer Nullable

Section titled “[TSM-8486] .NET API: IListAttributeValue.SortOrder Is No Longer Nullable”

[BREAKING] The SortOrder property on IListAttributeValue has changed its type from int? to int. Any client code that handles this property as nullable (e.g. null checks or nullable assignments) must be updated. The SortOrder property on IListAttributeValue now returns a non-nullable int. In addition, the sortOrder parameter on IListAttributeValueFactory.TryCreate and Create now defaults to 0 when not provided, removing the need to explicitly pass a value when the sort order does not matter.

This release addresses several bug fixes and improvements across the HTTP and .NET APIs, including build and documentation corrections, a security dependency update, and more robust formula time series handling.

[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-7785] Added Support for Formula Time Series Referencing a Time Series with a Unit That is Not Defined in the Database

Section titled “[TSM-7785] Added Support for Formula Time Series Referencing a Time Series with a Unit That is Not Defined in the Database”

Formula time series will use the default interval transformation method when the unit does not exist, instead of returning an error.

This version fixes several bugs in the HTTP API and adds minor features to search and delete functionality.

Section titled “[TSM-7171] Time Series Search: Attribute with empty string value search”

When searching in the HTTP API with attribute=<name>|, i.e “pipe, followed by nothing”, or attribute=<name>|oneof(,<value>) will return time series that have the attribute assigned with an empty value.

[TSM-7894] HTTP API: Hide SQL Error Details From User-Facing Responses

Section titled “[TSM-7894] HTTP API: Hide SQL Error Details From User-Facing Responses”

This change ensures that low-level SQL error details are no longer exposed in user-facing HTTP API responses when deleting time series definitions. Instead, the detailed SQL error is stored internally on a dedicated property for diagnostics, so customers only see a generic, high-level error message.

[TSM-7905] AttributeStoreFactory has an unnecessary parameter

Section titled “[TSM-7905] AttributeStoreFactory has an unnecessary parameter”

IAttributeStoreFactory no longer requires the AttributeTypeStore to be provided in the create method, as it can be acquired internally. Therefore, the method has been overloaded and the old method was marked as obsolete.

[TSM-8022] .NET API: Delete Attribute Assignments Also Removes Underlying Data

Section titled “[TSM-8022] .NET API: Delete Attribute Assignments Also Removes Underlying Data”

Deleting an attribute or list attribute assignment now also deletes the underlying entry data for the affected time series and attribute. The deletion is performed explicitly in configurable chunks (configuration key TSM:Persistence:Data:ChunkSize, default 1000) to improve performance and stability when large volumes of data are removed. Previously, it was not possible to edit and save the HAKOM.xml file while the HTTP API Service is running. This is now possible but changes to the settings are still only applied after restarting the service.

[TSM-8044] HAKOM.xml is Locked while HTTP API is Running

Section titled “[TSM-8044] HAKOM.xml is Locked while HTTP API is Running”

Previously, it was not possible to edit and save the HAKOM.xml file while the HTTP API Service is running. This is now possible but changes to the settings are still only applied after restarting the service.

[TSM-8070] OpenAPI Specification: Incorrect Capitalization of Types in Description

Section titled “[TSM-8070] OpenAPI Specification: Incorrect Capitalization of Types in Description”

Parameter type names like interval.type were incorrectly referenced with a capitalized letter after the dot (e.g. interval.Type) in the description fields. This has been fixed to be consistent throughout.

[TSM-8125] .NET API: Delete Quotation Time Series Support for TransactionScopes

Section titled “[TSM-8125] .NET API: Delete Quotation Time Series Support for TransactionScopes”

Using the .NET API to delete a quotation time series inside a TransactionScope no longer causes a deadlock.

[TSM-8152] Interpolated Flag marked Obsolete

Section titled “[TSM-8152] Interpolated Flag marked Obsolete”

The Flag “Interpolated” with the identifier 22 has been marked obsolete and will be removed altogether with the next major release. Users are advised to not use it in future development and remove it from already existing systems.

[TSM-8158] Long Save Time for Non-Cyclic Time Series With Duplicate Values

Section titled “[TSM-8158] Long Save Time for Non-Cyclic Time Series With Duplicate Values”

This change fixes an issue where saving non-cyclic time series data with duplicate consecutive values could take several minutes. After the adjustment, such data is stored with normal performance while keeping the existing behavior of not saving duplicate values twice.

[TSM-8176] Nullable TimeSeriesDataCollection Properties

Section titled “[TSM-8176] Nullable TimeSeriesDataCollection Properties”

The Interval, Cyclic, Function, Unit, and TimeZone properties of TimeSeriesDataCollections have been made nullable in the context of HTTP requests to allow deserialization when these values are not present in the serialized data. When null, the deserializer now attempts to retrieve default values from the target time series to which the data is being written. The default time series provider can also be implemented to fetch the default values from some other context.

[TSM-8181] .NET API: Add Search for Attribute Assignments by Attribute and/or List Attribute Unit

Section titled “[TSM-8181] .NET API: Add Search for Attribute Assignments by Attribute and/or List Attribute Unit”

A new overload for the (Try)FindAssignments method has been added, that allows searching for attribute to time series assignments by attribute- and/or list attribute unit reference.

[TSM-8182] HTTP API and .NET API: Error Handling When Deleting or Unassigning List Attribute Units

Section titled “[TSM-8182] HTTP API and .NET API: Error Handling When Deleting or Unassigning List Attribute Units”

[BREAKING] When deleting or unassigning list attribute units, these operations no longer automatically succeed if dependent data exists! The following endpoints are affected:

  • DELETE repositories/{repository}/lists/units/{unit}/assignments/{attribute}
  • DELETE repositories/{repository}/lists/units/{unit}

When deleting or unassigning list attribute units, existing dependencies (e.g., list attribute assignments that reference the unit) are now taken into account. A force parameter has been added to the HTTP API’s DELETE methods (see above) and the .NET API’s (Try)DeleteAssignment methods in the IListAttributeUnitStore, allowing deletions or unassignments to be enforced even if dependencies exist. If force = false or omitted, a new descriptive error is raised that includes affected dependent pairs of time series and attribute identifiers.

[TSM-8183] .NET API: Add Force Parameter to Delete List Attribute Value Methods

Section titled “[TSM-8183] .NET API: Add Force Parameter to Delete List Attribute Value Methods”

A force parameter has been added to the (Try)Delete(ByValue/Description) methods to allow deleting a list attribute value even if it is used in a list attribute to time series assignment. If force is set to true, existing references in assignments will be deleted.

[TSM-8184] HTTP API and .NET API: Error Handling When Deleting Attributes

Section titled “[TSM-8184] HTTP API and .NET API: Error Handling When Deleting Attributes”

[BREAKING] When deleting attributes, the DELETE repositories/{repository}/attributes/{attribute} endpoint no longer deletes automatically if assignments exist!

When deleting attributes, existing assignments are now taken into account. A force parameter has been added to both the HTTP API (as a query parameter) and the .NET API’s (Try)Delete methods in the AttributeStore, allowing deletions to be enforced even if assignments exist. If force = false or omitted, a new descriptive error is raised that includes the affected assignment identifiers.

[TSM-8185] ListAttributeValueStore: (Try)GetUsage

Section titled “[TSM-8185] ListAttributeValueStore: (Try)GetUsage”

A new method has been added that gets all references to time series assignments that use a list attribute with the specified value.

[TSM-8202] HTTP API: List Attribute Unit Reference Can Be Omitted from Request Body

Section titled “[TSM-8202] HTTP API: List Attribute Unit Reference Can Be Omitted from Request Body”

When saving or updating list attribute values via the HTTP API, the list attribute unit reference can now be omitted from the request body if the unit is already specified in the route path (e.g., /repositories/{repository}/lists/units/{unit}/values). The API will automatically use the unit from the route context.

[TSM-8203] Allow Force Changing a List Attributes Unit Even if it Has Assigned Values

Section titled “[TSM-8203] Allow Force Changing a List Attributes Unit Even if it Has Assigned Values”

A force parameter has been added to the (Try)SaveOrUpdateListAttributeAssignment method to allow updating an assignment even if it not empty. If force is set to true, existing values of the assignment will be deleted if the assignment’s list attribute unit changes.

[TSM-8209] HTTP API: Allow specifying only one quotation boundary

Section titled “[TSM-8209] HTTP API: Allow specifying only one quotation boundary”

It is now possible to specify just one of quotation.from or quotation.to in HTTP requests. Previously, both parameters had to be specified together or omitted entirely. Now, each parameter can be provided independently.

[TSM-8212] HTTP API: Reference List Attribute Values by Value in HTTP Requests

Section titled “[TSM-8212] HTTP API: Reference List Attribute Values by Value in HTTP Requests”

When retrieving, updating or deleting list attribute values via the HTTP API, the targeted list attribute value can now be referenced by its value in the HTTP request paths, instead of only by its ID.

[TSM-8327] Added an Endpoint to Get All Assigned Units of a List-Type Attribute

Section titled “[TSM-8327] Added an Endpoint to Get All Assigned Units of a List-Type Attribute”

A new endpoint has been added, which allows users to get all ListAttributeUnits assigned to a specific attribute.

[TSM-8329] Added an Endpoint to Get All Assignments Between Units and Attribute

Section titled “[TSM-8329] Added an Endpoint to Get All Assignments Between Units and Attribute”

A new endpoint has been added, which allows users to get all ListAttributeUnitAssignments (all assignments between units and attributes).

[TSM-8333] HTTP API and .NET API: Error Handling When Updating List Attribute Values

Section titled “[TSM-8333] HTTP API and .NET API: Error Handling When Updating List Attribute Values”

[BREAKING] When updating list attribute values, these operations no longer automatically succeed if dependent data exists! The following endpoint is affected:

  • PUT repositories/{repository}/lists/units/{unit}/values/{value}_
© 2026 Volue.Version v0.6.38017 November 2026