Forum Discussion
MarkShnier__You
Qrew Legend
5 years agoIf you truly have a one to one relationship, it begs the question as to why bother. Why not just have one table with all the fields on one table.
But if you like you can set up an Automation to trigger on Creating a Place, to create a child Restaurant. Linked to the Parent Place.
------------------------------
Mark Shnier (YQC)
Quick Base Solution Provider
Your Quick Base Coach
http://QuickBaseCoach.com
mark.shnier@gmail.com
------------------------------
But if you like you can set up an Automation to trigger on Creating a Place, to create a child Restaurant. Linked to the Parent Place.
------------------------------
Mark Shnier (YQC)
Quick Base Solution Provider
Your Quick Base Coach
http://QuickBaseCoach.com
mark.shnier@gmail.com
------------------------------
Francesco_Achil
5 years agoQrew Member
Hi Mark,
thank you for your answer, in the end I went with a single table like you suggested and I'm conditionally showing the fields I need, although I'm afraid this approach may not scale up very well once I get lots of different "subclasses" with associated fields.. but it seems indeed the easiest way to integrate into quickbase.
I discarded the automation way because I found no way to create "empty fields" on a form to fill up record created by the automation.
------------------------------
Francesco
------------------------------
thank you for your answer, in the end I went with a single table like you suggested and I'm conditionally showing the fields I need, although I'm afraid this approach may not scale up very well once I get lots of different "subclasses" with associated fields.. but it seems indeed the easiest way to integrate into quickbase.
I discarded the automation way because I found no way to create "empty fields" on a form to fill up record created by the automation.
------------------------------
Francesco
------------------------------