Hie @vishsahu
Another quick one. I have realised if one creates a parent child relationship with all collections relevant or linked to the user collection, one ends up with an extremely bloated User Collection with dozens of fields. Is it possible to just make the relevant collection point at the user collection without having to have a field in the User Collection pointing at the reference or would be child collection? Not sure if i have explained it well.
Thanks
Hi @WillieMak,
You can create a reference field without creating a parent child relationship easily.
Thanks.
Hie @vishsahu . Ok but in what special cases are parent-child relationships absolutely necessary in Drapcode? I have watched some of your tutorial videos where you use parent child relationships and I assumed it is necessary and straightforward to say a User has many child collections because the records belong directly to them and are specific. e.g a business, a listing, educational records, address, social media etc. Sorry, i really struggle working with filters because I sort of understand that I will need to use filters to isolate a users records when calling for them in the UI.
Thanks
@WillieMak If it is must have, then you should create them as that is the whole purpose.
Only scenarios to avoid this relationship is when you are expecting the parent to have 100s of childrens, then it does not make sense. If the no of possible children are limited, then go ahead with it.
Ex: Person has many addresses (in this case it is good to have parent child, as the no of addresses are limited).
Bank Account has many transactions ( in this case it is bad, as a bank account can have 1000s of transactions)
Thanks.