Impact 2024: The Industrial Data and AI Conference for and by Users | Nominate Speakers Now for a Ch...
Hello from the Solutions Portal team!We have a new release coming, which is by far our largest release yet! We hope this release will make it easier toBrowse through your data inside your CDF Project Enable new solutions built on top of CDF Enable new no code solution possibilities We have a new home screen with new functionality!Any user can now ‘Browse solutions’. Through here, you can view all solutions that Cognite has to offer. If they’re not enabled, a demo can be requested. If you are an admin, SOME applications can be installed through a wizard for free (today, blueprint) and some are automatically installed (Charts).An explorer designed for SMEs. We’ve taken the old ADI explorer, made some improvements based on feedback, and now have an early version out for early adopters.An early version of global search is included also - easily search your way through any CDF resource (with more resources to come!) New CDF application: Blueprint!Blueprint is a no code solution that allows
As an application developer, a very common interface to build is filtering user interfaces. There are a few types of aggregation that would be very useful to us! #1 Unique value aggregationIn order to allow for effective filtering, aggregating a field by all its unique values is vital for this, to enable showing the user all possible options for a certain filter.Generally the amount of results can be limited to perhaps 1000, but having this paginate (or a higher number of 10000) would be even better! This also allows us in many cases to avoid needing expensive ‘substring queries’ on fields, as doing this in the front end on several thousand strings is trivial. Not all fields needs this, so if its required to add a `@aggregatable` decorator, then this is fine!In addition to this, having the amount of each of these values would be useful, to allow us to sort by the most commonly occurring fields.This is by far the highest priority for our use case! #2 Count aggregationSecond most importa
Hei!In the current schema setup, I might make a query such as this:The terms ‘edges’ and ‘node’ is a bit confusing to me. I’m not sure what they really mean in this context (I understand it from a graph db point of view, but its a bit confusing from other points. I might expect something like this instead{ listAsset() { items { externalId } pageinfo { cursor, ... } }} Curious to hear your thoughts on this :)
The @searchable field is a great addition! Fundamental for certainThe final point to make it usable for us will be to allow the user to select what searchable field they want to be able to filter on. e.g. given the schematype Equipment { name: String @searchable @filterable description: String @searchable @filterable} Its very common that the user will know that they want to search on specifically name or description.
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.
Check the
documentation
Ask the
Community
Take a look
at
Academy
Cognite
Status
Page
Contact
Cognite Support
