Impact 2024: The Industrial Data and AI Conference for and by Users | Nominate Speakers Now for a Ch...
The GA release will not include an updated Power BI connector that supports data from FDM, but this is planned later on. Will keep this thread updated.Anders
The externalId is the id of an instance (a node) which may have multiple types attached to it. A node can both be Equipment and Pump. In FDM, nodes exist in a space, and all externalId’s have to be unique within a space.
Hi,Tooling to smooth importing of RDFs is on the roadmap, but it is likely that FDM will not have a 1-1 mapping to RDF so SPARQL would work directly on it. We have already done some nice work in this area that we can discuss. However, I’d love to sit down with you to learn more about the ontologies you want to represent in FDM. This is definitely an important topic for us.
I’ll shine some more light on this topic as well. FDM is designed to reduce the amount of data migration needed on non breaking data types even though the data model itself has a breaking change. One example would be that you remove a property from a type (leading to a breaking change). In this scenario, there is no need for any data migration as the other properties still point to the same physical storage. An example of a breaking change where data needs to be migrated is restructuring of physical storage, and change of data types (int → float for example). Here we have plans for making this a joyful experience later on, but at GA, the recommended way to solve this is create/update a CDF transformation that will handle it. I am very interested in having a session on what kind of breaking changes you expect so we ensure they are covered greatly from the product.
FDM is a new service, so no data you create there will appear as Assets. However, throughout 2023, we are planning to mirror Assets etc into FDM so you will find data both places.To populate data, you can follow the guide in the documentation. In the beta version, we have not opened the APIs for data ingestion, but this will be a public API once we reach general availability (GA) in the February release.If you want two data models to share the same equipment class, you will have to wait for GA, as it is not properly supported today. Data model types are independent today. The entity matching APIs can be used directly if you want to use it on data in FDM. The APIs assume no specific resource types, so you are free to use them as you wish. In 2023, we’ll update the UIs in fusion so you have the nice, guided experience too.
Hi,When you have two fields with the same target type, you would do exactly as if you have a single property. This is a part we have yet not put in the docs (coming very soon!), but the UI would help you create this transformation. But to also answer your question, assuming you have a RAW table with the columns frontPart, backPart and externalId (the first two would be external ids to the Part instances)Select array("datamodelexternalId", `frontPart`) as `frontPart`, array("datamodelexternalId", `backPart`) as `backPart`, string(`externalId`) as `externalId`from `database`.`table`;
Hi,Thanks for reaching out. Interfaces are not properly supported and should not have been added as a choice in the UI quite yet. When we reach GA, we fully support what you try to achieve here. So whatever you do with interfaces can go wrong in the beta version. Sorry about the inconvenience, and hope you will enjoy what we have to offer in a couple of months :)
Hi, I’ll follow up on @Jason Dressel’s comment. So the limits in the beta areBeta:max 2000 data model types in a CDF project, across all data models max 250 properties per data model type max 1000 data models max 1000 instances per request (+extra instances through relations)In GA, we will enforce the limit of 1) scoped to data model and not globally in the CDF project. The exact limits in GA are still TBD, but will be documented.
Hi, thanks for reporting this. This is absolutely true! We have decided to remove the CURL and Python example since this is possible to configure using the UI.Configuring ACLs will be added to the CLI tool soon.
This is a great idea! We are discussing this internally in the team. Will keep you posted here :)
Thanks for this great in depth explanation if your idea. The problem you describe is precisely why we are creating the data modeling capabilities with schema service. To be able to have a contract that an application can trust, and move the customization from the application layer to earlier in the data pipeline.Your idea here with an Application A contract that is being used by multiple CDF projects is great and is something we are working towards now. I’ll keep you posted on updates in this area :) Again, thanks a lot!
Thanks for the input. We are currently keeping our focus on the existing SDKs, but .NET is definitely on the list of potential future ones.
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.