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()
ScottMarks
7 years agoQrew Member
Hmm actually you're right. My mistake.
Perhaps you could redirect to a code page that takes the rid url param, as well as dbid and use some javascript to run a call after the fact with the current time.
I think that should work, I'll see if I can setup a demo.
Perhaps you could redirect to a code page that takes the rid url param, as well as dbid and use some javascript to run a call after the fact with the current time.
I think that should work, I'll see if I can setup a demo.