Community Discussions

The external id of some time series contains special characters. Should they contain special characters, no, but that is not the issue here. As long as CDF allows special characters in their ID’s it should also have support for them in the rest of the system. When you press the copy button in Fusion you don’t get the special characters, and without those characters the ID is invalid and cannot be used. Hence the copy button does not actually copy the external ID, it alters it and that is an issue.# The actual external IDLIMS_Skarv_Analysis 9-ion analysis_SP 44-AP-0027 - DS - 2. STG\xa0SEP_Param Sulphate, SO42-_Unit mg/l# Copied from Fusion UILIMS_Skarv_Analysis 9-ion analysis_SP 44-AP-0027 - DS - 2. STG SEP_Param Sulphate, SO42-_Unit mg/lThe fact that the external ids contain these characters to begin with is a different issue we are looking into.

Hi,First of all, where can we get the OID Project public data API documentation, and what are the parameters we need to pass to fetch the data?My aim is to use OID public data to access any asset — for example, a pump set — and display its data and health status on a dashboard. The dashboard will be built using React, and for the backend we can use FastAPI with the Cognite SDK.

HiWe are testing out a new deletion transformation for a view in data modeling. The transformation looks something like this:select externalIdfrom cdf_data_models(...)where project in ("ProjectA","ProjectB")This transformation always times out and returns a “Graph query time out” error message. However, when changing the transformation to this the transformation just runs fine:select externalIdfrom cdf_data_models(...)where project = "ProjectA"unionselect externalIdfrom cdf_data_models(...)where project = "ProjectB"For context, the project column here is indexed and the view has around 10 properties and about 1.7 million rows. The transformations all query the same view.We are therefore wondering how the filtering in transformations handles filtering in data modeling and why these transformations are performing different. Learning more about this would benefit us greatly when working with transformations and data modeling in the future :)Thanks in advance!Sebastian

Hi When testing some new functionality in a Cognite Function I got this error message: “The size of the data field is too large.”The data input was from the output of another function ran previously in a workflow.I am looking through the documentation to find what the limits are, but can not find anything.For my use case I can decrease the input size and run more batches, but it would be good to know what the size limits are for input data into Cognite Functions. Also, are there any other size limits I should be aware of?Thank you!Sebastian

All,Now that you’ve had some time to “play with” the Records feature, we’re looking to identify what the consensus is when it comes to the available aggregations for Records. Do we have a useful mix of aggregations available in the API today? Which of the aggregates do you use most often? What is your experience with the API documentation for aggregate API endpoint so far? Have you attempted to use the movingFunction aggregate? What problem did you use it to solve for your  use case? Was the information in the documentation sufficient and useful for you? If you haven’t used the aggregate, please help us understand why not? Have you attempted to use the timeHistogram aggregate? Was the information in the documentation sufficient and useful for you? If you haven’t used the aggregate, please help us understand why not? Is there a use case involving aggregates that you have not been able to address in Records? Please describe the use case? How important is the “missing” aggregate for

Had a chance to experiment with streams and records and it seems to be working well.  Couple of questions based on what I found:Are any of the filtering options that are available for general data modeling queries but not available with records likely to be supported in future?  Specifically, I am thinking of queries like Fetch me all of the records in the last week where the `asset` property is below `Facility-ABC` (i.e. it contains `Facility-ABC` in asset.path).  I think this would require us to use the nested filter unless the total number of assets that were below Facility-ABC was small enough to pass them directly into the filter.  I can imagine that this kind of filter is more difficult to implement and a more expensive operation, but I think it could be valuable. Is there a reason why containers rather than views must be used when creating/querying records?  It seems like a view with a specific version is nothing more than a set of containers with a (possibly incomplete) list of

All,We’re readying a release of the OPC UA Extractor with support for the Records API and are looking for help with testing data flow of OPC UA events/alarms to CDF Records. The extractor creates containers for several different OPC UA event types and will be able to store data in either mutable or immutable streams (as specified in the configuration file for the extractor)Please reach out - feel free to email me at thomas.sjolshagen@cognite.com and let me know if you’re interested in testing the new extractor).Also, keep in mind that we have support for Records as a target and source in the Hosted extractors for CDF, so let me know here if you’ve got questions about how to use the hosted extractor for the purpose of onboarding relevant data to Records.

“I’m using cognite/opcua-extractor-net as container.Is there a docker image version for linux/arm64 platform available ? (not present on docker hub)”

hi guys,  can you please tell me the reason of the error below while API testing in Postman:any help is very much appreciated 

Hello,I am using OPC UA extractor to bring in sensor data in my cdf project. I want to limit the number of tags I am bring in from the source. I observed that in the PI extractor there is capability to include or exclude tags. Is there a similar filtering capability in OPC UA Extractor?

Hello,I am testing streams and records in one of our projects, but I am getting “The user does not have any ILA streams capabilities.” error.I am also not able to add the capabilities for Streams and Records to my user group as I cannot see them in the capability type list 

If I want to establish a relationship between a specific data model (not the core or enterprise model) and assets like a "function location," Do I  necessarily need to bring all the views from the core or enterprise models into your domain data model?The goal is not to extend the core model but to create a reference from my domain data model to the asset, possibly using node_reference.For instance, if I have an inventory and want to relate materials to a local storage (which is represented as an asset in the enterprise data model), could I define a property in my domain model that references the enterprise asset.Example:graphqltype StorageLocation { location: String plant: CogniteAsset # Reference to the asset in the enterprise model } In this case, I am just creating a link between my domain model and the asset without needing to extend the enterprise model or bring its full view into my domain model , works? 

Hi all,I am building a solution model on top of  a domain model we already have in place for a project.The domain model contains all the instances we have in the project, but this consumer is only interested in a subset and would like some filters in place to ensure that they are only getting the subset of interest. One of the requirements is that a certain property is according to their project standards and has a minimum length for a property. I see that there is a Range filter to check if a numeric property’s value is within a specified range, but is there any way I can add functionality to get the values length for this property?

I have the following question regarding Containers,  Spaces and Instances. Let's say I have a Container named Well in the space A and all its instances are created in space B. When I delete container Well in space A and recreate it (because I want to change a column name for example): Does instance in space B are deleted as well? If they are not deleted, If I rerun the transformation to populate the new container again in space B with the new schema (same external_id) what state should I expect my instances to be in ? A merge of old and new schema? What is the best practice ? To delete container in its space and its instances in all spaces also? Thank you!  

This might be a basic question, but I often find myself uncertain about when to use CogniteDescribable in data modeling within Cognite Data Fusion.For example, let's say we have domain tables in our data model, such as MaterialType, which contains data from SAP and defines the types of materials we work with (e.g., code and description). In this case, would it be appropriate to implement CogniteDescribable to reuse common properties like name and description?What are the advantages of doing so? Does using CogniteDescribable provide any specific benefits—such as improved performance through indexing or partitioning—when used it containers?In summary, should I always use CogniteDescribable in these types of scenarios, or are there cases where it's better not to?

 I have created 1 workflow , in which I am creating dynamic tasks depending on input, it creates batch of ids and create tasks out of it. Below is workflow definitionWorkflowVersionUpsert(   workflow_external_id="test_dynamic-0729",   version="1",   workflow_definition=WorkflowDefinitionUpsert(       description="This workflow has two steps",       tasks=[           WorkflowTask(                external_id="test_sub_tasks",                parameters=FunctionTaskParameters(                    external_id="test_sub_tasks",                    data="${workflow.input}"                ),                retries=1,                timeout=3600,                depends_on=[],                on_failure = "abortWorkflow",            ),           WorkflowTask(                external_id="test_create_sub",                parameters=DynamicTaskParameters(                    tasks="${test_sub_tasks.output.response.tasks}"                ),                name="Dynamic Task",                description=

I’m using n8n AI agent builder to query CDF via an http request. The body of the request is:The request URL is https://westeurope-1.cognitedata.com/api/v1/projects/essc-sandbox-44/events{ "filter": { "startTime": { "min": 1751070336000, "max": 1751588736000 }, "dataSetIds": [7726848970162689] }, "limit": 1000}CDF seems to recognize the datasetid filter but not other filters like starttime as shown or others like Types. The result set returned is all events in that datasetid.I’ve also tried minstarttime and maxstarttime.ideas?  

Hi All,We are encountering an issue after uploading E57 point cloud files into Cognite Data Fusion (CDF). The rendering quality of the images is quite poor, and we're unsure if we're making a mistake during the upload process.Has anyone else experienced similar issues? If so, do you have any solutions or recommendations to improve the image quality for point cloud in CDF?Please feel free to share your insights and suggestions.Thank you!

hello guys, I wonder how do you populate data model directly from the dataset? so i have ingested all my timeseries data into my dataset and then i want to run transformations using this dataset as a source but how do i get the actual values from the data points and can you filter just to extract certain timeseries data? this is the query i am running at the moment: select  cast(`externalId` as STRING) as externalId,  cast(`name` as STRING) as name,  cast(`description` as STRING) as descriptionfrom  `_cdf`.`timeseries`; what i want really is to import all my timeseries data from my dataset into my data model and then continue building. 

Hi,We have just rolled out “mutability” support for the Records API service. Mutability is the ability to change a record once it has initially been written to the Records API service.Enabling mutability for a stream requires using the settings.template.name key in the payload of the creation request for a stream. I.e. submitting a POST operation to the /streams endpoint, with - for example - the following body:items: [ externalId: "a-mutable-stream-1", settings: { template: { name: "MutableTestStream" } }] There are two supported “mutable”stream settings templates: “MutableTestStream”, and “MutableLiveData”.To update or create a record in this stream, you must use the newly introduced upsert endpoint in the Records API and specify the required identifiers of the previously ingested record you’re wanting to update.Over the next couple of weeks, we would love it if you could spend some time familiarizing yourself with mutable streams, and test record updates to he

I have a question about contextualization.In my setup, I have a functional location with a machine, and under the machine, there's a sub-station. When I contextualize a document related to the sub-station, why isn't it directly linked to the machine level and the functional location? I understand that I manually contextualize it to the specific station, but since the station is part of the machine and the functional location, it should appear there too.I think there's a missing link in my data modeling between the functional location, machine, and sub-station. What methods can I use to ensure that when I contextualize a document, it shows up at all levels of the hierarchy linked to that machine?

We intend to effect 3 breaking changes to the Records API over the next couple of weeks of the Private Beta program. These changes may require updates of your test procedures. /streams API “settings” attribute will be required Summary: Modifying the Cognite Streams API.From when: After July 15, 2025Description:The Streams API provides a broad spectrum of functionalities, but it's important to understand that these capabilities are not mutually exclusive; enhancing one often means adjusting another. For instance, if a stream is designed for permanent data storage, it will offer unlimited record retention but a lower maximum ingestion rate. Conversely, streams built for temporary data staging will support significantly bigger ingestion rate but only for a brief retention period. Similarly, you'll choose between mutable streams (allowing record changes) and immutable streams (optimized for high volume and speed).Because of these crucial distinctions, it's essential for users to be fully a

Hello, We are considering storing a relational database table with more than 100 columns as Records.Since the maximum number of properties per container is 100, we need to define a single table across two or more containers.In this case, I would like to know how to write a query that allows us to freely filter records that have properties defined across multiple containers.Our goal is to query the Records data in a way similar to executing SQL on the original RDB table with over 100 columns.Based on my testing, the behavior was as follows, which is not what I intended:When using only properties from container A in the filter or sort: only records of properties from container A are retrieved. When using properties from both container A and container B in the filter or sort: an empty JSONL is returned.If this cannot be resolved with a single query, I would appreciate advice on what kind of post-processing could help achieve the desired result.

i want to take export of one table to another table but facing this datatype error .also tried with multiple datatype (like string , float and Bigint ) still same issue is coming.