Your hidden field is a Date field?  Try the following

In a Filter (or AL) 
 Action 1: Set you hidden Date field to:  DATEADD( "yyyy", 6, DATE($Expiration 
Date$))

Fred


-----Original Message-----
From: Action Request System discussion list(ARSList) 
[mailto:[email protected]] On Behalf Of Kemes, Lisa
Sent: Monday, December 28, 2009 9:17 AM
To: [email protected]
Subject: Re: Epoch time rollover issue for dates past 2037

Weird,

I'm running into the EXACT same issue.  I need to delete records that are 6 
years old, so I added a Date/Time field (hidden) and added 6 years to the 
Expiration Date and set my hidden Date/Time field to this date.  Problem is 
that some people had 2037 as a year for their expiration date and I got 
1/1/1969 for the hidden field because of this limitation.  

So I changed it to a Date field, tried the same thing and now I'm getting 
1/1/9999.  I know you can't add seconds/days/hours to a Date field.  I'm 
setting this field with $Expiration Date$ + ((((6 * 365) * 24) * 60) * 60).  
Expiration Date is a Date/Time Field.

So, now I don't know what to do.  Set a character field and THEN set the Date 
field maybe?


Lisa

-----Original Message-----
From: Action Request System discussion list(ARSList) 
[mailto:[email protected]] On Behalf Of Reiser, John J
Sent: Wednesday, December 23, 2009 1:16 PM
To: [email protected]
Subject: Re: Epoch time rollover issue for dates past 2037

@Matt,
 I'm probably going to build a Dialog that lets them select the date they need, 
store it as a DATE field for workflow and display YYYMMDD (at the request of 
the user).

My RFE will probably be to get the same interface for DATE fields (calendar 
widget) with the ability to type in any year value.

@Mark,
Yes I will be doing those types of error trapping.


Thanks,

---
John J. Reiser
Senior Software Development Analyst
Remedy Administrator/Developer
Lockheed Martin - MS2
The star that burns twice as bright burns half as long. 
Pay close attention and be illuminated by its brilliance. - paraphrased by me 
-----Original Message-----
From: Action Request System discussion list(ARSList) 
[mailto:[email protected]] On Behalf Of Carey Matthew Black
Sent: Wednesday, December 23, 2009 9:14 AM
To: [email protected]
Subject: Re: Epoch time rollover issue for dates past 2037

John,

Given all that you said....

I would suggest that you do all of the following:

1) Use a UI that you build ( if you do not like the default UI )
    A display only dialog, called from a custom button and suppress
the OOB UI for the field.
    If you have to ... go all the way to a DVF for a custom "Web'ish" UI.

2) Use either a Date field or a Char field ( up to you ) to hold the data.
    My two cents... use a Date field. It makes doing math much easier
than using strings.

3) Submit an RFE for what you want the product to do (or not do).

HTH.

-- 
Carey Matthew Black
BMC Remedy AR System Skilled Professional (RSP)
ARS = Action Request System(Remedy)

Love, then teach
Solution = People + Process + Tools
Fast, Accurate, Cheap.... Pick two.



On Tue, Dec 22, 2009 at 3:23 PM, Reiser, John J <[email protected]> wrote:
> **
>
> Hello Listers,
>
> ARS 7.1 Patch 004
>
> MS SQL 2005
>
>
>
> We have a need to record an end date greater than 2037 and the Date/Time
> fields are restricted by the 32 bit integer of Epoch Time.
>
> I prefer to avoid Date only fields because of the widget and the BC check
> box.
>
> Do Date only fields cause any workflow headaches? I will probably need to
> check End Dates against the current date when records are entered and
> retrieved.
>
> Example. Don't let a date be set in the past. Lock out changes to a record
> if the End Date has passed when the record is opened. Etc.
>
> Just looking for a sanity check. Is there a better work around like
> formatting the date to a character field (YYYYMMDD) or do I just use the
> Date only because "it's fully supported by BMC and it was designed to
> address this type of issue."
>
>
>
> Merry Christmas to all.
>
> Thanks,
>
> ---
> John J. Reiser
> Senior Software Development Analyst
> Remedy Administrator/Developer
> Lockheed Martin - MS2
> The star that burns twice as bright burns half as long.
> Pay close attention and be illuminated by its brilliance. - paraphrased by
> me

_______________________________________________________________________________
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"

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

Reply via email to