Hi all,
I have a question regarding the use of nested attributes from linked objects when defining indexes.
In my model, I have an object Cement that has a direct link to another object called ScenarioContent.
I would like to use the attribute ScenarioContent.Type as part of the index on the Cement object.
This is particularly useful, because I use views that filter Cement instances based on ScenarioContent.Type.
For example, to expose only planned scenarios, I use the following rawFilter in a view:
@view(
rawFilter: {
nested: {
scope: ["Cement", "ScenarioContent"]
filter: {
equals: {
property: ["ScenarioContent", "Type"]
value: "PLANNED"
}
}
}
}
)
Question:
Can I use this nested attribute (ScenarioContent.Type) in the index definition of Cement?
If this is not currently supported, is there a recommended alternative to support performant queries on this kind of filter?
Check the
documentation
Ask the
Community
Take a look
at
Academy
Cognite
Status
Page
Contact
Cognite Support