Skip to main content
Question

Add two tables in one form and optionally using Default record picker

  • December 13, 2020
  • 0 replies
  • 35 views

I have two tables

Client, the parent
Problem, the child

What I would like to be able to do, and haven't been able to figure it out yet, is 

When a client adds their own problem via a form on the internet, they add both their client information and their problem in a single form with a single (preferred) submit.  For privacy reasons, we don't want to display any existing client information when the problem is entered via the internet (yes, we could end up with duplicates).

When an employee adds a problem on behalf of a client (via intranet), the employee can take advantage of the default record picker to select the correct client and then add the problem.

The forms will look different as different client information may be collected based on the origin of the form (ie, internet or intranet).

Can two tables be added/updated in a single form/submit?

Can the default record picker behavior be turned on/off for the parent via the form?

------------------------------
Katherine Oakey
------------------------------
This topic has been closed for replies.

MarkShnierYou
Forum|alt.badge.img+22
  • Quickbase Alumni
  • December 13, 2020
There are a variety of solutions.

Here is one.  The internet users are not experienced Quick Base users so it has to be stupid simple and need to enter their client info and the problem on a single form.

I suggest making an EOTI Client form (to be used on the Role Everyone On The Internet), where they fill out the Client information and also you will include fields for the child information, right on the Client form.  The form would not have a field for [Related Client]

I would then set up an Automation to fire, when the "Problem Description" field on the Parent Client record was not blank which would create the Child problem record.

Internal staff would be notified of new EOTI Client entries and look to see if the client already exists.   If the client does exists, then they would edit the child problem record and attach it to the previously existing Client record, leaving the EOTI Client record childless.  That record should be flagged as "archived" to keep it off reports and drop down choices for new problems. 

If the client record is a bone fide new Client record, it would remain, and you might want to clear out the problem information entered on the client record or hide that section of the form based on a form rule and a checkbox.


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