Mark,
I'm having the same problems with Date fields for some time now (these
are Date only fields, not Date/Time fields). I think it DOES have
something to do with the quotation marks.
When I do this:
'mydate' 6/21/2008 it works,
But when I do:
'mydate' ($DATE$ - (((60 * 60) * 24) *
Hi, Lisa:
I have had to deal with a similar conversion.
We have a Self-Service application that pushes entries into our Helpdesk
form. The field on the Self-Service form is Date/Time. The field that
this Self-Service date/time field is being pushed into is a DATE field.
So, I did the
You could additionally push the value from the date/time field (integer)
into a plain character field. This will give the usable date format,
such as 10/27/2008 05:22:01AM. Then, you could do another set fields to
the Date Field that takes just the first 10 characters of what is in the
char field,
In this situation you would need the escalation to modify EVERY record, and
have a series of filters fire on modify that performed the remove on only
those records that matched
-Original Message-
From: Action Request System discussion list(ARSList)
[mailto:[EMAIL PROTECTED] On Behalf Of
This is good advice, but none of my fields are Date/Time fields, they
are all Date Fields only.
Lisa
From: Action Request System discussion list(ARSList)
[mailto:[EMAIL PROTECTED] On Behalf Of Michelle Lucero
Sent: Wednesday, October 29, 2008 2:30 PM
To:
You can create a form with only 1 record on it and have the escalation
fire against that form.
i.e. Create a form ArchiveEscalationControl
Put a Date Only field on it ArchiveDate
Create an Escalation Do Work that runs against
ArchiveEscalationControl
Escalation does a Set fields to
I checked in the documentation and found that both $DATE$ and
$TIMESTAMP$ resolve to current date when used with a Date field (not to
be confused with a Date/Time field set to display as Date). It appears
that the arithmetic is not being performed in the comparisons.
'my_date_field' ($DATE$ -
I usually have to put the Date fields inside quotes when doing
calculations
'my_date_field' ($DATE$ + 182)
I've tried that. It doesn't work.I've entered 28.10.2020 into my date
field, i.e. I'm saying in my AL RunIf qualification: 28.10.2020
($DATE$ + 1), but the AL goes into else action. As
Hi Doug,
'my_date_field' ($DATE$ + 15724800)
I've tried that. It doesn't work.I've entered 28.10.2020 into my date
field, i.e. I'm saying in my AL RunIf qualification: 28.10.2020
($DATE$ + 1), but the AL goes into else action. As this example shows
it doesn't really matter it ARS sees date as
Hi Gary,
Yeah, I think that doug is on to something here. The $DATE$ keyword is
referring to seconds, I believe, and thus you need to add six months
worth of seconds. Note, that $DATE$ calculates to midnight that day, so
if you need to calculate six months from now, then you will likely need
An easy way to do this is to use the multipliers. You will also need to
use $TIMESTAMP$
'my_date_field' ($TIMESTAMP$ + (60*60*24*182))
$TIMESTAMP$ returns the number of seconds elapsed since midnight
Coordinated Universal Time (UTC) of January 1, 1970.
Guess what platform Remedy ARS was
A couple of questions...
Is your field a Date/Time, Date Only, or Time Only field?
Since it is an AL have you tried using the 7.1 Client to see if it does
the same thing?
If your field is a Date/Time field (even if it is set to only display
the Date) you will need to use TIMESTAMP instead of
There was a native Macintosh client through version 3.2. It was one of the
reasons we originally bought the product.
Christopher Strauss, Ph.D.
Call Tracking Administration Manager
University of North Texas Computing IT Center
http://itsm.unt.edu/
-Original Message-
From: Action
Hi Listers,
I have a date field on my form and I want to check, if the date
entered isn't later than 6 months from now. I have an Active Link with
the following qualification:
'my_date_field' $DATE$ + 182
This doesn't work.
'my_date_field' $DATE$ works just fine. As soon as I try to add any
have you tried
'my_date_field' ($DATE$ + 182)
so that it will add 182 to the date before doing the compare?
-Original Message-
From: Action Request System discussion list(ARSList)
[mailto:[EMAIL PROTECTED] On Behalf Of Mark Milke
Sent: Monday, October 27, 2008 8:27 AM
To:
'my_date_field' ($DATE$ + 182)
so that it will add 182 to the date before doing the compare?
Yes, that's exactly what I did.
Mark
___
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
Platinum Sponsor:
I usually have to put the Date fields inside quotes when doing
calculations
'my_date_field' ($DATE$ + 182)
Fred
-Original Message-
From: Action Request System discussion list(ARSList)
[mailto:[EMAIL PROTECTED] On Behalf Of Mark Milke
Sent: Monday, October 27, 2008 10:08 AM
To:
Try
'my_date_field' ($DATE$ + 15724800)
Humor me
Doug
-Original Message-
From: Action Request System discussion list(ARSList)
[mailto:[EMAIL PROTECTED] On Behalf Of Mark Milke
Sent: Monday, October 27, 2008 11:08 AM
To: arslist@ARSLIST.ORG
Subject: Re: Adding days to a Date field in a
Yeah, I think that doug is on to something here. The $DATE$ keyword is
referring to seconds, I believe, and thus you need to add six months
worth of seconds. Note, that $DATE$ calculates to midnight that day, so
if you need to calculate six months from now, then you will likely need
to use
Oh...I know why it's not workingbecause $DATE$ can be used for both Date
and Date/Time fieldsand remedy probably does some dynamic stuff to the
value when you are doing a compare with a date field...so what you may need
to do is
setfield ztmp_datefield = $DATE$
setfield ztmp_datefield =
Yeah, It is at the database level a Date/Time field, the DISPLAY
property is TIME
:)
Doug
-Original Message-
From: Action Request System discussion list(ARSList)
[mailto:[EMAIL PROTECTED] On Behalf Of Opela, Gary L CTR USAF AFMC 72
CS/SCBAH
Sent: Monday, October 27, 2008 11:21 AM
To:
An easy way to do this is to use the multipliers. You will also need to
use $TIMESTAMP$
'my_date_field' ($TIMESTAMP$ + (60*60*24*182))
$TIMESTAMP$ returns the number of seconds elapsed since midnight
Coordinated Universal Time (UTC) of January 1, 1970.
Guess what platform Remedy ARS was first
What I use is $DATE$ + (60*60*24*182) in stead of the big long can't remember
integer. That way I can see what I am adding.
Rocky
Rocky Rockwell
Remedy Application Designer
Wk Phone: 214-567-8874
Cell: 214-663-7229
[EMAIL PROTECTED]
-Original Message-
From: Action Request System
Yes, that should work.
Although the $DATE$ keyword can be used for both Date and Date/Time fields,
using an arithmetic operation against the keyword seems to force it to
translate into a date/time value (# of seconds instead of # of days) at the
database level. You can observe this by running
Frank,
This syntax will work if searching a Date/Time field, but it will not work with
a Date (only) field. The value on the right side of the qualification
(($TIMESTAMP$ + (60*60*24*182)) would generate an integer value well beyond the
range of the Date field type. If you divided this value
Mark,
Even if that did work, it wouldn't be always accurate, considering leap years
or the 2 consecutive months that we have 30 days.
Why not try string manupulation, by setting the current value contained in the
date field, to a character field and then find the month position and extract
26 matches
Mail list logo
