I need to check a date/time field is "before now",...
# suiteanalyticsn
NElliott
07/03/2019, 8:10 AMI need to check a date/time field is "before now", I will be doing this in code but want to avoid using a javascript date object as I'm seeing unexpected results.
Can anyone advise, through the UI is fine, what I can add to the criteria to check this please?
(cannot be "before today" has to include the time.
Thanks.
b
battk
07/03/2019, 8:33 AMyou can try converting them both to dates so that when you subtract them, you get a number
battk
07/03/2019, 8:34 AMid rather try and get the javascript date working rather than do something ugly with formulas
n
NElliott
07/03/2019, 9:01 AMNo, not's not what I mean. I have a scheduled script runs every 15 mins. I only want results where the date/time on the records is "before now"
NElliott
07/03/2019, 9:02 AMI'm not looking for an ugly formula I'm hoping there's a before "now" like before "today"
NElliott
07/03/2019, 9:03 AM@al3xicon actually looks like you were doing something similar
a
al3xicon
07/03/2019, 1:15 PMhey @NElliott I was trying to calculate the time (hours) elapsed between a custom date/time field on a support case and "now" ({today})
al3xicon
07/03/2019, 1:16 PMso if you used something like that in your saved search criteria that drives your scheduled script, i'd assume it would work
al3xicon
07/03/2019, 1:16 PMit's just
({today} - {customfield}) * 24al3xicon
07/03/2019, 1:17 PMor should be anyway
al3xicon
07/03/2019, 1:17 PMbut for whatever reason it doesn't quite work with custom fields the way it does with native date/time fields, so you ave to wrap your
{customfield}al3xicon
07/03/2019, 1:18 PMand just use the same format for date/time, i used
MM/DD/YYYY HH24:MIHH24HHn
NElliott
07/03/2019, 1:23 PM@al3xicon Thank you very much for replying that's very helpful, appreciated.
a
al3xicon
07/03/2019, 1:24 PMcheers no problem
n
NElliott
07/03/2019, 1:27 PMI was trying to compare the datetime "now" i.e when the script is started, with a date/time field on an SO. The reason being, the field on the SO can be in the future.
As it turns out it was another search criteria that was throwing up "unexpected" behaviour 😑Eventually I go to the bottom of it.
This is still very useful information you provided, I'll bank it 👍
a
al3xicon
07/03/2019, 1:38 PMright on - i'm sure you'll come across this issue before long!
4 Views