Hello,
That would be nice to be able to use the asset external IDs (instead of the assetId field) in transformations, to link events (or timeseries, sequences) to existing assets.
Hello,
That would be nice to be able to use the asset external IDs (instead of the assetId field) in transformations, to link events (or timeseries, sequences) to existing assets.
Enter your username or e-mail address. We'll send you an e-mail with instructions to reset your password.
+1
or at least to extend the function
https://docs.cognite.com/cdf/integration/guides/transformation/write_sql_queries/#asset_ids
to be able to use externalId as well
Using names can lead to unexpected results since they are not unique
Similar to the one for dataset i guess
https://docs.cognite.com/cdf/integration/guides/transformation/write_sql_queries/#asset_ids
In general, we would also like to be able to create our own custom SQL function as well
FWIW, the reason we link by internal ID of the asset has to do with fact that we allow externalIds to be mutable in the current asset centric model.
That might not (shouldn’t) prevent a transformation from looking up on the externalId of the asset, and use it’s assetId (the internal ID) to create a link.
thanks@Thomas Sjølshagen , yes that makes sense.
Yes as a data engineer, you will most likely know the external_id so having a way to find the id from external_id is necessary. It would be good to have either a custom function for that or allowed directly in transformations