Re: Bug with comparing a Date field to the $DATE$ keyword in a table fields qualification???
Joe, try the following:
Change the table qualification to (EXTERNAL($ztmpQualification$)) AND
('Start Date' = $DATE$)
Create display only field ztmpQualification.
Create active link that sets ztmpQualification = ('Queue' = $Queue$)
Create active link that does a table refresh
You might have to end up setting ztmpQualification = ('Queue' =
$Queue$) AND ('Start Date' = $\DATE$) and your table field
qualification just to EXTERNAL($ztmpQualification$)
For some reason, a table field on a display-only form doesn't seem to
parse correctly $Field$ although the EXTERNAL() function does.
It is also worth noting that if you are pulling in data from 'Queue' and
there is the event that the value could be $NULL$, you need to check for
$NULL$ and for . I know you aren't doing that here, but for instance
if you had 'Queue' != $NULL$ on there, you need to change this to
('Queue' != $NULL$) AND ('Queue' != ). If the user puts value in the
'Queue' field and then backspaces over it, on a display only form, I've
noticed that the value is no longer $NULL$, but the empty set, .
Thanks,
Gary Opela, Jr
Sr. Remedy Developer
Leader Communications, Inc.
405 736 3211
-Original Message-
From: Action Request System discussion list(ARSList)
[mailto:[EMAIL PROTECTED] On Behalf Of Joe D'Souza
Sent: Monday, August 20, 2007 11:30 PM
To: arslist@ARSLIST.ORG
Subject: Bug with comparing a Date field to the $DATE$ keyword in a
table fields qualification???
**
Listers,
I am literally pulling my hair over this.. I am on ARS 7.0.1 Patch 003
on Windows 2K3SP2 and MS-SQL 2K5SP2..
I have one data form and another display only form. In the data form
among other fields I have a character field called Queue and another
Date field (not Date/Time).
I have a simple qualification using a Date field in the qualification on
a Table field. I copied the qualification below.
('Queue' = $Queue$) AND ('Start Date' = $DATE$)
This returns all the records when the table field is refreshed after
having a value of Test Queue in the Queue field irrespective of the
value of the Start Date in the underlying data form when it should have
been returning only 1 record on the table field.
On the User Tool however if I search the form using advanced search
('Queue' = Test Queue) AND ('Start Date' = 8/20/2007)
I get just one record as I should given my data.
Is this a known bug with using a Date field on a table fields
qualification??
Joe
__20060125___This posting was submitted with HTML in
it___
___
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org ARSlist:Where the
Answers Are
Re: Bug with comparing a Date field to the $DATE$ keyword in a table fields qualification???
Gary, (and maybe Joe too)
I actually think the date stuff your seeing is actually related to
these details...
Ref: Workflow-Objects-700.pdf Pg 199
For example, if you have a table field with a qualification of
EXTERNAL($Qualify Field$)
and Qualify Field is a character field with a value of
('Create Date' $TIMESTAMP$) AND ('Login Name' = $USER$)
the table field will not produce expected results when refreshed. The
keywords will expand, producing a qualification such as
('Create Date' 05/22/02 11:00:34 AM) AND ('Login Name' = Demo)
This is not a valid query, since the date/time and character values
are not enclosed in quotation marks. To prevent the keywords from
expanding, write the qualification like this:
('Create Date' $\TIMESTAMP$) AND ('Login Name' = $\USER$)
In forms viewed on the Web, if EXTERNAL() references a field that
contains a qualification such as $Date 1$ = 'Date 2', you must add
double quotation marks around $Date 1$, like this:
$Date 1$ = 'Date 2'.
Note: In BMC Remedy User, the EXTERNAL operator reads date and time
string from the server's time. On the web, the EXTERNAL operator reads
the date and time string from client's time zone.
HTH
--
Carey Matthew Black
Remedy Skilled Professional (RSP)
ARS = Action Request System(Remedy)
Love, then teach
Solution = People + Process + Tools
Fast, Accurate, Cheap Pick two.
On 8/21/07, Opela, Gary L Contr OC-ALC/ITMA
[EMAIL PROTECTED] wrote:
Joe, try the following:
Change the table qualification to (EXTERNAL($ztmpQualification$)) AND
('Start Date' = $DATE$)
Create display only field ztmpQualification.
Create active link that sets ztmpQualification = ('Queue' = $Queue$)
Create active link that does a table refresh
You might have to end up setting ztmpQualification = ('Queue' =
$Queue$) AND ('Start Date' = $\DATE$) and your table field
qualification just to EXTERNAL($ztmpQualification$)
For some reason, a table field on a display-only form doesn't seem to
parse correctly $Field$ although the EXTERNAL() function does.
It is also worth noting that if you are pulling in data from 'Queue' and
there is the event that the value could be $NULL$, you need to check for
$NULL$ and for . I know you aren't doing that here, but for instance
if you had 'Queue' != $NULL$ on there, you need to change this to
('Queue' != $NULL$) AND ('Queue' != ). If the user puts value in the
'Queue' field and then backspaces over it, on a display only form, I've
noticed that the value is no longer $NULL$, but the empty set, .
Thanks,
Gary Opela, Jr
Sr. Remedy Developer
Leader Communications, Inc.
405 736 3211
-Original Message-
From: Action Request System discussion list(ARSList)
[mailto:[EMAIL PROTECTED] On Behalf Of Joe D'Souza
Sent: Monday, August 20, 2007 11:30 PM
To: arslist@ARSLIST.ORG
Subject: Bug with comparing a Date field to the $DATE$ keyword in a
table fields qualification???
**
Listers,
I am literally pulling my hair over this.. I am on ARS 7.0.1 Patch 003
on Windows 2K3SP2 and MS-SQL 2K5SP2..
I have one data form and another display only form. In the data form
among other fields I have a character field called Queue and another
Date field (not Date/Time).
I have a simple qualification using a Date field in the qualification on
a Table field. I copied the qualification below.
('Queue' = $Queue$) AND ('Start Date' = $DATE$)
This returns all the records when the table field is refreshed after
having a value of Test Queue in the Queue field irrespective of the
value of the Start Date in the underlying data form when it should have
been returning only 1 record on the table field.
On the User Tool however if I search the form using advanced search
('Queue' = Test Queue) AND ('Start Date' = 8/20/2007)
I get just one record as I should given my data.
Is this a known bug with using a Date field on a table fields
qualification??
Joe
___
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org ARSlist:Where the
Answers Are
Re: Bug with comparing a Date field to the $DATE$ keyword in a table fields qualification???
Carey, thanks for expanding upon this, but I'm not using any keywords
such as $DATE$ or $TIMESTAMP$ in my external field's value. My situation
only worked whenever I used EXTERNAL(), and I think that Joe is probably
having the same thing.
I was suggesting he try using the EXTERNAL, and if he referenced $DATE$,
then it would have to be escaped as $\DATE$.
Thanks,
Gary Opela, Jr
Sr. Remedy Developer
Leader Communications, Inc.
405 736 3211
-Original Message-
From: Action Request System discussion list(ARSList)
[mailto:[EMAIL PROTECTED] On Behalf Of Carey Matthew Black
Sent: Tuesday, August 21, 2007 7:38 AM
To: arslist@ARSLIST.ORG
Subject: Re: Bug with comparing a Date field to the $DATE$ keyword in a
table fields qualification???
Gary, (and maybe Joe too)
I actually think the date stuff your seeing is actually related to
these details...
Ref: Workflow-Objects-700.pdf Pg 199
For example, if you have a table field with a qualification of
EXTERNAL($Qualify Field$)
and Qualify Field is a character field with a value of
('Create Date' $TIMESTAMP$) AND ('Login Name' = $USER$)
the table field will not produce expected results when refreshed. The
keywords will expand, producing a qualification such as
('Create Date' 05/22/02 11:00:34 AM) AND ('Login Name' = Demo)
This is not a valid query, since the date/time and character values
are not enclosed in quotation marks. To prevent the keywords from
expanding, write the qualification like this:
('Create Date' $\TIMESTAMP$) AND ('Login Name' = $\USER$)
In forms viewed on the Web, if EXTERNAL() references a field that
contains a qualification such as $Date 1$ = 'Date 2', you must add
double quotation marks around $Date 1$, like this:
$Date 1$ = 'Date 2'.
Note: In BMC Remedy User, the EXTERNAL operator reads date and time
string from the server's time. On the web, the EXTERNAL operator reads
the date and time string from client's time zone.
HTH
--
Carey Matthew Black
Remedy Skilled Professional (RSP)
ARS = Action Request System(Remedy)
Love, then teach
Solution = People + Process + Tools
Fast, Accurate, Cheap Pick two.
On 8/21/07, Opela, Gary L Contr OC-ALC/ITMA
[EMAIL PROTECTED] wrote:
Joe, try the following:
Change the table qualification to (EXTERNAL($ztmpQualification$)) AND
('Start Date' = $DATE$)
Create display only field ztmpQualification.
Create active link that sets ztmpQualification = ('Queue' = $Queue$)
Create active link that does a table refresh
You might have to end up setting ztmpQualification = ('Queue' =
$Queue$) AND ('Start Date' = $\DATE$) and your table field
qualification just to EXTERNAL($ztmpQualification$)
For some reason, a table field on a display-only form doesn't seem to
parse correctly $Field$ although the EXTERNAL() function does.
It is also worth noting that if you are pulling in data from 'Queue'
and
there is the event that the value could be $NULL$, you need to check
for
$NULL$ and for . I know you aren't doing that here, but for instance
if you had 'Queue' != $NULL$ on there, you need to change this to
('Queue' != $NULL$) AND ('Queue' != ). If the user puts value in the
'Queue' field and then backspaces over it, on a display only form,
I've
noticed that the value is no longer $NULL$, but the empty set, .
Thanks,
Gary Opela, Jr
Sr. Remedy Developer
Leader Communications, Inc.
405 736 3211
-Original Message-
From: Action Request System discussion list(ARSList)
[mailto:[EMAIL PROTECTED] On Behalf Of Joe D'Souza
Sent: Monday, August 20, 2007 11:30 PM
To: arslist@ARSLIST.ORG
Subject: Bug with comparing a Date field to the $DATE$ keyword in a
table fields qualification???
**
Listers,
I am literally pulling my hair over this.. I am on ARS 7.0.1 Patch 003
on Windows 2K3SP2 and MS-SQL 2K5SP2..
I have one data form and another display only form. In the data form
among other fields I have a character field called Queue and another
Date field (not Date/Time).
I have a simple qualification using a Date field in the qualification
on
a Table field. I copied the qualification below.
('Queue' = $Queue$) AND ('Start Date' = $DATE$)
This returns all the records when the table field is refreshed after
having a value of Test Queue in the Queue field irrespective of the
value of the Start Date in the underlying data form when it should
have
been returning only 1 record on the table field.
On the User Tool however if I search the form using advanced search
('Queue' = Test Queue) AND ('Start Date' = 8/20/2007)
I get just one record as I should given my data.
Is this a known bug with using a Date field on a table fields
qualification??
Joe
___
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org ARSlist:Where
the Answers Are
___
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
Re: Bug with comparing a Date field to the $DATE$ keyword in a table fields qualification???
Carey, Gary,
Thanks for your notes.
Carey, mine isn't the Date/time field but the Date field so $TIMESTAMP$
cannot be used to compare it but the $DATE$ keyword would have to be used
instead.
Gary, about using external, sure I can try that and see if it works. I don't
yet see why this qualification shouldn't work directly from a table field..
And yes you do need to escape keywords with a \ when used in External
Qualifications..
Cheers
Joe
-Original Message-
From: Action Request System discussion list(ARSList)
[mailto:[EMAIL PROTECTED] Behalf Of Opela, Gary L Contr OC-ALC/ITMA
Sent: Tuesday, August 21, 2007 8:43 AM
To: arslist@ARSLIST.ORG
Subject: Re: Bug with comparing a Date field to the $DATE$ keyword in a
table fields qualification???
Carey, thanks for expanding upon this, but I'm not using any keywords
such as $DATE$ or $TIMESTAMP$ in my external field's value. My situation
only worked whenever I used EXTERNAL(), and I think that Joe is probably
having the same thing.
I was suggesting he try using the EXTERNAL, and if he referenced $DATE$,
then it would have to be escaped as $\DATE$.
Thanks,
Gary Opela, Jr
Sr. Remedy Developer
Leader Communications, Inc.
405 736 3211
-Original Message-
From: Action Request System discussion list(ARSList)
[mailto:[EMAIL PROTECTED] On Behalf Of Carey Matthew Black
Sent: Tuesday, August 21, 2007 7:38 AM
To: arslist@ARSLIST.ORG
Subject: Re: Bug with comparing a Date field to the $DATE$ keyword in a
table fields qualification???
Gary, (and maybe Joe too)
I actually think the date stuff your seeing is actually related to
these details...
Ref: Workflow-Objects-700.pdf Pg 199
For example, if you have a table field with a qualification of
EXTERNAL($Qualify Field$)
and Qualify Field is a character field with a value of
('Create Date' $TIMESTAMP$) AND ('Login Name' = $USER$)
the table field will not produce expected results when refreshed. The
keywords will expand, producing a qualification such as
('Create Date' 05/22/02 11:00:34 AM) AND ('Login Name' = Demo)
This is not a valid query, since the date/time and character values
are not enclosed in quotation marks. To prevent the keywords from
expanding, write the qualification like this:
('Create Date' $\TIMESTAMP$) AND ('Login Name' = $\USER$)
In forms viewed on the Web, if EXTERNAL() references a field that
contains a qualification such as $Date 1$ = 'Date 2', you must add
double quotation marks around $Date 1$, like this:
$Date 1$ = 'Date 2'.
Note: In BMC Remedy User, the EXTERNAL operator reads date and time
string from the server's time. On the web, the EXTERNAL operator reads
the date and time string from client's time zone.
HTH
--
Carey Matthew Black
Remedy Skilled Professional (RSP)
ARS = Action Request System(Remedy)
Love, then teach
Solution = People + Process + Tools
Fast, Accurate, Cheap Pick two.
On 8/21/07, Opela, Gary L Contr OC-ALC/ITMA
[EMAIL PROTECTED] wrote:
Joe, try the following:
Change the table qualification to (EXTERNAL($ztmpQualification$)) AND
('Start Date' = $DATE$)
Create display only field ztmpQualification.
Create active link that sets ztmpQualification = ('Queue' = $Queue$)
Create active link that does a table refresh
You might have to end up setting ztmpQualification = ('Queue' =
$Queue$) AND ('Start Date' = $\DATE$) and your table field
qualification just to EXTERNAL($ztmpQualification$)
For some reason, a table field on a display-only form doesn't seem to
parse correctly $Field$ although the EXTERNAL() function does.
It is also worth noting that if you are pulling in data from 'Queue'
and
there is the event that the value could be $NULL$, you need to check
for
$NULL$ and for . I know you aren't doing that here, but for instance
if you had 'Queue' != $NULL$ on there, you need to change this to
('Queue' != $NULL$) AND ('Queue' != ). If the user puts value in the
'Queue' field and then backspaces over it, on a display only form,
I've
noticed that the value is no longer $NULL$, but the empty set, .
Thanks,
Gary Opela, Jr
Sr. Remedy Developer
Leader Communications, Inc.
405 736 3211
-Original Message-
From: Action Request System discussion list(ARSList)
[mailto:[EMAIL PROTECTED] On Behalf Of Joe D'Souza
Sent: Monday, August 20, 2007 11:30 PM
To: arslist@ARSLIST.ORG
Subject: Bug with comparing a Date field to the $DATE$ keyword in a
table fields qualification???
**
Listers,
I am literally pulling my hair over this.. I am on ARS 7.0.1 Patch 003
on Windows 2K3SP2 and MS-SQL 2K5SP2..
I have one data form and another display only form. In the data form
among other fields I have a character field called Queue and another
Date field (not Date/Time).
I have a simple qualification using a Date field in the qualification
on
a Table field. I copied the qualification below.
('Queue' = $Queue$) AND ('Start Date' = $DATE$)
This returns all the records when the table field is refreshed after
Re: Bug with comparing a Date field to the $DATE$ keyword in a table fields qualification???
Joe, I agree that the qualification SHOULD work directly in the table
field, but in my experiences, for some reason it does not.
Give out the External a try, I'll bet you a Mt. Dew (if I ever meet you)
that it will :)
Thanks,
Gary Opela, Jr
Sr. Remedy Developer
Leader Communications, Inc.
405 736 3211
-Original Message-
From: Action Request System discussion list(ARSList)
[mailto:[EMAIL PROTECTED] On Behalf Of Joe D'Souza
Sent: Tuesday, August 21, 2007 9:36 AM
To: arslist@ARSLIST.ORG
Subject: Re: Bug with comparing a Date field to the $DATE$ keyword in a
table fields qualification???
Carey, Gary,
Thanks for your notes.
Carey, mine isn't the Date/time field but the Date field so $TIMESTAMP$
cannot be used to compare it but the $DATE$ keyword would have to be
used
instead.
Gary, about using external, sure I can try that and see if it works. I
don't
yet see why this qualification shouldn't work directly from a table
field..
And yes you do need to escape keywords with a \ when used in External
Qualifications..
Cheers
Joe
-Original Message-
From: Action Request System discussion list(ARSList)
[mailto:[EMAIL PROTECTED] Behalf Of Opela, Gary L Contr OC-ALC/ITMA
Sent: Tuesday, August 21, 2007 8:43 AM
To: arslist@ARSLIST.ORG
Subject: Re: Bug with comparing a Date field to the $DATE$ keyword in a
table fields qualification???
Carey, thanks for expanding upon this, but I'm not using any keywords
such as $DATE$ or $TIMESTAMP$ in my external field's value. My situation
only worked whenever I used EXTERNAL(), and I think that Joe is probably
having the same thing.
I was suggesting he try using the EXTERNAL, and if he referenced $DATE$,
then it would have to be escaped as $\DATE$.
Thanks,
Gary Opela, Jr
Sr. Remedy Developer
Leader Communications, Inc.
405 736 3211
-Original Message-
From: Action Request System discussion list(ARSList)
[mailto:[EMAIL PROTECTED] On Behalf Of Carey Matthew Black
Sent: Tuesday, August 21, 2007 7:38 AM
To: arslist@ARSLIST.ORG
Subject: Re: Bug with comparing a Date field to the $DATE$ keyword in a
table fields qualification???
Gary, (and maybe Joe too)
I actually think the date stuff your seeing is actually related to
these details...
Ref: Workflow-Objects-700.pdf Pg 199
For example, if you have a table field with a qualification of
EXTERNAL($Qualify Field$)
and Qualify Field is a character field with a value of
('Create Date' $TIMESTAMP$) AND ('Login Name' = $USER$)
the table field will not produce expected results when refreshed. The
keywords will expand, producing a qualification such as
('Create Date' 05/22/02 11:00:34 AM) AND ('Login Name' = Demo)
This is not a valid query, since the date/time and character values
are not enclosed in quotation marks. To prevent the keywords from
expanding, write the qualification like this:
('Create Date' $\TIMESTAMP$) AND ('Login Name' = $\USER$)
In forms viewed on the Web, if EXTERNAL() references a field that
contains a qualification such as $Date 1$ = 'Date 2', you must add
double quotation marks around $Date 1$, like this:
$Date 1$ = 'Date 2'.
Note: In BMC Remedy User, the EXTERNAL operator reads date and time
string from the server's time. On the web, the EXTERNAL operator reads
the date and time string from client's time zone.
HTH
--
Carey Matthew Black
Remedy Skilled Professional (RSP)
ARS = Action Request System(Remedy)
Love, then teach
Solution = People + Process + Tools
Fast, Accurate, Cheap Pick two.
On 8/21/07, Opela, Gary L Contr OC-ALC/ITMA
[EMAIL PROTECTED] wrote:
Joe, try the following:
Change the table qualification to (EXTERNAL($ztmpQualification$)) AND
('Start Date' = $DATE$)
Create display only field ztmpQualification.
Create active link that sets ztmpQualification = ('Queue' = $Queue$)
Create active link that does a table refresh
You might have to end up setting ztmpQualification = ('Queue' =
$Queue$) AND ('Start Date' = $\DATE$) and your table field
qualification just to EXTERNAL($ztmpQualification$)
For some reason, a table field on a display-only form doesn't seem to
parse correctly $Field$ although the EXTERNAL() function does.
It is also worth noting that if you are pulling in data from 'Queue'
and
there is the event that the value could be $NULL$, you need to check
for
$NULL$ and for . I know you aren't doing that here, but for instance
if you had 'Queue' != $NULL$ on there, you need to change this to
('Queue' != $NULL$) AND ('Queue' != ). If the user puts value in the
'Queue' field and then backspaces over it, on a display only form,
I've
noticed that the value is no longer $NULL$, but the empty set, .
Thanks,
Gary Opela, Jr
Sr. Remedy Developer
Leader Communications, Inc.
405 736 3211
-Original Message-
From: Action Request System discussion list(ARSList)
[mailto:[EMAIL PROTECTED] On Behalf Of Joe D'Souza
Sent: Monday, August 20, 2007 11:30 PM
To: arslist@ARSLIST.ORG
Subject: Bug with comparing a
Re: Bug with comparing a Date field to the $DATE$ keyword in a table fields qualification???
How did you know that's my favorite soda after coke :-)
Joe
-Original Message-
From: Action Request System discussion list(ARSList)
[mailto:[EMAIL PROTECTED] Behalf Of Opela, Gary L Contr OC-ALC/ITMA
Sent: Tuesday, August 21, 2007 10:38 AM
To: arslist@ARSLIST.ORG
Subject: Re: Bug with comparing a Date field to the $DATE$ keyword in a
table fields qualification???
Joe, I agree that the qualification SHOULD work directly in the table
field, but in my experiences, for some reason it does not.
Give out the External a try, I'll bet you a Mt. Dew (if I ever meet you)
that it will :)
Thanks,
Gary Opela, Jr
Sr. Remedy Developer
Leader Communications, Inc.
405 736 3211
-Original Message-
From: Action Request System discussion list(ARSList)
[mailto:[EMAIL PROTECTED] On Behalf Of Joe D'Souza
Sent: Tuesday, August 21, 2007 9:36 AM
To: arslist@ARSLIST.ORG
Subject: Re: Bug with comparing a Date field to the $DATE$ keyword in a
table fields qualification???
Carey, Gary,
Thanks for your notes.
Carey, mine isn't the Date/time field but the Date field so $TIMESTAMP$
cannot be used to compare it but the $DATE$ keyword would have to be
used
instead.
Gary, about using external, sure I can try that and see if it works. I
don't
yet see why this qualification shouldn't work directly from a table
field..
And yes you do need to escape keywords with a \ when used in External
Qualifications..
Cheers
Joe
-Original Message-
From: Action Request System discussion list(ARSList)
[mailto:[EMAIL PROTECTED] Behalf Of Opela, Gary L Contr OC-ALC/ITMA
Sent: Tuesday, August 21, 2007 8:43 AM
To: arslist@ARSLIST.ORG
Subject: Re: Bug with comparing a Date field to the $DATE$ keyword in a
table fields qualification???
Carey, thanks for expanding upon this, but I'm not using any keywords
such as $DATE$ or $TIMESTAMP$ in my external field's value. My situation
only worked whenever I used EXTERNAL(), and I think that Joe is probably
having the same thing.
I was suggesting he try using the EXTERNAL, and if he referenced $DATE$,
then it would have to be escaped as $\DATE$.
Thanks,
Gary Opela, Jr
Sr. Remedy Developer
Leader Communications, Inc.
405 736 3211
-Original Message-
From: Action Request System discussion list(ARSList)
[mailto:[EMAIL PROTECTED] On Behalf Of Carey Matthew Black
Sent: Tuesday, August 21, 2007 7:38 AM
To: arslist@ARSLIST.ORG
Subject: Re: Bug with comparing a Date field to the $DATE$ keyword in a
table fields qualification???
Gary, (and maybe Joe too)
I actually think the date stuff your seeing is actually related to
these details...
Ref: Workflow-Objects-700.pdf Pg 199
For example, if you have a table field with a qualification of
EXTERNAL($Qualify Field$)
and Qualify Field is a character field with a value of
('Create Date' $TIMESTAMP$) AND ('Login Name' = $USER$)
the table field will not produce expected results when refreshed. The
keywords will expand, producing a qualification such as
('Create Date' 05/22/02 11:00:34 AM) AND ('Login Name' = Demo)
This is not a valid query, since the date/time and character values
are not enclosed in quotation marks. To prevent the keywords from
expanding, write the qualification like this:
('Create Date' $\TIMESTAMP$) AND ('Login Name' = $\USER$)
In forms viewed on the Web, if EXTERNAL() references a field that
contains a qualification such as $Date 1$ = 'Date 2', you must add
double quotation marks around $Date 1$, like this:
$Date 1$ = 'Date 2'.
Note: In BMC Remedy User, the EXTERNAL operator reads date and time
string from the server's time. On the web, the EXTERNAL operator reads
the date and time string from client's time zone.
HTH
--
Carey Matthew Black
Remedy Skilled Professional (RSP)
ARS = Action Request System(Remedy)
Love, then teach
Solution = People + Process + Tools
Fast, Accurate, Cheap Pick two.
On 8/21/07, Opela, Gary L Contr OC-ALC/ITMA
[EMAIL PROTECTED] wrote:
Joe, try the following:
Change the table qualification to (EXTERNAL($ztmpQualification$)) AND
('Start Date' = $DATE$)
Create display only field ztmpQualification.
Create active link that sets ztmpQualification = ('Queue' = $Queue$)
Create active link that does a table refresh
You might have to end up setting ztmpQualification = ('Queue' =
$Queue$) AND ('Start Date' = $\DATE$) and your table field
qualification just to EXTERNAL($ztmpQualification$)
For some reason, a table field on a display-only form doesn't seem to
parse correctly $Field$ although the EXTERNAL() function does.
It is also worth noting that if you are pulling in data from 'Queue'
and
there is the event that the value could be $NULL$, you need to check
for
$NULL$ and for . I know you aren't doing that here, but for instance
if you had 'Queue' != $NULL$ on there, you need to change this to
('Queue' != $NULL$) AND ('Queue' != ). If the user puts value in the
'Queue' field and then backspaces over it, on a display only form,
I've
noticed that
Re: Bug with comparing a Date field to the $DATE$ keyword in a table fields qualification???
Well, I've grown up on Mt. Dew. Anyone who knows me can attest that I
have probably more Mt. Dew in my veins than blood at any one time!
Thanks,
Gary Opela, Jr
Sr. Remedy Developer
Leader Communications, Inc.
405 736 3211
-Original Message-
From: Action Request System discussion list(ARSList)
[mailto:[EMAIL PROTECTED] On Behalf Of Joe D'Souza
Sent: Tuesday, August 21, 2007 9:40 AM
To: arslist@ARSLIST.ORG
Subject: Re: Bug with comparing a Date field to the $DATE$ keyword in a
table fields qualification???
How did you know that's my favorite soda after coke :-)
Joe
-Original Message-
From: Action Request System discussion list(ARSList)
[mailto:[EMAIL PROTECTED] Behalf Of Opela, Gary L Contr OC-ALC/ITMA
Sent: Tuesday, August 21, 2007 10:38 AM
To: arslist@ARSLIST.ORG
Subject: Re: Bug with comparing a Date field to the $DATE$ keyword in a
table fields qualification???
Joe, I agree that the qualification SHOULD work directly in the table
field, but in my experiences, for some reason it does not.
Give out the External a try, I'll bet you a Mt. Dew (if I ever meet you)
that it will :)
Thanks,
Gary Opela, Jr
Sr. Remedy Developer
Leader Communications, Inc.
405 736 3211
-Original Message-
From: Action Request System discussion list(ARSList)
[mailto:[EMAIL PROTECTED] On Behalf Of Joe D'Souza
Sent: Tuesday, August 21, 2007 9:36 AM
To: arslist@ARSLIST.ORG
Subject: Re: Bug with comparing a Date field to the $DATE$ keyword in a
table fields qualification???
Carey, Gary,
Thanks for your notes.
Carey, mine isn't the Date/time field but the Date field so $TIMESTAMP$
cannot be used to compare it but the $DATE$ keyword would have to be
used
instead.
Gary, about using external, sure I can try that and see if it works. I
don't
yet see why this qualification shouldn't work directly from a table
field..
And yes you do need to escape keywords with a \ when used in External
Qualifications..
Cheers
Joe
-Original Message-
From: Action Request System discussion list(ARSList)
[mailto:[EMAIL PROTECTED] Behalf Of Opela, Gary L Contr OC-ALC/ITMA
Sent: Tuesday, August 21, 2007 8:43 AM
To: arslist@ARSLIST.ORG
Subject: Re: Bug with comparing a Date field to the $DATE$ keyword in a
table fields qualification???
Carey, thanks for expanding upon this, but I'm not using any keywords
such as $DATE$ or $TIMESTAMP$ in my external field's value. My situation
only worked whenever I used EXTERNAL(), and I think that Joe is probably
having the same thing.
I was suggesting he try using the EXTERNAL, and if he referenced $DATE$,
then it would have to be escaped as $\DATE$.
Thanks,
Gary Opela, Jr
Sr. Remedy Developer
Leader Communications, Inc.
405 736 3211
-Original Message-
From: Action Request System discussion list(ARSList)
[mailto:[EMAIL PROTECTED] On Behalf Of Carey Matthew Black
Sent: Tuesday, August 21, 2007 7:38 AM
To: arslist@ARSLIST.ORG
Subject: Re: Bug with comparing a Date field to the $DATE$ keyword in a
table fields qualification???
Gary, (and maybe Joe too)
I actually think the date stuff your seeing is actually related to
these details...
Ref: Workflow-Objects-700.pdf Pg 199
For example, if you have a table field with a qualification of
EXTERNAL($Qualify Field$)
and Qualify Field is a character field with a value of
('Create Date' $TIMESTAMP$) AND ('Login Name' = $USER$)
the table field will not produce expected results when refreshed. The
keywords will expand, producing a qualification such as
('Create Date' 05/22/02 11:00:34 AM) AND ('Login Name' = Demo)
This is not a valid query, since the date/time and character values
are not enclosed in quotation marks. To prevent the keywords from
expanding, write the qualification like this:
('Create Date' $\TIMESTAMP$) AND ('Login Name' = $\USER$)
In forms viewed on the Web, if EXTERNAL() references a field that
contains a qualification such as $Date 1$ = 'Date 2', you must add
double quotation marks around $Date 1$, like this:
$Date 1$ = 'Date 2'.
Note: In BMC Remedy User, the EXTERNAL operator reads date and time
string from the server's time. On the web, the EXTERNAL operator reads
the date and time string from client's time zone.
HTH
--
Carey Matthew Black
Remedy Skilled Professional (RSP)
ARS = Action Request System(Remedy)
Love, then teach
Solution = People + Process + Tools
Fast, Accurate, Cheap Pick two.
On 8/21/07, Opela, Gary L Contr OC-ALC/ITMA
[EMAIL PROTECTED] wrote:
Joe, try the following:
Change the table qualification to (EXTERNAL($ztmpQualification$)) AND
('Start Date' = $DATE$)
Create display only field ztmpQualification.
Create active link that sets ztmpQualification = ('Queue' = $Queue$)
Create active link that does a table refresh
You might have to end up setting ztmpQualification = ('Queue' =
$Queue$) AND ('Start Date' = $\DATE$) and your table field
qualification just to EXTERNAL($ztmpQualification$)
For some reason, a table field on a display-only
Re: Bug with comparing a Date field to the $DATE$ keyword in a table fields qualification???
I've been that way with coke..
Anyway getting back to the thread, did you notice this on just the $DATE$
keyword or the $TIMESTAMP$ keyword as well? I am pretty sure the $TIMESTAMP$
keyword works as expected at least on version 6.3.x. I am not sure if the
$DATE$ works on 6.3 as I don't think I ever had the need to use it on 6.3
table field qualifications..
Joe
-Original Message-
From: Action Request System discussion list(ARSList)
[mailto:[EMAIL PROTECTED] Behalf Of Opela, Gary L Contr OC-ALC/ITMA
Sent: Tuesday, August 21, 2007 10:43 AM
To: arslist@ARSLIST.ORG
Subject: Re: Bug with comparing a Date field to the $DATE$ keyword in a
table fields qualification???
Well, I've grown up on Mt. Dew. Anyone who knows me can attest that I
have probably more Mt. Dew in my veins than blood at any one time!
Thanks,
Gary Opela, Jr
Sr. Remedy Developer
Leader Communications, Inc.
405 736 3211
-Original Message-
From: Action Request System discussion list(ARSList)
[mailto:[EMAIL PROTECTED] On Behalf Of Joe D'Souza
Sent: Tuesday, August 21, 2007 9:40 AM
To: arslist@ARSLIST.ORG
Subject: Re: Bug with comparing a Date field to the $DATE$ keyword in a
table fields qualification???
How did you know that's my favorite soda after coke :-)
Joe
-Original Message-
From: Action Request System discussion list(ARSList)
[mailto:[EMAIL PROTECTED] Behalf Of Opela, Gary L Contr OC-ALC/ITMA
Sent: Tuesday, August 21, 2007 10:38 AM
To: arslist@ARSLIST.ORG
Subject: Re: Bug with comparing a Date field to the $DATE$ keyword in a
table fields qualification???
Joe, I agree that the qualification SHOULD work directly in the table
field, but in my experiences, for some reason it does not.
Give out the External a try, I'll bet you a Mt. Dew (if I ever meet you)
that it will :)
Thanks,
Gary Opela, Jr
Sr. Remedy Developer
Leader Communications, Inc.
405 736 3211
-Original Message-
From: Action Request System discussion list(ARSList)
[mailto:[EMAIL PROTECTED] On Behalf Of Joe D'Souza
Sent: Tuesday, August 21, 2007 9:36 AM
To: arslist@ARSLIST.ORG
Subject: Re: Bug with comparing a Date field to the $DATE$ keyword in a
table fields qualification???
Carey, Gary,
Thanks for your notes.
Carey, mine isn't the Date/time field but the Date field so $TIMESTAMP$
cannot be used to compare it but the $DATE$ keyword would have to be
used
instead.
Gary, about using external, sure I can try that and see if it works. I
don't
yet see why this qualification shouldn't work directly from a table
field..
And yes you do need to escape keywords with a \ when used in External
Qualifications..
Cheers
Joe
-Original Message-
From: Action Request System discussion list(ARSList)
[mailto:[EMAIL PROTECTED] Behalf Of Opela, Gary L Contr OC-ALC/ITMA
Sent: Tuesday, August 21, 2007 8:43 AM
To: arslist@ARSLIST.ORG
Subject: Re: Bug with comparing a Date field to the $DATE$ keyword in a
table fields qualification???
Carey, thanks for expanding upon this, but I'm not using any keywords
such as $DATE$ or $TIMESTAMP$ in my external field's value. My situation
only worked whenever I used EXTERNAL(), and I think that Joe is probably
having the same thing.
I was suggesting he try using the EXTERNAL, and if he referenced $DATE$,
then it would have to be escaped as $\DATE$.
Thanks,
Gary Opela, Jr
Sr. Remedy Developer
Leader Communications, Inc.
405 736 3211
-Original Message-
From: Action Request System discussion list(ARSList)
[mailto:[EMAIL PROTECTED] On Behalf Of Carey Matthew Black
Sent: Tuesday, August 21, 2007 7:38 AM
To: arslist@ARSLIST.ORG
Subject: Re: Bug with comparing a Date field to the $DATE$ keyword in a
table fields qualification???
Gary, (and maybe Joe too)
I actually think the date stuff your seeing is actually related to
these details...
Ref: Workflow-Objects-700.pdf Pg 199
For example, if you have a table field with a qualification of
EXTERNAL($Qualify Field$)
and Qualify Field is a character field with a value of
('Create Date' $TIMESTAMP$) AND ('Login Name' = $USER$)
the table field will not produce expected results when refreshed. The
keywords will expand, producing a qualification such as
('Create Date' 05/22/02 11:00:34 AM) AND ('Login Name' = Demo)
This is not a valid query, since the date/time and character values
are not enclosed in quotation marks. To prevent the keywords from
expanding, write the qualification like this:
('Create Date' $\TIMESTAMP$) AND ('Login Name' = $\USER$)
In forms viewed on the Web, if EXTERNAL() references a field that
contains a qualification such as $Date 1$ = 'Date 2', you must add
double quotation marks around $Date 1$, like this:
$Date 1$ = 'Date 2'.
Note: In BMC Remedy User, the EXTERNAL operator reads date and time
string from the server's time. On the web, the EXTERNAL operator reads
the date and time string from client's time zone.
HTH
--
Carey Matthew Black
Remedy Skilled Professional (RSP)
ARS = Action Request System(Remedy)
Re: Bug with comparing a Date field to the $DATE$ keyword in a table fields qualification???
Well, I'm not using either of the keywords, so I didn't have problem
with those. What I had problem was the equivalent of your $Queue$
reference. For some reason, that wasn't expanding properly. It would not
surprise me if the $Queue$ wasn't expanding properly for me, that you
would also experience a problem with $DATE$. I think for some reason
that the Display Only feature of the form must change something, because
of the action I noted below with $NULL$ and the empty set working
differently on Display Only forms vs. normal forms.
Thanks,
Gary Opela, Jr
Sr. Remedy Developer
Leader Communications, Inc.
405 736 3211
-Original Message-
From: Action Request System discussion list(ARSList)
[mailto:[EMAIL PROTECTED] On Behalf Of Joe D'Souza
Sent: Tuesday, August 21, 2007 9:50 AM
To: arslist@ARSLIST.ORG
Subject: Re: Bug with comparing a Date field to the $DATE$ keyword in a
table fields qualification???
I've been that way with coke..
Anyway getting back to the thread, did you notice this on just the
$DATE$
keyword or the $TIMESTAMP$ keyword as well? I am pretty sure the
$TIMESTAMP$
keyword works as expected at least on version 6.3.x. I am not sure if
the
$DATE$ works on 6.3 as I don't think I ever had the need to use it on
6.3
table field qualifications..
Joe
-Original Message-
From: Action Request System discussion list(ARSList)
[mailto:[EMAIL PROTECTED] Behalf Of Opela, Gary L Contr OC-ALC/ITMA
Sent: Tuesday, August 21, 2007 10:43 AM
To: arslist@ARSLIST.ORG
Subject: Re: Bug with comparing a Date field to the $DATE$ keyword in a
table fields qualification???
Well, I've grown up on Mt. Dew. Anyone who knows me can attest that I
have probably more Mt. Dew in my veins than blood at any one time!
Thanks,
Gary Opela, Jr
Sr. Remedy Developer
Leader Communications, Inc.
405 736 3211
-Original Message-
From: Action Request System discussion list(ARSList)
[mailto:[EMAIL PROTECTED] On Behalf Of Joe D'Souza
Sent: Tuesday, August 21, 2007 9:40 AM
To: arslist@ARSLIST.ORG
Subject: Re: Bug with comparing a Date field to the $DATE$ keyword in a
table fields qualification???
How did you know that's my favorite soda after coke :-)
Joe
-Original Message-
From: Action Request System discussion list(ARSList)
[mailto:[EMAIL PROTECTED] Behalf Of Opela, Gary L Contr OC-ALC/ITMA
Sent: Tuesday, August 21, 2007 10:38 AM
To: arslist@ARSLIST.ORG
Subject: Re: Bug with comparing a Date field to the $DATE$ keyword in a
table fields qualification???
Joe, I agree that the qualification SHOULD work directly in the table
field, but in my experiences, for some reason it does not.
Give out the External a try, I'll bet you a Mt. Dew (if I ever meet you)
that it will :)
Thanks,
Gary Opela, Jr
Sr. Remedy Developer
Leader Communications, Inc.
405 736 3211
-Original Message-
From: Action Request System discussion list(ARSList)
[mailto:[EMAIL PROTECTED] On Behalf Of Joe D'Souza
Sent: Tuesday, August 21, 2007 9:36 AM
To: arslist@ARSLIST.ORG
Subject: Re: Bug with comparing a Date field to the $DATE$ keyword in a
table fields qualification???
Carey, Gary,
Thanks for your notes.
Carey, mine isn't the Date/time field but the Date field so $TIMESTAMP$
cannot be used to compare it but the $DATE$ keyword would have to be
used
instead.
Gary, about using external, sure I can try that and see if it works. I
don't
yet see why this qualification shouldn't work directly from a table
field..
And yes you do need to escape keywords with a \ when used in External
Qualifications..
Cheers
Joe
-Original Message-
From: Action Request System discussion list(ARSList)
[mailto:[EMAIL PROTECTED] Behalf Of Opela, Gary L Contr OC-ALC/ITMA
Sent: Tuesday, August 21, 2007 8:43 AM
To: arslist@ARSLIST.ORG
Subject: Re: Bug with comparing a Date field to the $DATE$ keyword in a
table fields qualification???
Carey, thanks for expanding upon this, but I'm not using any keywords
such as $DATE$ or $TIMESTAMP$ in my external field's value. My situation
only worked whenever I used EXTERNAL(), and I think that Joe is probably
having the same thing.
I was suggesting he try using the EXTERNAL, and if he referenced $DATE$,
then it would have to be escaped as $\DATE$.
Thanks,
Gary Opela, Jr
Sr. Remedy Developer
Leader Communications, Inc.
405 736 3211
-Original Message-
From: Action Request System discussion list(ARSList)
[mailto:[EMAIL PROTECTED] On Behalf Of Carey Matthew Black
Sent: Tuesday, August 21, 2007 7:38 AM
To: arslist@ARSLIST.ORG
Subject: Re: Bug with comparing a Date field to the $DATE$ keyword in a
table fields qualification???
Gary, (and maybe Joe too)
I actually think the date stuff your seeing is actually related to
these details...
Ref: Workflow-Objects-700.pdf Pg 199
For example, if you have a table field with a qualification of
EXTERNAL($Qualify Field$)
and Qualify Field is a character field with a value of
('Create Date' $TIMESTAMP$) AND ('Login Name' = $USER$)
Re: Bug with comparing a Date field to the $DATE$ keyword in a table fields qualification???
I thought the NULL thingy was strange too. I didn't notice these qualifications behave differently on display only forms from regular forms though.. that's a new one to me. Did you ever raise a support call regarding that and if so what was the response you got? Not working as designed I hope.. Joe -Original Message- From: Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED] Behalf Of Opela, Gary L Contr OC-ALC/ITMA Sent: Tuesday, August 21, 2007 10:59 AM To: arslist@ARSLIST.ORG Subject: Re: Bug with comparing a Date field to the $DATE$ keyword in a table fields qualification??? Well, I'm not using either of the keywords, so I didn't have problem with those. What I had problem was the equivalent of your $Queue$ reference. For some reason, that wasn't expanding properly. It would not surprise me if the $Queue$ wasn't expanding properly for me, that you would also experience a problem with $DATE$. I think for some reason that the Display Only feature of the form must change something, because of the action I noted below with $NULL$ and the empty set working differently on Display Only forms vs. normal forms. Thanks, Gary Opela, Jr Sr. Remedy Developer Leader Communications, Inc. 405 736 3211 -Original Message- From: Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED] On Behalf Of Joe D'Souza Sent: Tuesday, August 21, 2007 9:50 AM To: arslist@ARSLIST.ORG Subject: Re: Bug with comparing a Date field to the $DATE$ keyword in a table fields qualification??? I've been that way with coke.. Anyway getting back to the thread, did you notice this on just the $DATE$ keyword or the $TIMESTAMP$ keyword as well? I am pretty sure the $TIMESTAMP$ keyword works as expected at least on version 6.3.x. I am not sure if the $DATE$ works on 6.3 as I don't think I ever had the need to use it on 6.3 table field qualifications.. Joe -Original Message- From: Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED] Behalf Of Opela, Gary L Contr OC-ALC/ITMA Sent: Tuesday, August 21, 2007 10:43 AM To: arslist@ARSLIST.ORG Subject: Re: Bug with comparing a Date field to the $DATE$ keyword in a table fields qualification??? Well, I've grown up on Mt. Dew. Anyone who knows me can attest that I have probably more Mt. Dew in my veins than blood at any one time! Thanks, Gary Opela, Jr Sr. Remedy Developer Leader Communications, Inc. 405 736 3211 -Original Message- From: Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED] On Behalf Of Joe D'Souza Sent: Tuesday, August 21, 2007 9:40 AM To: arslist@ARSLIST.ORG Subject: Re: Bug with comparing a Date field to the $DATE$ keyword in a table fields qualification??? How did you know that's my favorite soda after coke :-) Joe -Original Message- From: Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED] Behalf Of Opela, Gary L Contr OC-ALC/ITMA Sent: Tuesday, August 21, 2007 10:38 AM To: arslist@ARSLIST.ORG Subject: Re: Bug with comparing a Date field to the $DATE$ keyword in a table fields qualification??? Joe, I agree that the qualification SHOULD work directly in the table field, but in my experiences, for some reason it does not. Give out the External a try, I'll bet you a Mt. Dew (if I ever meet you) that it will :) Thanks, Gary Opela, Jr Sr. Remedy Developer Leader Communications, Inc. 405 736 3211 -Original Message- From: Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED] On Behalf Of Joe D'Souza Sent: Tuesday, August 21, 2007 9:36 AM To: arslist@ARSLIST.ORG Subject: Re: Bug with comparing a Date field to the $DATE$ keyword in a table fields qualification??? Carey, Gary, Thanks for your notes. Carey, mine isn't the Date/time field but the Date field so $TIMESTAMP$ cannot be used to compare it but the $DATE$ keyword would have to be used instead. Gary, about using external, sure I can try that and see if it works. I don't yet see why this qualification shouldn't work directly from a table field.. And yes you do need to escape keywords with a \ when used in External Qualifications.. Cheers Joe -Original Message- From: Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED] Behalf Of Opela, Gary L Contr OC-ALC/ITMA Sent: Tuesday, August 21, 2007 8:43 AM To: arslist@ARSLIST.ORG Subject: Re: Bug with comparing a Date field to the $DATE$ keyword in a table fields qualification??? Carey, thanks for expanding upon this, but I'm not using any keywords such as $DATE$ or $TIMESTAMP$ in my external field's value. My situation only worked whenever I used EXTERNAL(), and I think that Joe is probably having the same thing. I was suggesting he try using the EXTERNAL, and if he referenced $DATE$, then it would have to be escaped as $\DATE$. Thanks, Gary Opela, Jr Sr. Remedy Developer Leader Communications, Inc. 405 736 3211 -Original Message- From: Action
Re: Bug with comparing a Date field to the $DATE$ keyword in a table fields qualification???
What do your SQL logs say is being used for the qualification?
Thad Esser
Remedy Developer
Argue for your limitations, and sure enough, they're yours.-- Richard
Bach
Joe D'Souza [EMAIL PROTECTED]
Sent by: Action Request System discussion list(ARSList)
arslist@ARSLIST.ORG
08/21/2007 07:36 AM
Please respond to
arslist@ARSLIST.ORG
To
arslist@ARSLIST.ORG
cc
Subject
Re: Bug with comparing a Date field to the $DATE$ keyword in a table
fields qualification???
Carey, Gary,
Thanks for your notes.
Carey, mine isn't the Date/time field but the Date field so $TIMESTAMP$
cannot be used to compare it but the $DATE$ keyword would have to be used
instead.
Gary, about using external, sure I can try that and see if it works. I
don't
yet see why this qualification shouldn't work directly from a table
field..
And yes you do need to escape keywords with a \ when used in External
Qualifications..
Cheers
Joe
-Original Message-
From: Action Request System discussion list(ARSList)
[mailto:[EMAIL PROTECTED] Behalf Of Opela, Gary L Contr OC-ALC/ITMA
Sent: Tuesday, August 21, 2007 8:43 AM
To: arslist@ARSLIST.ORG
Subject: Re: Bug with comparing a Date field to the $DATE$ keyword in a
table fields qualification???
Carey, thanks for expanding upon this, but I'm not using any keywords
such as $DATE$ or $TIMESTAMP$ in my external field's value. My situation
only worked whenever I used EXTERNAL(), and I think that Joe is probably
having the same thing.
I was suggesting he try using the EXTERNAL, and if he referenced $DATE$,
then it would have to be escaped as $\DATE$.
Thanks,
Gary Opela, Jr
Sr. Remedy Developer
Leader Communications, Inc.
405 736 3211
-Original Message-
From: Action Request System discussion list(ARSList)
[mailto:[EMAIL PROTECTED] On Behalf Of Carey Matthew Black
Sent: Tuesday, August 21, 2007 7:38 AM
To: arslist@ARSLIST.ORG
Subject: Re: Bug with comparing a Date field to the $DATE$ keyword in a
table fields qualification???
Gary, (and maybe Joe too)
I actually think the date stuff your seeing is actually related to
these details...
Ref: Workflow-Objects-700.pdf Pg 199
For example, if you have a table field with a qualification of
EXTERNAL($Qualify Field$)
and Qualify Field is a character field with a value of
('Create Date' $TIMESTAMP$) AND ('Login Name' = $USER$)
the table field will not produce expected results when refreshed. The
keywords will expand, producing a qualification such as
('Create Date' 05/22/02 11:00:34 AM) AND ('Login Name' = Demo)
This is not a valid query, since the date/time and character values
are not enclosed in quotation marks. To prevent the keywords from
expanding, write the qualification like this:
('Create Date' $\TIMESTAMP$) AND ('Login Name' = $\USER$)
In forms viewed on the Web, if EXTERNAL() references a field that
contains a qualification such as $Date 1$ = 'Date 2', you must add
double quotation marks around $Date 1$, like this:
$Date 1$ = 'Date 2'.
Note: In BMC Remedy User, the EXTERNAL operator reads date and time
string from the server's time. On the web, the EXTERNAL operator reads
the date and time string from client's time zone.
HTH
--
Carey Matthew Black
Remedy Skilled Professional (RSP)
ARS = Action Request System(Remedy)
Love, then teach
Solution = People + Process + Tools
Fast, Accurate, Cheap Pick two.
On 8/21/07, Opela, Gary L Contr OC-ALC/ITMA
[EMAIL PROTECTED] wrote:
Joe, try the following:
Change the table qualification to (EXTERNAL($ztmpQualification$)) AND
('Start Date' = $DATE$)
Create display only field ztmpQualification.
Create active link that sets ztmpQualification = ('Queue' = $Queue$)
Create active link that does a table refresh
You might have to end up setting ztmpQualification = ('Queue' =
$Queue$) AND ('Start Date' = $\DATE$) and your table field
qualification just to EXTERNAL($ztmpQualification$)
For some reason, a table field on a display-only form doesn't seem to
parse correctly $Field$ although the EXTERNAL() function does.
It is also worth noting that if you are pulling in data from 'Queue'
and
there is the event that the value could be $NULL$, you need to check
for
$NULL$ and for . I know you aren't doing that here, but for instance
if you had 'Queue' != $NULL$ on there, you need to change this to
('Queue' != $NULL$) AND ('Queue' != ). If the user puts value in the
'Queue' field and then backspaces over it, on a display only form,
I've
noticed that the value is no longer $NULL$, but the empty set, .
Thanks,
Gary Opela, Jr
Sr. Remedy Developer
Leader Communications, Inc.
405 736 3211
-Original Message-
From: Action Request System discussion list(ARSList)
[mailto:[EMAIL PROTECTED] On Behalf Of Joe D'Souza
Sent: Monday, August 20, 2007 11:30 PM
To: arslist@ARSLIST.ORG
Subject: Bug with comparing a Date field to the $DATE$ keyword in a
table fields qualification???
**
Listers,
I am literally pulling my hair over this.. I am
Re: Bug with comparing a Date field to the $DATE$ keyword in a table fields qualification???
Joe,
I can't remember the bug number off the top of my head, but there has been a
longstanding issue with the use of the $DATE$ keyword in workflow
qualifications when used against Date fields. The keyword incorrectly expands
to a Date/Time integer value instead of a Date integer value. It works
correctly when used in a search qualification in the client, however.
The workaround that I would normally recommend is this:
1.. On 'Window Loaded', set a hidden, display-only Date field to the value of
$DATE$ (the bug doesn't affect set fields values).
2.. In your workflow qualification (i.e., 'Run If', 'Set Fields If', 'Push
Fields If', or table field qualification), replace the $DATE$ keyword with the
field reference to the hidden display-only Date field. For example, instead of
'Start Date' = $DATE$, use 'Start Date = $zTmpCurrentDate$.
3.. For table fields, make sure the table field is triggered to refresh AFTER
the hidden display-only Date field value is set to $DATE$ (you may need to
de-select the Refresh on Entry Change property).
Hope this helps,
Thomas
- Original Message -
From: Joe D'Souza
Newsgroups: gmane.comp.crm.arsystem.general
To: arslist@ARSLIST.ORG
Sent: Monday, August 20, 2007 11:29 PM
Subject: Bug with comparing a Date field to the $DATE$ keyword in a table
fields qualification???
**
Listers,
I am literally pulling my hair over this.. I am on ARS 7.0.1 Patch 003 on
Windows 2K3SP2 and MS-SQL 2K5SP2..
I have one data form and another display only form. In the data form among
other fields I have a character field called Queue and another Date field (not
Date/Time).
I have a simple qualification using a Date field in the qualification on a
Table field. I copied the qualification below.
('Queue' = $Queue$) AND ('Start Date' = $DATE$)
This returns all the records when the table field is refreshed after having a
value of Test Queue in the Queue field irrespective of the value of the Start
Date in the underlying data form when it should have been returning only 1
record on the table field.
On the User Tool however if I search the form using advanced search
('Queue' = Test Queue) AND ('Start Date' = 8/20/2007)
I get just one record as I should given my data.
Is this a known bug with using a Date field on a table fields qualification??
Joe
__20060125___This posting was submitted with HTML in it___
___
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org ARSlist:Where the
Answers Are
Re: Bug with comparing a Date field to the $DATE$ keyword in a table fields qualification???
Now that would explain the cause of the error.. The integer converted by the
'Start Date' would then always be less than the integer converted by the
$DATE$ if it expands to the date time integer thus returning all the
records..
Joe
-Original Message-
From: Action Request System discussion list(ARSList)
[mailto:[EMAIL PROTECTED] Behalf Of Thomas Bean
Sent: Tuesday, August 21, 2007 7:17 PM
To: arslist@ARSLIST.ORG
Subject: Re: Bug with comparing a Date field to the $DATE$ keyword in a
table fields qualification???
**
Joe,
I can't remember the bug number off the top of my head, but there has been
a longstanding issue with the use of the $DATE$ keyword in workflow
qualifications when used against Date fields. The keyword incorrectly
expands to a Date/Time integer value instead of a Date integer value. It
works correctly when used in a search qualification in the client, however.
The workaround that I would normally recommend is this:
1.. On 'Window Loaded', set a hidden, display-only Date field to the
value of $DATE$ (the bug doesn't affect set fields values).
2.. In your workflow qualification (i.e., 'Run If', 'Set Fields If',
'Push Fields If', or table field qualification), replace the $DATE$ keyword
with the field reference to the hidden display-only Date field. For
example, instead of 'Start Date' = $DATE$, use 'Start Date =
$zTmpCurrentDate$.
3.. For table fields, make sure the table field is triggered to refresh
AFTER the hidden display-only Date field value is set to $DATE$ (you may
need to de-select the Refresh on Entry Change property).
Hope this helps,
Thomas
- Original Message -
From: Joe D'Souza
Newsgroups: gmane.comp.crm.arsystem.general
To: arslist@ARSLIST.ORG
Sent: Monday, August 20, 2007 11:29 PM
Subject: Bug with comparing a Date field to the $DATE$ keyword in a
table fields qualification???
**
Listers,
I am literally pulling my hair over this.. I am on ARS 7.0.1 Patch 003
on Windows 2K3SP2 and MS-SQL 2K5SP2..
I have one data form and another display only form. In the data form
among other fields I have a character field called Queue and another Date
field (not Date/Time).
I have a simple qualification using a Date field in the qualification on
a Table field. I copied the qualification below.
('Queue' = $Queue$) AND ('Start Date' = $DATE$)
This returns all the records when the table field is refreshed after
having a value of Test Queue in the Queue field irrespective of the value
of the Start Date in the underlying data form when it should have been
returning only 1 record on the table field.
On the User Tool however if I search the form using advanced search
('Queue' = Test Queue) AND ('Start Date' = 8/20/2007)
I get just one record as I should given my data.
Is this a known bug with using a Date field on a table fields
qualification??
Joe
No virus found in this outgoing message.
Checked by AVG Free Edition.
Version: 7.5.484 / Virus Database: 269.12.1/965 - Release Date: 8/21/2007
4:02 PM
___
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org ARSlist:Where the
Answers Are
Bug with comparing a Date field to the $DATE$ keyword in a table fields qualification???
Listers,
I am literally pulling my hair over this.. I am on ARS 7.0.1 Patch 003 on
Windows 2K3SP2 and MS-SQL 2K5SP2..
I have one data form and another display only form. In the data form among
other fields I have a character field called Queue and another Date field
(not Date/Time).
I have a simple qualification using a Date field in the qualification on a
Table field. I copied the qualification below.
('Queue' = $Queue$) AND ('Start Date' = $DATE$)
This returns all the records when the table field is refreshed after having
a value of Test Queue in the Queue field irrespective of the value of the
Start Date in the underlying data form when it should have been returning
only 1 record on the table field.
On the User Tool however if I search the form using advanced search
('Queue' = Test Queue) AND ('Start Date' = 8/20/2007)
I get just one record as I should given my data.
Is this a known bug with using a Date field on a table fields
qualification??
Joe
No virus found in this outgoing message.
Checked by AVG Free Edition.
Version: 7.5.484 / Virus Database: 269.12.1/963 - Release Date: 8/20/2007
5:44 PM
___
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org ARSlist:Where the
Answers Are
