I have a set fields action that just doesn't like what I'm setting the field to. I'm trying to set a date field using math; I'm trying to set Required Resolution Date (date/time field) to $TIMESTAMP$+(60*60*24*$NumberOfDays$) on some custom forms and it just doesn't work. If I set it with another date/time field, it works, but if I try and calculate time using timestamp, it doesn't. According to abydos, if I put in the calucation, the other part of the action changes from selecting from my form to "current transaction"--but this is not reflected on the screen when looking at the filter in administrator. I came up with a work around, but I wonder if this is expected behavior, if I'm doing something wrong, or if I found a weird bug. Has anyone else seen this type of thing before?
ARS 7.1 ITSM 7.0.3 CMDB 2.1 p4 Anne Ramey *********************************** E-mail correspondence to and from this address may be subject to the North Carolina Public Records Law and may be disclosed to third parties only by an authorized State Official. _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org attend wwrug10 www.wwrug.com ARSlist: "Where the Answers Are"
