Creating a child record from a button on the parent form and automatically returning back to the parent form after the child record has been saved.User is on parent form and adds a record to the child form through a button. Is there a way to automatically return back to the parent form after the child form has been saved? If not, it there a way to indicate on the button that a child record has been created for the parent record by changing the color of the button? This is my existing formula URLRoot() & "db/" & [_DBID_ROOT_CAUSE] & "?a=API_GenAddRecordForm&_fid_17=" & URLEncode ([Record ID#])& "&z=" & Rurl()Thanks All,Evan

Evan, That is very odd, because your button looks quite normal and the bit at the end with the &z=... tells QuickBase to redisplay the Parent record after saving. Is there anything else unusual here in your setup. I can provide an alternative to that code which would probably work, but I'm not understanding what is different about your use case where the normal Add child button is not returning to the Parent. What is happening now after you save the child?

I see what you mean. Yes it does return back. Sorry for the confusion, I explained my setup incorrectly. I have a parent form that has a child table inside it with a button that leads to the grandchild. Is it possible to return back to the parent form after the grandchild record has been saved? Is there also a way to indicate on the button that a grandchild record has been created after it's been saved? I need an indication to avoid saving multiple records related to the same record. Thanks so much for the help!

OK, now it makes sense. The magic is using "&NextURL= ....No problem,var text URLONE = URLRoot() & "db/" & [_DBID_ROOT_CAUSE] & "?a=API_GenAddRecordForm&_fid_17=" & URLEncode ([Record ID#]);var text URLTWO = URLRoot() & "db/" & [_DBID_the table name of the parent] & "?a=dr&rid=" & [Related Parent];$URLONE& "&NextURL=" & URLEncode($URLTWO)I am using formula variables for readability and when you link the next thing for QuickBase to do, you need to URLEncode it. Not sure why, but that's the syntax to make it work.

i did update the fields and I am now receiving the error "Formula syntax errorThere are extra characters beyond the end of the formula."URLRoot() & "db/" & [_DBID_ROOT_CAUSE] & "?a=API_GenAddRecordForm&_fid_17=" & URLEncode ([Record ID#])& "&z=" & Rurl() var text URLONE = URLRoot() & "db/" & [_DBID_ROOT_CAUSE] & "?a=API_GenAddRecordForm&_fid_17=" & URLEncode ([Record ID#]);var text URLTWO = URLRoot() & "db/" & [_DBID_DAMAGE] & "?a=dr&rid=" & [Related Damage Parts Incidents2 - Related Incident];$URLONE& "&NextURL=" & URLEncode($URLTWO)Am I missing something?Thanks for your help!

//You just need this part. this replaces your original formula. var text URLONE = URLRoot() & "db/" & [_DBID_ROOT_CAUSE] & "?a=API_GenAddRecordForm&_fid_17=" & URLEncode ([Record ID#]);var text URLTWO = URLRoot() & "db/" & [_DBID_the table name of the parent] & "?a=dr&rid=" & [Related Parent];$URLONE& "&NextURL=" & URLEncode($URLTWO)

Creating a child record from a button on the parent form and automatically return back to the parent form after the child has been saved.

55 Replies

QuickBaseCoachD
Qrew Captain
8 years ago
The problem is the the URLTWO

var text URLTWO = URLRoot() & "db/" & [_DBID_DAMAGE] & "?a=dr&rid=" & [Related Damage];

Stop and think about where is the user is when they push this button. They are sitting on a damage parts record. The record that you want to display is in the table above that which is called damage. The record ID that you want to display in the damage table is in fact the parent of the damage parts record. And that record ID is likely called [related damage].
EvanFujikawa
Qrew Cadet
8 years ago
Yes! That was the trick!!!

Now, instead of enabling the user to create multiple Grand Child Records (Root Cause) through the button, is there a way to disable the button from adding multiple records after an initial record has been created and possibly indicating on the button such as a color change to tell the user a record has been created? Essentially I just want the user to edit the original record through the button instead of creating new records.

Your help is greatly appreciated!!
QuickBaseCoachD
Qrew Captain
8 years ago
no problem,
you can make a summary field of the [# of root causes] on he relationships between damage parts and root causes.

Then instead of where it says

$URLONE
& "&NextURL=" & URLEncode($URLTWO)

replace that with

IF([# Root Causes]=0,
$URLONE
& "&NextURL=" & URLEncode($URLTWO))

The button will be blank after the first one is added.
EvanFujikawa
Qrew Cadet
8 years ago
This works great, but now the button disappears disabling any link to the created record. Is there a way to keep the link accessible in cases where the user needs to edit the record?

thanks!!
QuickBaseCoachD
Qrew Captain
8 years ago
I don't understand.

The purpose of the button was to add a new record, not to edit an existing record. If the user needs to edit the record they should just edit the record with the edit pencil icon.
EvanFujikawa
Qrew Cadet
8 years ago
I needed to create an add button because I want to limit the access to only a few tables. The user only has access to the "Root Cause" form through the parent form "Damage" which is accessible only through the add button.
QuickBaseCoachD
Qrew Captain
8 years ago
Why not have a child table of the root cause on the damage parts table?
EvanFujikawa
Qrew Cadet
8 years ago
If I create a child table (root cause) on the damage parts table, will this require me to show all the field criteria on the table or can I have a button that will link the user directly to the form for editing?
QuickBaseCoachD
Qrew Captain
8 years ago
When you put th Report Link field type for the ROot Cases in the Damanage Parts form, you can specify that the child records ( just one record in your case) should appear directly on the form in a report. You may them create an unfiltered report to use to decide which columns (fields) of the rooot causes, you want to show to the users.

Users can then choose to either view the root because or edit it.
EvanFujikawa
Qrew Cadet
8 years ago
I do have several form rules setup on for my Root Cause form. Will these also work through a report link?

Forum Discussion

Creating a child record from a button on the parent form and automatically return back to the parent form after the child has been saved.

55 Replies

Related Content

PDF Document Generator, automatically attached to a record

create pipeline to create new records based on current record

Create child records from Parent List - User field

Pipeline - Add Year from Record Created to a field

Add button to create record in different app