Skip to main content
Gathering Interest

Versioning within a data model

Related products:Data Modeling
  • October 8, 2024
  • 1 reply
  • 22 views
A
Committed ⭐️
Forum|alt.badge.img+1

For upcoming work we need the ability to define a subscope of a data model (example: A data model covers all aspects of a house, the subscope is the bathroom that is up for a makeover). I suggest this to be implemented as a new base class like “Cognite_versionable”. This needs to encompass both the values stored in the model, but also the structure of the model.

Again - the bathroom example:

Version 1: The same structure as the original bathroom just different specs (values) like for replacing stuff with better products.
Version 2: Replace the shower with a bathtub and add an extra sink

In V2 above this also means a different structure of elements linked to the bathroom.

1 reply

U
Practitioner ⭐️⭐️⭐️
  • Uzair Wali
  • Practitioner ⭐️⭐️⭐️
  • July 21, 2026

Hi ​@Andre Asbjornsen,

I wanted to follow up on this request. Could you clarify the ask here with a slightly more clear example perhaps, one that explains the use case you are/were solving for?

A Data Model is a versioned collection of Views (which are themselves versioned). By design, a data model cannot contain 2 versions of the same entity (View) within it as it is counter to the core purpose of this (versioned) collection. Our REST APIs allow you to retrieve all versions of a View explicitly though, so you can still fetch, retrieve and query through older versions of a View, regardless if it is included in your data model or not.

Regards

    Terms & ConditionsAccessibility statement