This is one of those rare instances where "Direct SQL" is useful. Remedy
does not support everything, but SQL does. Actually, I believe Remedy
will perform an implicit conversion in your case, but the following
should be useful.

There are several ways to do this
CONVERT
TO_CHAR
TO_NUM
Etc., etc.

You would set up enough temporary fields to hold all breakdowns and then
you use "Direct SQL" to perform a Set Fields action

It would look something like this

Set Fields action
Read Value for Field From: SQL

SELECT TO_CHAR($Integer Field$) FROM Test_Form  WHERE
something='something'  (I probably have the syntax wrong, so check your
SQL reference book (My favorite is the "O'Reilly SQL Pocket Guide")

Name: Character field2
Value: $1$

Note: When you pick the value, a drop down called "SQL Result Column"
appears. This is the tie to the SELECT above. You can have several
variables if you wish.

You can use any SQL function like this.

Hope this helps,

Gordon M. Frank
Lockheed Martin

-----Original Message-----
From: Action Request System discussion list(ARSList)
[mailto:[email protected]] On Behalf Of David Sanders
Sent: Saturday, October 10, 2009 10:17 AM
To: [email protected]
Subject: Re: Real to Integer Comparisons

Hi Alex

You could add a new integer field to your form, and add a filter with a
Set
Fields action to set the value of SequenceNumber to the new integer
field.
This field will then always contain just the whole number part of your
sequencing number.

HTH

David Sanders
Remedy Solution Architect
Enterprise Service Suite @ Work
==========================
 
tel +44 1494 468980
mobile +44 7710 377761
email [email protected]
 
web http://www.westoverconsulting.co.uk
 

-----Original Message-----
From: Action Request System discussion list(ARSList)
[mailto:[email protected]] On Behalf Of Alexander Straph
Sent: Saturday, October 10, 2009 12:00 AM
To: [email protected]
Subject: Real to Integer Comparisons

Hi.

The client has a set up where they have a field called SequenceNumber.
This
field is a decimal number set to a precision of 2.

The reason for this is because they have "subsequence numbers", that is
it
goes like 1, 2, 3, 3.1, 3.2, 3.3, 4.

The entries are being grouped by whole number, that is 3, 3.1, 3.2, 3.3
would belong to one group.  But how to check for such numbers?

One idea that I floated was to use the TRUNC function to get the numbers
to
round down.  Then compare the sequence numbers against the truncated
number,
if they are between the truncated number and the number + 1, then that
is a
record that you're looking for.

The problem that I have is that such a comparison is likely to trigger a
type mismatch error.  Comparing a real to an integer is not supported in
any
ARS, is it (I'm using 6.3)?

Anybody got any ideas on how to do this?


      __________________________________________________________________
Looking for the perfect gift? Give the gift of Flickr! 

http://www.flickr.com/gift/

________________________________________________________________________
____
___
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
Platinum Sponsor:[email protected] ARSlist: "Where the Answers
Are"

________________________________________________________________________
_______
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
Platinum Sponsor:[email protected] ARSlist: "Where the Answers
Are"

_______________________________________________________________________________
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
Platinum Sponsor:[email protected] ARSlist: "Where the Answers Are"

Reply via email to