Hi team,
We’d like to suggest an improvement for the Transformations feature.
Currently, in Transformations, we only have access to staging tables and not to the instances of the data model that have already been created. This leads to some redundancy and inefficiencies in transformation logic.
Use case:
Let’s say I load Well objects in a first transformation, applying a set of filters (e.g., valid wells, correct country, etc.). Then, in a second transformation, I want to load Wellbore objects. However, to ensure consistency, I want to join with only the wells that were already loaded into the data model — not reapply the same filtering logic I used earlier.
Currently, since I can’t access the already loaded Well instances in the data model, I have to duplicate the filtering logic or rely on external references, which is error-prone and inefficient.
Suggestion:
Allow read access to instances of the data model from within transformations, so we can:
- Reference already created objects (e.g., Well) directly when creating new ones (e.g., Wellbore).
- Avoid duplication of logic.
- Ensure better consistency across related business objects.
Let me know if this is technically feasible or already planned.
Thanks a lot!
Check the
documentation
Ask the
Community
Take a look
at
Academy
Cognite
Status
Page
Contact
Cognite Support