On a side note, be careful of that "1=0" qualification. From my experience, it works great in MSSQL and Sybase, but will do a full table scan in Oracle.
If you leave the qualification blank, and set the "If no records match" to "Create new entry" and "If any records match" to "Take no action" it will create a new record without doing a table scan first. Just be very careful to set the "If any records match" to "Take no action", otherwise you could end up modifying every record in the table. _____ From: Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED] On Behalf Of Joe DeSouza Sent: Monday, December 18, 2006 7:56 AM To: [email protected] Subject: Re: Push fields failing Tarun, If you do not include the mandatory fields, you will get an error on the interface itself to that effect that required fields without a default cannot be set to NULL. So it can't be that Ilya is facing that problem. Ilya, What is your setup like? I'm wondering if you have a 'shared' database, with this filter being corrupted using an IP to resolve the server while doing the Push Fields so it works from one server but not another? Its just a wild guess.. Open the filter and see what server name you see on the Push Fields action.. Joe ----- Original Message ---- From: Tarun Kumar SHARMA <[EMAIL PROTECTED]> To: [email protected] Sent: Monday, December 18, 2006 5:37:32 AM Subject: Re: Push fields failing Hello Ilya, Are you including all mandatory fields (e.g. Submitter etc) while creating an entry in form B by Push action with condition 1=0 ? Regards, Tarun -----Original Message----- From: Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED] On Behalf Of Ilya Romaine Sent: Monday, December 18, 2006 3:47 PM To: [email protected] Subject: Push fields failing Hello We have a form (FORM A) where workflow fires on submit of a record, this creates a record in another form (FORM B). There is no Run If Qualification on the filter which creates the record in FORM B, and the Push Field If is 0=1, create new entry if no matches, so a record should get created on every submission of FORM A. However some records submitted into FORM A do not create a FORM B, there are not messages in the error logs and I can't find anything in the Filter/API/SQL logs. Remedy have said it could be something to do with nextid and arschema getting locked. FORM A is busy (5000 per day), but not so busy IMO that we should experience problems with nextid and arschema. Has anyone had a similar issue, or does anyone have any ideas? Cheers Ilya __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com __20060125_______________________This posting was submitted with HTML in it___ _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org ARSlist:"Where the Answers Are"
