Kevin, Uh... a Push action in a filter that fires on Submit should have the Entry ID value to be able to push to the target form.
However, if you make that filter non-phased then it will NOT have the value. Is it possible that for submit you have made this push action non-phased? -- Carey Matthew Black Remedy Skilled Professional (RSP) ARS = Action Request System(Remedy) Love, then teach Solution = People + Process + Tools Fast, Accurate, Cheap.... Pick two. On 2/28/07, Kevin Thornley <[EMAIL PROTECTED]> wrote:
So I think it's time for me to take a new approach and solicit suggestions on how others would accomplish this goal. So here goes: I have a schema that is setup as a parent/child based on the status field. On this schema is a count field used for counting all the children. I also have a fields for the parent entry id, child id and another field used for sub-status. So the intent is to have the parent count all the children that apply whenever the sub-status equals a certain value. The approach I been taking is whenever the child meets the sub-status criteria I fire a filter that pushes the entry id to the parent records child id field then another filter that fires whenever this child id changes on the parent that does a count on the child records with the same parent id & sub-status. So this all seems to work great whenever the child record gets modified that meets the conditions. The problem is when a child record gets submitted that meets the condition. The entry id does not yet exist so the filter that pushes the child's entry id the parents child id field is null so all the subsequent actions fail. Ideas ? Thanks Kevin
_______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org ARSlist:"Where the Answers Are"
