Guys (and Gals): There are many many problems with nested table loops in Active Link Huids.
To work around them all: Do not refer to fields from the first table in the workflow or qualifications of the second table. Instead, have the first table loop guide copy the fields from the table columns to DO fields on the form not columns), then the second table qualification can refer to these fields and be refreshed and looped. This is implemented by the user tool and it seems not to stack appropriate variables for table looping and hence looses track of just about everthing. This bug has been around for some time. Cheers Ben >----- ------- Original Message ------- ----- >From: :[email protected] >To: [email protected] >Sent: Tue, 21 Aug 2007 10:11:09 > >Hi Shawn, > >If you refresh the table you are looping through, I >would think that Remedy >considers the refreshed table a new table, so you >have finished looping >through the old table, so to speak. > >I think the way to do what you want to do, is loop >through the table, do the >refresh on a second (new) table and then loop >through the second table, >using a new Active Link Guide. > >I hope this helps, assuming I have understood the >problem correctly. > >Regards, > >John Magnusssen, >London, England > >On 8/21/07, snow8261 <[EMAIL PROTECTED]> wrote: >> >> can you show your logs? >> both table looping is off and table looping is on >> >> i guess the only reason that the 3rd action of a >guide not running is >> because it is empty table,nothing to loop. >> >> On Aug 21, 2:42 am, Shawn Stonequist ><[EMAIL PROTECTED]> >> wrote: >> > Greetings List!! >> > >> > Another Table Loop issue I'm hoping you can >help with! Many thanks in >> > advance!! >> > >> > I've got an Active Link (executes on a button) >that runs an Active Link >> > Guide that includes 3 active links, and has 1 >label just before the 3rd >> AL. >> > The 3rd AL refreshes the table, sets some temp >fields based on the >> refreshed >> > table, then sets a Diary Field with the values >of those temp fields. >> > >> > When Table Looping is off, this works perfectly >(though of course, only >> > works on 1 row per button press). >> > >> > With Table Looping on, the Guide seems to >completely ignore the last >> Active >> > Link. According to the Logs, the Guide runs, >checks the first and second >> > links, runs the appropriate one, then goes to >the Label and stops. >> > >> > This is perfect except for the fact that it >stops too soon, and I see no >> > reason for it to do so. >> > >> > A little more detail if its helpful: >> > >> > The first two AL are set to check the Status in >the table, and if its >> not >> > "theirs" push their value to the child record >(e.g. the "Active Status" >> AL >> > only runs if the Status is "Inactive" and vice >verse for the second >> one), >> > then uses a "Go to Label" action to ensure that >the other AL is skipped.. >> > (here is where it all ends when Table Loop is >turned on). >> > >> > The third AL refreshes the table, sets the temp >fields in the first set >> > fields action, then uses a second set field >action to set the Diary >> field. >> > >> > Any ideas? >> > Again, thanks in advance for your help!!! >> > Shawn Stonequist >> > EMNS, Inc. >> > >> > >> >___________________________________________________ >____________________________ >> > UNSUBSCRIBE or access ARSlist Archives >atwww.arslist.orgARSlist:"Where >> the Answers Are" >> >> >> >___________________________________________________ >____________________________ >> UNSUBSCRIBE or access ARSlist Archives at >www.arslist.org ARSlist:"Where >> the Answers Are" >> > >___________________________________________________ >____________________________ >UNSUBSCRIBE or access ARSlist Archives at >www.arslist.org ARSlist:"Where the Answers Are" >** ><div>Hi Shawn, </div> ><div> </div> ><div>If you refresh the table you are looping >through, I would think that Remedy considers the >refreshed table a new table, so you have finished >looping through the old table, so to speak. </div> ><div> </div> ><div>I think the way to do what you want to do, is >loop through the table, do the refresh on a >second (new) table and then loop through the >second table, using a new Active Link Guide. </div> ><div> </div> ><div>I hope this helps, assuming I have understood >the problem correctly. <br> </div> ><div>Regards, </div> ><div> </div> ><div>John Magnusssen, </div> ><div>London, England<br> </div> ><div><span class="gmail_quote">On 8/21/07, <b >class="gmail_sendername">snow8261</b> <<a >href="mailto:[EMAIL PROTECTED]">[EMAIL PROTECTED] ></a>> wrote:</span> ><blockquote class="gmail_quote" >style="PADDING-LEFT: 1ex; MARGIN: 0px 0px 0px >0.8ex; BORDER-LEFT: #ccc 1px solid">can you show >your logs?<br>both table looping is off and table >looping is on<br><br>i guess the only reason that >the 3rd action of a guide not running is ><br>because it is empty table,nothing to >loop.<br><br>On Aug 21, 2:42 am, Shawn Stonequist ><<a >href="mailto:[EMAIL PROTECTED]">shawn.stone >[EMAIL PROTECTED]</a>><br>wrote:<br>> Greetings >List!!<br>><br>> Another Table Loop issue >I'm hoping you can help with! Many thanks in ><br>> advance!!<br>><br>> I've got an >Active Link (executes on a button) that runs an >Active Link<br>> Guide that includes 3 active >links, and has 1 label just before the 3rd >AL.<br>> The 3rd AL refreshes the table, sets >some temp fields based on the refreshed ><br>> table, then sets a Diary Field with the >values of those temp fields.<br>><br>> When >Table Looping is off, this works perfectly (though >of course, only<br>> works on 1 row per button >press).<br>><br>> With Table Looping on, the >Guide seems to completely ignore the last Active ><br>> Link. According to the Logs, the Guide >runs, checks the first and second<br>> links, >runs the appropriate one, then goes to the Label >and stops.<br>><br>> This is perfect except >for the fact that it stops too soon, and I see no ><br>> reason for it to do so.<br>><br>> A >little more detail if its helpful:<br>><br>> >The first two AL are set to check the Status in the >table, and if its not<br>> "theirs" >push their value to the child record ( >e.g. the "Active Status" AL<br>> only >runs if the Status is "Inactive" and vice >verse for the second one),<br>> then uses a >"Go to Label" action to ensure that the >other AL is skipped.<br> >> (here is where it all ends when Table Loop is >turned on).<br>><br>> The third AL refreshes >the table, sets the temp fields in the first >set<br>> fields action, then uses a second set >field action to set the Diary field. ><br>><br>> Any ideas?<br>> Again, thanks >in advance for your help!!!<br>> Shawn >Stonequist<br>> EMNS, Inc.<br>><br>> >___________________________________________________ >____________________________<br> >> UNSUBSCRIBE or access ARSlist Archives >atwww.arslist.orgARSlist:"Where the Answers >Are"<br><br>__________________________________ >_____________________________________________<br>UN >SUBSCRIBE or access ARSlist Archives at ><a >href="http://www.arslist.org";>www.arslist.org</a> >ARSlist:"Where the Answers >Are"<br></blockquote></div><br> >__20060125_______________________This posting was >submitted with HTML in it___ _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org ARSlist:"Where the Answers Are"
