But I only get 1 object from the 1:N relations. Is that normal?
Alternatively I can load table by specifying properties and relations depth. However I would need a sequence of complex nested IF/else statements to check if each relation needs updating (if the related object exists, if the relation has changed, etc.)
What is the best way to check objects with relations versus an external list and then update them?
When you specify a list of properties, you get them as property values rather than related objects. If you need to get the related objects, you need to use either the relations connector or the relations depth connector.
I have an additional question on getting a list of properties from related objects
If we take a schema example like the above, and I am loading the Tutors table (which is a child of Students, in turn a child of Parents), is there a way to load properties of a parent related object?
I know that if I am loading the parent table, I can include child table properties with, for example subjects.tutors.tutor_name, but is there a way to go the opposite way around? From child to parent?
Strangely, if I try to retrieve the parent objectId together with the child objectId, it will not do so. Any other field is fine. If I do each separately, it is also fine (eg. parents[slots].objectId works on its own). But the combination only gives one objectId.