You can combine the two Filter #1's below too.
Use the second Set field If: Qualification (include AND 'Request ID'
!= $Request ID$). It will work just as well for Submit as it does
modify.
The basic idea is "Test4Dup" that was published back in the days of
old in an RxPress. ( Circa 91? 92?)
The only "gotcha" is that it does not work for multiple transaction
that are taking place right now. (AKA: before the first transaction is
committed to the RDBMS.) One POSSIBLE way to get around that is to do
a Filter non-phased Push to a second form with data the you would us
in the Test4Dup logic. Then issue a Application-Release-Pending and
have your Test4Dup logic run on the target form for the Push action. I
think that will catch the second record even if the first parent
record is not yet committed to the RDBMS. (But I have not tested that
idea. Bugs may abound...)
--
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 10/13/06, Grooms, Frederick W <[EMAIL PROTECTED]> wrote:
**
Sure ... You can do a simple Set Fields action to set a Display Only temp
field as an indicator. A second filter then checks the indicator to see if
the value exists.
Example
Scenario: Regular Remedy form called FormA with only default fields (plus
a 15 char display only field called zTmpDupID). You want to make sure users
don't enter a short description twice.
Submit version
Filter 1 On Submit
Action 1:
Set fields Read value from FormA
Set Fields If: 'Short Description' = $Short Description$
No Requests Match Set to $NULL$
Any Requests Match Use First Matching
Set zTmpDupID = $Request ID$
Modify version
Filter 1 On Modify
Action 1:
Set fields Read value from FormA
Set Fields If: 'Short Description' = $Short Description$ and
'Request ID' != $Request ID$
No Requests Match Set to $NULL$
Any Requests Match Use First Matching
Set zTmpDupID = $Request ID$
Filter 2
If zTmpDupID != $NULL$ Show Error to prevent save
Hope this info helps
Fred
________________________________
From: Action Request System discussion list(ARSList)
[mailto:[EMAIL PROTECTED] On Behalf Of Sullivan, Neil G CTR USAF
AFRL/SNOX
Sent: Friday, October 13, 2006 8:08 AM
To: [email protected]
Subject: Duplicate Records
**
Listers,
Is there any way possible to use workflow to check for duplicate records in
a form without using a unique index? I can't use an index because some of
the values in the field will be null.
Any help is appreciated.
Neil "Sully" Sullivan
Remedy Developer/Administrator
AFRL/SNOX
Wright Patterson AFB, OH 45433
937-904-9788
_______________________________________________________________________________
UNSUBSCRIBE or access ARSlist Archives at http://www.wwrug.org
