Looks like it's the use of request id's in the push field qualification. This won't match records in the two forms.
Why not push the GUID (assuming it's unique) into the lookup table along with the vendor form data. Then, using $GUID$ = 'GUID' you won't duplicate records on the second and subsequent passes. _____ From: Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED] On Behalf Of Cupp, Michael E Jr. CTR USAF AFRL/SNOD Sent: 26 January 2007 19:32 To: [email protected] Subject: Issues with Escalation Importance: High I have an escalation I have created on a vendor form, which queries my LDAP. On the basic tab, my run if is ( 'sourceObjectGUID' != $NULL$ ) AND ( 'sn' LIKE "CU%" ) I want only records with a GUID populated and last name starts with CU On the If action, I have 1 action, it is a push fields. I am pushing the value to Customer Lookup, and the push field if is $Request ID$ = 'Request ID' If No Requests match create a new and if any requests match modify the first I then list my fields, and their corresponding values. When this runs 1st, it does EXACTLY what I expect it to, against an empty table (Customer Lookup), it creates records for each Vendor Form record that matches the above run if clause. When it runs subsequent, instead of UPDATING the existing records, it ADDs new ones, thus creating duplicates in my Customer Info table. Does anyone have any ideas why? --- Michael Cupp, Jr., Contractor, RCF Oracle Database Administrator AFRL EBS Helpdesk Team Lead AFRL/SNOD Enterprise Operations Center Wright-Patterson AFB, Ohio DSN 785-3827 __20060125_______________________This posting was submitted with HTML in it___ _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org ARSlist:"Where the Answers Are"
