Another option would be to use a Direct SQL Action. Matt
> 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" > > _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org attend wwrug10 www.wwrug.com ARSlist: "Where the Answers Are"
