Forum Discussion
ScottMarks
7 years agoQrew Member
You could always have your API call redirect to ANOTHER API call that then modifies the end time with Now(). That way, no matter how long someone is on the page, the Now() is always called on the second half and is always "up to date".
//First section of your API call that changes record values n such, Now() is not included in this part..
URLRoot()&"db/"&Dbid()&"?a=API_EditRecord&rid="&[Record ID#]&"&apptoken=xxxxxxx&<DO YOUR STUFF HERE FIRST>
//Second section which executes the NOW() function, which has been "refreshed" in a second api call.
&"&rdr="&URLRoot()&"db/"&Dbid()&"?a=API_EditRecord&rid="&[Record ID#]&"&apptoken=xxxxxxx&_fid_19=Now()
QuickBaseCoachD
7 years agoQrew Captain
Scott, that won't work.
If you did that formula and exposed the code, you would see that it is all resolved into a text string URL and the second Now() is immediately populated.
I'm still liking the Action method, myself. Trigger an Action to do the update if you really need the Now() time.
If you did that formula and exposed the code, you would see that it is all resolved into a text string URL and the second Now() is immediately populated.
I'm still liking the Action method, myself. Trigger an Action to do the update if you really need the Now() time.