I had run transformation giving me error for Duplicate node externalIds for space 'PDM' even after deleting all the data from the model for space PDM still giving the same error, I also verified by api still there is no data still giving the error for Duplicate node externalIds for space 'PDM' .
Hello Team,Not able to open the FDM from fusion ui on below url. Can you helphttps://slb.fusion.cognite.com/slb-pdf/data-models?cluster=westeurope-1.cognitedata.com&env=westeurope-1 Also when I hit below api its giving 500{{baseUrl}}/api/v1/projects/{{project}}/models/datamodels?inlineViews=trueResponse - { "error": { "code": 500, "message": "Unexpected state" }} Can you help on this ?
It seems I can create transformations for types but there is no option to select a relationship when creating a transformation to a data model. Below it shows the “Target type and relationship” dropdown only has types but not relationships. Is there anything I missing?
Below works and the data model is published.Data Model Version - 1type Employee @view(version: "1"){name: String}Next stepBelow doesn't work and I get an error "Can not change the nullability of the property\n We do not support modifying a field's 'required'ness at the moment."Data Model Version - 2type Employee @view(version: "2"){name: String!}
More of a design question: only interfaces are allowed after the implements keyword, so you have to know what types you plan to extend beforehand, but this is not always possible or reliable. Since interfaces also produce views, I am tempted to make everything an interface, but are there any downsides?
When adding a node instance with Float properties, it always gives an error “The value of property 'xxx' must be a 64 bit floating point number” if the value in the request body is 0 or negative number, but it works fine if the value is positive.Could you help take a look?
Hi,Let’s I have below data model created in FDM and there are 2 types Device and Sensor. Device is referring to other type Sensor. Device - name:String - sensors:[Sensor] Sensor - name:String - timestamp: Timestamp - value: Float I have populated the data through transformation in this model. I wanted to check on how to get the latest timestamp and value for particular device and sensor through FDM GraphQL query.Example:Device : d1Sensor:name: s1timestamp: 2023-01-01 01:00value: 10.0 name: s1timestamp: 2023-01-02 01:00value: 20.0 name: s1timestamp: 2023-01-03 01:00value: 30.0 I am expecting to latest timestamp as 2023-01-03 01:00 and value as 30.0
Is there a plan to support enumeration (or any way to restrict value of string properties) in the future?Enumerations are described here: https://graphql.org/learn/schema/, but seems like its currently not supported:
I'm sorry, I'm new to cognite and don't quite understand the basics. FDM is one specific model with data? And if I need several models (I mean models filled with data) with the same schema, then I need to create several FDMs and then transform the data into them?
When creating a transform into an FDM type, it is necessary to provide the externalId of the instance. Does the value of externalId need to be unique across all instances of all types in the model or only across instances of the given type?
Hi from HUB Ocean and the Ocean Data Platform. We are participating in the open ocean data cataloging scene, for instance through the EU ILIAD “Digital twin of the ocean” project.Home | Iliad - Digital Twin of the Ocean (ocean-twin.eu)In order to improve the interoperability between the myriad of ocean data portals, web services and data catalogues out there, it will be very important for the Ocean Data Platform data catalog to support technologies and concepts like RDF (Resource Description Framework), SHACL (Shapes Constraint Language) and SPARQL (RDF query language). Is this already supported by FDM or is it on the roadmap?
As we develop richer models supporting a greater variety of workflows, we have started asking questions about model maintenance and modularization. Decomposing large models into sub-models that have low coupling seems attractive, but would require some type of referential support across models. Is Cognite considering such a feature, or how do we envision managing complex models in general? As you are probably aware large models have an increased risk that a breaking change in a peripheral type will force a new version on the entire model. Since data must be manually migrated today, this creates a maintenance load that we would be keen to address.
Hello,I wanted to checkout on any upper limits for following if limit exists.Max no of Schemas that can be created in one Data Model in FDM Max no of fields that could be added in one schema Max no of Data Models under one project Also any other limits around the data size or count or number of records that could be fetched in one query or anything related in general if exists.Please help us out with these numbers, this would help us to plan accordingly!
Hi could you share an example of a transformation to load a type that has multiple links to another type? All the examples I’ve seen only set startNode and endNode but no place to specify which field. For example:type Composite { frontPart: Part backPart: Part}type Part { ...}
I created a data model that contains an interface (this is to allow polymorphism). When a type references the interface then the the Data Management table shows this error:It seems the UI relies on every reference to contain an externalId field, and that this field is implicitly defined for types but not for interfaces, as the GraphQL query returns with this error: "Validation error of type FieldUndefined: Field 'externalId' in type 'Twin' is undefined @ 'listEquipment/items/twins/items/externalId'"In the above Twin is an interface type, and Equipment contains a field which is a reference to an array of Twin.
The curl command suggested here needs quotes around all JSON property names, needs to use " instead of ', and needs trailing commas removed before curl will stop reporting invalid JSON payload.
Already have an account? Login
Enter your username or e-mail address. We'll send you an e-mail with instructions to reset your password.
Sorry, we're still checking this file's contents to make sure it's safe to download. Please try again in a few minutes.
Sorry, our virus scanner detected that this file isn't safe to download.