Skip to main content

CDF Fundamentals Discussion

  • October 29, 2021
  • 177 replies
  • 6330 views

Show first post

177 replies

Forum|alt.badge.img+2
  • Seasoned ⭐️⭐️⭐️
  • June 29, 2026

Hello Cognite Team,

I am experiencing an issue when copying the following SQL into CogniteActivity.

 

SELECT

workpackage_desc AS description,

to_timestamp(completion_time/1000) AS endTime,

to_timestamp(start_time/1000) AS startTime,

concat('○○●●:', key) AS externalId

FROM IFSDB.maintenance

WHERE to_timestamp(completion_time/1000) > to_timestamp(start_time/1000)

その他の行を表示する

When I paste this SQL into CogniteActivity, an error occurs and the screen appears as shown in the attached screenshot.
 

Could you please help us understand:

  1. What is causing this error?
  2. Is this related to whitespace, special characters, or SQL syntax parsing?
  3. Are there any recommended workarounds or syntax changes to avoid the issue?

Please see the attached screenshot for reference.

Thank you for your support.

 

The “!” next to the “space” propery means that this is a non-nullable property. In other words, a required field that needs to be filled out. In your expression, I do not see you returning space. The same rule applies for externalId. It is non-nullable, and you return it in the expression:

concat(‘Mani1949’, key) AS externalId

So you also need something similar for the space:

'fixed_space_example' AS space

 

Hope that clears it up


Maria Fonseca
Expert ⭐️⭐️⭐️⭐️
Forum|alt.badge.img+5
  • Expert ⭐️⭐️⭐️⭐️
  • June 29, 2026

Hello ​@Kubota Mami ,

Please make sure you follow the section on “CogniteActivity Transformation”

  • Create a new transformation and name it FirstnameBirthyear-Activity. A unique external ID for your transformation will be generated automatically.

  • Fill out the following to create your Events transformation.

    • Destination: Cognite core data model

    • Version: v1

    • Target space: cdf-fundamentals

    • Target  type or relationship: CogniteActivity

    • Action: Create or Update

    • For incoming NULL values on updates: Keep existing values (Default)

I have mark in bold the setting that I believe you have missed. I will also attach an screenshot on how should look. I have run the preview myself and could not encounter any issue with the space.

Let me know if that helps.