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.

If the user views a root cause Record, then the form rules will kick in regardless of how the user found their way to the record, so yes, your form rules will work.

Sorry, this is my first time using forms, tables and using Quickbase.

Will this allow the user to add a new record in root cause form and access that same record with ability to edit through the damage parts table? So far I seem to have everything in place but the accessibility to the record that was added in Root Cause.

If you have a Report link field on the damage parts table and choose to show the root cause records directly on the form, then you also get a choice as to whether that embedded table is editable. That is a setting on the form property for that report link field.

If you make that editable, that means that when you edit the damage parts record the root causes become editable as well in what is called the grid edit format.

However if you have form rules they will not be applicable in grade edit format, and also of course there is a realistic limit to how wide you would want to make that embedded report in terms of the number of fields.

If you have a complicated root cause for him with many fields then it will be more practical to have the users click the pencil icon on the embedded report on the damage parts record and edit on the full form.

Just to confirm, can you confirm that you do in fact have an a better table of the root causes with the records directly showing on the damage parts record?

That's essentially what I did here. This is a child table (Damage Parts) embedded in the parent form (Damage). At the end to the right "Add Investigation" is the button link to the grandchild form (Root Cause). I want to avoid adding root cause fields since the table is already too long and I don't want those fields visible to all users.



Workflow direction example Damage >> Damage Parts >> Root Cause

Was that a question?

Is there a function I can add to the formula you provided that will allow a user access to the root cause record created by the add button? After a record is added I want to disable the user from adding multiple records to the same row and only allow access for editing the record that was created.

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 Incident];

 

$URLONE

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

You make make a summary of the minimum of the Record ID# of the root cause record.  Call it [Record ID# of the Root Cause]

Then change the button to this (not tested)

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 Incident];

var text ADD =  

$URLONE

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

var text EDIT = URLRoot() & "db/" & [_DBID_ROOT_CAUSE] & "?a=dr&rid=" & [Record ID# of the Root Cause];

IF([Record ID# of the Root Cause]>0, $EDIT, $ADD)

I've created "Record ID# of the Root Cause" and made it a summary in (Damage Parts) Table and I have updated the formula in the add button. Everything seems to take, but after creating a root cause record the button does not allow me to edit and does allows me to keep adding records. Is the If statement for the edit/add part of the formula for the button? I have included that as well.

Please post your formula

Also, two more things.  Where do you want to leave the user after they save the root cause edit?

Also if you want to land the user on edit mode on the root case, this line needs to read as below (er instead of dr,   (er means edit record.  dr means display record)


var text EDIT = URLRoot() & "db/" & [_DBID_ROOT_CAUSE] & "?a=er&rid=" & [Record ID# of the Root Cause];