Skip to main content

Release Notes: Version 26.02

What's New ✨​

Get_latest_datapoint Function Added In Rule Framework​

We've added a function (get_latest_datapoint) to the rule framework which allows you to get the last available datapoint for a channel directly, instead of repeatedly loading data to find it. To learn more, check out our documentation here.

Fixed case sensitive issue with timeseries data​

We've resolved an issue where Datasource IDs were treated as case-sensitive in the timeseries table, which previously caused data visibility issues when IDs didn't match exactly (e.g., 'DS_name' vs 'ds_name'). Datasource IDs in the timeseries table are now case-insensitive, aligning with all other platform tables.

⚠️ Important: This update includes a change to how data is stored in BigTable. A small data migration is required during deployment; this will be managed by our support team and is expected to have zero impact on environment downtime.

Disabled EnerGPT Preview​

EnerGPT preview has been disabled in the platform. The feature can be made available, at a cost, if you wish to enable it please contact our support team.

UI 🖥️

  • Permission condition restrictions: Updated the interface to correctly reflect that conditions are not supported for MLModels, Channel Families, and Live Flags permissions.

  • Improved tag traceability: Fixed an attribution error across both the original and new consoles to ensure that created or updated tags correctly display the actual user in the created_by field instead of "System."

🛠 Error Handling

  • Rule inheritance: Resolved an issue that prevented audit events from being logged when a rule had an invalid parent class; an audit event is now triggered if a class attempts to inherit from multiple classes.

  • Enhanced RuleResult validation: Improved audit event clarity when the return object in RuleResult is invalid by providing specific details on the cause of the validation failure.

🔐API and Permissions

  • User group removal sync: Fixed a synchronization issue ensuring all rights are correctly revoked and user details are updated immediately after a user is removed from a permission group.

  • Cross-console permission parity: Resolved inconsistencies between consoles to ensure all permissions granted in the original console are correctly propagated to the new console.

  • Append-only Datasource validation: Updated APIv1 to enforce "append-only" logic; any attempt to remove existing channels from a datasource will now return a 400 Bad Request to ensure data integrity and documentation alignment.

DPAs 🏷️

  • Improved documentation: Added comprehensive documentation and step-by-step instructions for creating Datapoint Attributes (DPAs) directly through the console.

  • Timezone-aware DPA ingestion: Fixed a bug where Timestamp DPAs were incorrectly converted to naive objects; they now correctly remain timezone-aware during ingestion.

🚀Platform & Backend Improvements​

  • Extended search capacity: Resolved a limitation in the search functionality that capped queries at 15 characters; users can now search using strings of any length.
  • Advanced Search view restoration: Fixed an issue preventing the use of the v_channel_data_and_annotations_latest_versions_pretty view, which is now fully queryable in Advanced Search.
  • Final deprecation of Transform Functions: Completed the removal of legacy Transform Functions (previously replaced by Transform Rules), ensuring they are no longer accessible within the platform.
  • Fixed auth bug: Fixed an issue that was causing users being not authorized in some namespaces after using APIv2 or JWT tokens.
  • Deployment Improvement: Included backend changes to reduce manual steps needed for deployment
  • Improved Logging Added JSON-formatted logs to BigTable and BigQuery writers
  • Record duplication cleanup: Fixed multiple backend logic errors that were causing duplicate and triplicate entries for the latest_datasource and datasource BigQuery tables.

26.02.01​

Bug Fixes​

  • Fixed Frontend bug: Fixed an issue regarding the google analytics API, that was causing the Frontend Build to fail