Forum Discussion
_anomDiebolt_
8 years agoQrew Elite
Here is a novel solution to your original question which employs a new technique I call Three Tables and a Form.
Here are the three tables and the fields I choose for the demo:
Opportunity
[Date]
[Source]
[Assigned To]
Company
[Company Name]
[City]
[State]
Contact
[Contact Name]
[Phone]
[Email]
There is also a fourth table which has all of these fields. We are never going to save any data in this forth table we are just going to hijack its add record form. Sounds crazy I know but this is Earth in early 2018 and QuickBase technology has yet to evolve to the point where one form can feed multiple tables in the fashion you want.
Here is the application
Three Tables And A Form
https://haversineconsulting.quickbase.com/db/bnffhvwjf
You can fill out one form using this form in the Onboardings table and upon saving you will be redirected to the display of the new Opportunity record which shows the newly created child Company and Contact records.
New Onboardings
https://haversineconsulting.quickbase.com/db/bnffh2xnk?a=nwr
Pastie Database
https://haversineconsulting.quickbase.com/db/bgcwm2m4g?a=dr&rid=619
Notes:
(1) I forgot to bind bottom Save button on the form so just use the upper button (easy to fix but I am lazy)
(2) This type of form is most appropriate where speed of data entry is the most important factor. If verification, extensive form rules or other factors are present that increase the navigational load you are better off using standard techniques.
(3) To seamless navigate away from the new record form we have substituted the Save button click handler and eliminated the unload proc that normally warns you that you are navigating away from a partially filled out form.
Here are the three tables and the fields I choose for the demo:
Opportunity
[Date]
[Source]
[Assigned To]
Company
[Company Name]
[City]
[State]
Contact
[Contact Name]
[Phone]
[Email]
There is also a fourth table which has all of these fields. We are never going to save any data in this forth table we are just going to hijack its add record form. Sounds crazy I know but this is Earth in early 2018 and QuickBase technology has yet to evolve to the point where one form can feed multiple tables in the fashion you want.
Here is the application
Three Tables And A Form
https://haversineconsulting.quickbase.com/db/bnffhvwjf
You can fill out one form using this form in the Onboardings table and upon saving you will be redirected to the display of the new Opportunity record which shows the newly created child Company and Contact records.
New Onboardings
https://haversineconsulting.quickbase.com/db/bnffh2xnk?a=nwr
Pastie Database
https://haversineconsulting.quickbase.com/db/bgcwm2m4g?a=dr&rid=619
Notes:
(1) I forgot to bind bottom Save button on the form so just use the upper button (easy to fix but I am lazy)
(2) This type of form is most appropriate where speed of data entry is the most important factor. If verification, extensive form rules or other factors are present that increase the navigational load you are better off using standard techniques.
(3) To seamless navigate away from the new record form we have substituted the Save button click handler and eliminated the unload proc that normally warns you that you are navigating away from a partially filled out form.