Hi Joe:
Thanks for the explanation. I had forgotten about to use push fields,
etc to force a filter into a later phase.
As for the reason I'm doing this ... it would be fine to simply use
the 'request id' field, BUT users may submit values into 'optional
field' which would override the 'request id' value. So the case is
that 'optional field' should contain the 'request id', unless it was
overridden by a different value from the user.
thanks again everyone for helping so thoroughly and quickly.
-Andy
On Aug 26, 2008, at 5:18 PM, Joe DeSouza wrote:
**
Andy,
May I ask why not use the Request ID field itself for whatever you
are doing if all you want to do is copy the value of the Request ID
field itself to that field that you have created?
The reason you do not see the request id field in ordinary set field
actions is that set field actions happen on the first phase. During
that first phase the transaction hasn't yet hit the database, and
the new Request ID is not yet available and hence its value is $NULL
$ at that time. Second and third stage actions happen after the
request is committed to the database and these actions would have
the Request ID available.
If whatever you are trying to accomplish can be completed with any
of the second or third stage actions, then you could use those to
access the value of the Request ID field..
Joe
----- Original Message ----
From: Andrew Hicox <[EMAIL PROTECTED]>
To: [email protected]
Sent: Tuesday, August 26, 2008 5:34:59 PM
Subject: how to copy 'request id' to other field on submit
Hello everyone:
I have a seemingly simple thing I'd like to do.
I have a form, and an optional field on that form. If the optional
field is $NULL$ upon submit, I'd like to copy the 'request id' (i.e.
"ticket number", fieldid = 1) into this field.
Filters do not seem to catch this, as they execute before commit.
Things I have tried.
Filter on Submit where 'optional field' = $NULL$ and 'request id' !=
'DB.request id'
Filter on Modify with same qualification
Filter on Modify & Submit with same qualification
All of the above at execution order 0 and the absurdly high value of
999
setting $LASTID$ as the default value of 'optional field' works, but
again because it is BEFORE the commit, it gets the previous 'request
id' value, not the one that will belong to the record I'm in.
SO ... is there a proper way to do this (other than leaving
'optional field' null and having an escalation come along and fix it
for me?)
thanks everyone,
-Andy
__Platinum Sponsor: www.rmsportal.com ARSlist: "Where the Answers
Are" html___
_______________________________________________________________________________
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
Platinum Sponsor: www.rmsportal.com ARSlist: "Where the Answers Are"
