Hi Akos... That kind of push can easily loop on you...
I would suggest doing one of the following: 1) Using LastId keyword to locate the ID (providing that this is the only creation initiated by this process). 2) Put a GUID on form A that gets pushed to form B. Then you can fire another filter that looks up the GUID on form B to return the form Request ID Hope this helps. On Jul 15, 5:08 am, Akos Malindovszky <jes...@vipmail.hu> wrote: > Hi all! > > 'm having a problem with the Push fields action in a Filter. > I have two forms A & B. When a ticket is created on A that matches certain > qualifications, then a new ticket is created on form B via a at Push field > action in a filter. I want to store the request-ID of the new ticket on form > A also, so there is a filter running on submit on B which pushes the info > back to the matching request on A. > My problem is that when the ID is pushed back from B to A, then A starts > running all the filters again triggered by this modification. Is there any > way to avoid this step. Can I push a value to a form without triggering a > modification? > > Thank you in advance. > > best regards, > Akos Malindovszky > Helpdesk Administrator > -- > View this message in > context:http://www.nabble.com/Push-Fields-creating-loop-tp24494356p24494356.html > Sent from the ARS (Action Request System) mailing list archive at Nabble.com. > > _______________________________________________________________________________ > UNSUBSCRIBE or access ARSlist Archives atwww.arslist.org > Platinum Sponsor:rmisoluti...@verizon.net ARSlist: "Where the Answers Are" _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org Platinum Sponsor:rmisoluti...@verizon.net ARSlist: "Where the Answers Are"
