Check the
documentation
Ask the
Community
Take a look
at
Academy
Cognite
Status
Page
Contact
Cognite Support
type Employee {
name: String!
department: Department!
}
type Department {
name: String!
}
I can't model a use case where an employee must belong to a department.
Solved
Unable to model a direct relationship as required field in a view using UI
Best answer by Dilini Fernando
Hi
I hope Anders’s reply was helpful. I’m closing this topic now, please feel free to create a new post if you have any questions.
Br,
Dilini
1 person likes this
Correct. As of today, we don’t support required relation fields like that.
Being able to ensure that an employee will always belong to a department is a very common use case in data modeling.
There is no workaround. The reason is the following:
If node X is in space A with a reference to node Y in space B.
If I delete my node Y, but don’t have access to delete your node X, what should happen?
I definitely see the use case, but we will not have a solution for this on the short term.
+2Hi
I hope Anders’s reply was helpful. I’m closing this topic now, please feel free to create a new post if you have any questions.
Br,
Dilini
Reply
Rich Text Editor, editor1
Editor toolbars
Press ALT 0 for help
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.