Fred, That seemed to work very well, all in one filter. Here's my computed value incase someone can use it. ((( "HD" + DATENUM( "yyyy", $DATE$)) + LPAD(DATENUM( "mm", $DATE$), 2, "00")) + LPAD(DATENUM( "dd", $DATE$), 2, "00")) + LPAD($Request ID$, 4, "0000")
My result was: HD200704230010 Thanks Steve On 4/23/07, Grooms, Frederick W <[EMAIL PROTECTED]> wrote:
** Actually I would use a filter to push the value to the new field. Since a Push action occurs in Phase 2 the Entry ID is available for use. Simply do a filter that pushes the the same record your new field data Push Fields If: $Entry ID$ = 'Entry ID' Field: YourNewField Value: Your computed value Fred ------------------------------ *From:* Action Request System discussion list(ARSList) [mailto: [EMAIL PROTECTED] *On Behalf Of *Steven Pataray *Sent:* Sunday, April 22, 2007 11:15 PM *To:* [email protected] *Subject:* Re: Date in Case number ** I can create a character field that displayes the HDyyyyddmm using the LPAD and DATENUM functions in an Active link but I don't know how to get the next Entry ID since the LASTID would get the last entry id since I have to use Execute On After Submit. How could I be sure that I'll always get the correct sequence number if it's After Submit since someone else could possibly submit before the transaction is complete? Thanks guys, I can use your recommendations to fuel my justification not to do this. Steve On 4/22/07, Rick Cook < [EMAIL PROTECTED]> wrote: > > I agree with Matt - see if he can get by with just a displayed number > that's > formatted like he wants - create a new field into which to dump that > reformatted Entry ID without mucking with what you already have. You > could > maybe compromise by agreeing to send that new field out in a few key > notifications and/or use it for reports, without having to rebuild all > of > the workflow associated with Field ID #1. > > Rick > > -----Original Message----- > From: Action Request System discussion list(ARSList) > [mailto:[EMAIL PROTECTED] On Behalf Of Carey Matthew Black > Sent: Saturday, April 21, 2007 6:30 PM > To: [email protected] > Subject: Re: Date in Case number > > Steven, > > I would strongly suggest that you NOT alter the field 1 value. Add a new > field. Do your business logic there and then propagate those changes to > the > table fields/forms of interest too. Simply add the time/cost of all of > those > changes and inform your management of the impact to the application and > any > future upgrades. See how much they think this is really worth. > > Generally I find that when you can use existing functionality (AKA: > 'Create Date') and not have to do additional, expensive, and difficult > to > maintain "enhancements" appeals to most management types. > > -- > 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 4/20/07, Steven Pataray <[EMAIL PROTECTED] > wrote: > > ** My managment would like to have a date included our HelpDesk Case > > number i.e. HD20070420xxxxx. The xxxxx would be the actual sequential > case > number. > > They would use this so they know what day a ticket was created. I > > really don't want to create another field with this number appended to > > each other since a lot of the reports and table queries are based on > the > Case number. > > Does anyone have any advise how I can achieve this? > > > > Thanks > > Steve > > > > ARS/HelpDesk 6.3 patch 19 > > Oracle 10g R1 Clustered > > Application server Windows 2003 > > > __20060125_______________________This posting was submitted with HTML in it___
_______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org ARSlist:"Where the Answers Are"
