Hi Misi,Hany.... so on :) Although this is something which i had tried, the problem here is that although i would stop this very filter executing in this form through a 'DoNotFireMySubmitFilter'/flag , at the same time i have many other filters running on a submit again with many complex qualification and which would need to run many times in the same form. And lets just say i introduce this particular 'DoNotFireMySubmitFilter' for all the other filters on the same form it would end me up letting the other filters getting executed only once for the life time of the record. So I cant go ahead with this. I was rather trying through a set field in activelink and then doing a commit but very wierdly it closes the AR user window!
Misi Mladoniczky wrote: > > Hi, > > Why not do a set-fields on the CURRENT TRANSACTION instead? > > If that is not possible, you can allways create a Display-Only-field > called something like DoNotFireMySubmitFilter=Yes, and skip the filter if > it is set. > > Best Regards - Misi, RRR AB, http://www.rrr.se > > Products from RRR Scandinavia: > * RRR|License - Not enough Remedy licenses? Save money by optimizing. > * RRR|Log - Performance issues or elusive bugs? Analyze your Remedy logs. > Find these products, and many free tools and utilities, at http://rrr.se. > >> Hi fellow listers, >> >> This is something which i had tried. >> >> My need was to change a field value in a form after a record is >> submitted/modified and the record for which i need the field value change >> to >> be made is the one which got submitted/modified. >> >> So I created a filter which gets triggerred(i.e on action Submit and >> Modify)and then do a push field and change the value in the field for the >> same form-record. >> >> Now my problem here is that as I am doing the push in the same form for >> changing a value in the field, "ARERR 299 Too many levels in filter >> processing" occurs. I know this happens because the Push field action >> ultimately triggers a submit/modify action on the same form and the >> filter >> get triggerred infinitely. >> >> Can anyone suggest me a different approach to this? >> >> Cheers :) >> -- >> View this message in context: >> http://old.nabble.com/ARERR-299-Too-many-levels-in-filter-processing-tp28750990p28750990.html >> Sent from the ARS (Action Request System) mailing list archive at >> Nabble.com. >> >> _______________________________________________________________________________ >> UNSUBSCRIBE or access ARSlist Archives at www.arslist.org >> attend wwrug10 www.wwrug.com ARSlist: "Where the Answers Are" >> >> -- >> This message was scanned by ESVA and is believed to be clean. >> > > _______________________________________________________________________________ > UNSUBSCRIBE or access ARSlist Archives at www.arslist.org > attend wwrug10 www.wwrug.com ARSlist: "Where the Answers Are" > > -- View this message in context: http://old.nabble.com/ARERR-299-Too-many-levels-in-filter-processing-tp28750990p28776247.html Sent from the ARS (Action Request System) mailing list archive at Nabble.com. _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org attend wwrug10 www.wwrug.com ARSlist: "Where the Answers Are"
