Forum Discussion
QuickBaseCoachD
Qrew Captain
Elisha, there is possibly an easier solution.
Your "add record" can specify where to go to upon Save. ie the NextURL.
var text ADD = URLRoot() & "db/" & [_DBIDxxxx] & "?API_GenAddRecordForm&ifv=1":
var text RedirectTo = the url to redirect to;
$ADD
& "&NextURL=" & URELEncode($RedirectTo )
Your "add record" can specify where to go to upon Save. ie the NextURL.
var text ADD = URLRoot() & "db/" & [_DBIDxxxx] & "?API_GenAddRecordForm&ifv=1":
var text RedirectTo = the url to redirect to;
$ADD
& "&NextURL=" & URELEncode($RedirectTo )
TateForgey
6 years agoQrew Assistant Captain
Thanks, Coach. Let's start with the code that is your response here. Is this a button you would put on a dashboard? That API is going to generate the form to add a record, right? So, it seems like it doesn't make sense to put it on a record, but maybe I'm wrong about that.
I'm looking for a situation where I open the edit view of a record, then someone edits the record and I replace the save button with a button that saves and redirects to a rich text page I have created. Is this type of code the way I would do that?
I'm looking for a situation where I open the edit view of a record, then someone edits the record and I replace the save button with a button that saves and redirects to a rich text page I have created. Is this type of code the way I would do that?