When is this not Required? Save parent record automatically when a child record is created.
------------------------------
Jim Harrison
------------------------------
Forum Discussion
------------------------------
Jim Harrison
------------------------------
11 Replies
- MarkShnier__You
Qrew Legend
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
------------------------------- Can you explain to me the benefits of having this checked on every table? In the app I work in I would say that pretty much none of the tables have this checked. What are we missing out on by not having it checked on a table that is the parent to many?
Everyone that posted here talked about how they wish it was the default but didn't go into why it should be. Not everyone is going to just "get it" and I am in that group myself here. Maybe I am missing something simple.- MarkShnier__YouSo when a user is filling out a parent form what they expect is to work their way down the form, say a New Client form, and fill in the boxes. Then they get to the button that says Add Child, (say Add Contact - one client has many contacts). So they just expect to keep working by clicking that Add Contact button.
But if you do not remember to check that box, then they get this most confusing pop up asking if they want to save their data. Well duh, of course they want to save the data that they just laboriously filled in all the boxes on the form, and now they are ready to add a contact.
By checking the box, the system behaves arguably "properly", auto saves and then the user continues with adding their child (say contact info).
------------------------------
Mark Shnier (YQC)
Quick Base Solution Provider
Your Quick Base Coach
http://QuickBaseCoach.com
markshnier2@gmail.com
------------------------------
- Mark,
Myself and many I have spoken to concur that this should be default behavior of Quick Base when building a table.
I also believe every relationship should have a default-summary "count" of child records too.
------------------------------
Laura Thacker (IDS)
laura@intelligentdbs.com
(626) 771 0454
------------------------------- MarkShnier__YouMaybe our moderator, Evan, has an idea of who to pass a link to this discussion to at Quick Base. Someone responsible for the New User Experience, perhaps. i know there is User Voice as a channel, but this is one that mainly benefits New Users, who would not even understand the issue let alone figure out how to vote for it.
------------------------------
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
------------------------------- Hi Jim,
I have seen the same before and it crops up due to the parent record not having a Record ID at the time the save happens. One thing I have done in instances like that is to either make a button that appears on the child record after it is saved that says "Back to Parent" that is nice and prominent that uses the Related Parent field to take the user back to Parent Records or I have changed the standard redirect to instead drop you on the parent table homepage after using that button to create a child record from the Parent record to bring the user right back to the parent table at least even when a record didn't have a Record ID at the time the button was hit.
------------------------------
Evan Martinez
Community Marketing Manager
Quick Base
------------------------------
