I have been reading a lot of @NigelG ’s posts on this matter over the last few days, and the following thread is what got me pointed in that direction. In it, @NigelG states:
The way you “tie” A Project to many Timeslips, and a Timeslip to One Project is by embedding a particular thing in the database record.
So the TimeSlip has a field of Type ProjectData, that gets set to a particular Project. Not the key or an Id, the whole thing.
Then he goes on to say:
What about the other way round, and here we finally get to your question !
Yes, we could probably sum up all TimeSlips for every unique project, but let’s make like easier for ourselves when querying the database, by making life a little more complex when we save the data.
So I add a field to the Project called Timeslips, and make it a list.
When I save the Timeslip, I also make a change to the Project to store this Timeslip’s thing on the Project in the List.
Forum
Academy
Marketplace
Showcase
Pricing
Features