Re: Problem with Push Fields in a Table Loop (RESOLVED)

** Thank you all!I solved my problem appending '! in the end of the filter's name. Then it works because with that, actions are executed in the desired order, because normally, without '!, push fields actions are delayed into a later phase and executed as a bulk after the Set Fields actions.

Problem with Push Fields in a Table Loop

** A filter A calls a Filter Guide B looping a table. This Filter Guide B contains a filter that should execute a push fields in another form.But there's a problem: it always push the same data. It's not a mistake with the Table I'm looping, because I tested using set fields and displayed

Re: Problem with Push Fields in a Table Loop

** Make sure that If any Requests match is set to ModifyFirst Matching Request. -Original Message- From: [EMAIL PROTECTED] To: arslist@ARSLIST.ORG Sent: Thu, 26 Oct 2006 9:19 AM Subject: Problem with Push Fields in a Table Loop ** A filter "A" calls a Filter Guide &

Re: Problem with Push Fields in a Table Loop

Hi Alex, You should add `! to the filter name to ensure that the actions are executed in the desired order. Push fields actions are otherwise delayed into a later phase and executed as a bulk after the Set Fields actions.. You can find further details on the phases and their purpose in the

Re: Problem with Push Fields in a Table Loop

Alex, I experienced a similar problem before, I believe I solved it creating a set field action to pass the column values to a display only field, and then use the display only fields on the push field action. Alfredo --- Alex Bredariol [EMAIL PROTECTED] wrote: A filter A calls a Filter

Re: Problem with Push Fields in a Table Loop

: Problem with Push Fields in a Table Loop Alex, I experienced a similar problem before, I believe I solved it creating a set field action to pass the column values to a display only field, and then use the display only fields on the push field action. Alfredo --- Alex Bredariol [EMAIL PROTECTED