| **
Well, I’ll tell you I won’t be
using them anymore. They’re a pain in my ARS! I used a Date type for a ‘Birth Date’
field, since many people here have a birthday prior to the beginning of Remedy
Time (1/1/1970). But now I’m kind of wishing I had just
used a char field with a lot of workflow to format and parse it for the age
calculations. Besides the problem I mention below, there
is the Web dialog popup for the field, which lists year first, then month and
day, and includes a check box for BC. Granted that’s fine for most
of the world, but around here the users were confused to no end. (After
all, who has a B.C. birthday?) And to change that popup, I had to hack a _javascript_ file (ar_date_popup.jsp) -Aaron * Email: [EMAIL PROTECTED] From: Action Request
System discussion list(ARSList) [mailto: ** Just wondering how
many people out there are using Date fields other then what is OOTB? I have
found I usually run into some kind of issue when I use them (granted I haven't
used them much since they were first added to ARS). About the only thing I use
them for currently is to put a nice looking date in an email (users don't care
much to see 09/22/06 17:58:15). On 9/26/06, ** I'm using a Date field type (not a date/time field that
displays date only – an actual date field) and thus the problem. -A From: Action Request System discussion
list(ARSList) [mailto:[email protected]]
On Behalf Of Ron Tavares ** The Date
field works the same as the Date/Time field from the database side.
They both record time in seconds. The difference is from the User
side. Date does not give you time of day selection, but it will set to
00:00:00 for the day choosen. So your query would have to be:
OR ('Effective
Date' >= $DATE$ - 86400) .ron
On
9/26/06, ** I've
got a DATE field (not a Date/Time field) from which I want to query relative to
the current day. This
works: ('Effective
Date' >= $DATE$) But
this does not: ('Effective
Date' >= $DATE$ - 1) But
strangely enough, this DOES work: ('Effective
Date' >= $DATE$ - 1156789196) So
it looks like the $DATE$ keyword evaluates in the date format (days) when used
by itself with a date field, but evaluates in the date/time format (seconds)
when used in arithmetic. The problem is that each day will add another
864399 to what needs to be subtracted, which makes things much more complicated
for an escalation! Is
there some way to work with date fields in queries that I'm missing? -Aaron * Email:
[EMAIL PROTECTED]
__20060125_______________________This
posting was submitted with HTML in it___
__20060125_______________________This posting was submitted with HTML in it___
|
- Re: OT Re: DATE fields and queries Aaron Keller
- Re: OT Re: DATE fields and queries Rodney Harris
- Re: OT Re: DATE fields and queries Misi Mladoniczky
- Re: OT Re: DATE fields and queries Rodney Harris
- Re: OT Re: DATE fields and queries Misi Mladoniczky
- Re: OT Re: DATE fields and queries Rodney Harris

