When is this not Required? Save parent record automatically when a child record is created.

Warning: Rant follows.

If there is a use case, it's certainly the "edge cases" like 1% of the time.

imho it hurts the new user experience to not default this for new apps and new tables.  For us old dogs just makes us feel stupid when we forget to check the box for a new table which then ends up being used as a Parent table. For all the work that Quick Base does to try to make the new developer experience more friendly, such as the New Drag and Drop App design interface, this small change would make a huge difference to the New User experience and hence the stickiness of new Quick Base prospects on a 30 day trial.

The checkbox's behavior should be changed to default to checked on newly created tables in all interface methods of creating a new table.

------------------------------
Mark Shnier (YQC)
Quick Base Solution Provider
Your Quick Base Coach
http://QuickBaseCoach.com
markshnier2@gmail.com
------------------------------

One issue we have noticed is the following:
1. add new parent
2. add new child from parent
parent prompts to save
3. click yes
taken to new child
4. complete child and save
does not return to parent
user clicks browser back button to return to parent
when user arrives at parent, save prompt is displayed, user clicks save

result:
second parent is created

expected:
user is returned to parent upon save of child

------------------------------
Jim Harrison
------------------------------