Yeah, that's what I was basing my implementation on.  According to the docs, if 
you add 100000000 to the number of the row selected, it is not supposed to show 
the selection.  If you simply use the row number, it is supposed to show the 
selection.  A negative number is supposed to keep it from firing the workflow.  
So, if I've understood the manual correctly, setting it to, say, -2 should 
select the second row, show the selection to the user, but not fire any 
workflow.  That is what I want to happen, but nothing seems to be happening.

Thanks,
Lyle

From: Action Request System discussion list(ARSList) 
[mailto:[email protected]] On Behalf Of Frank Caruso
Sent: Tuesday, July 14, 2009 12:37 PM
To: [email protected]
Subject: Re: Selecting a row in a table with an AL

** I do not have my Remedy docs handy but I know there is a section 
specifically on table walking and also talks about programatically selecting a 
row and whether it should or should not fire work flow. Something about adding 
1000 or 100000 to the table field.
I am not sure if you have already read this or have it available but it should 
help.

HTH

Frank

On Tue, Jul 14, 2009 at 8:39 PM, Lyle Taylor 
<[email protected]<mailto:[email protected]>> wrote:
**

Hi All,



ARS 7.1 P6



I have a situation where I need to programmatically select a row in a table.  
Based on what I've read, I should be able to do it, and I've written the code 
that I think should do it, but it's not doing it.



Basically, I have a display-only form with a table at the top that shows 
records the user can edit; the list is filtered based on the value of a couple 
selection fields.  If they select a record, is populates the area below the 
table, where the user can make and save changes.  Depending on the changes 
made, the contents of the table need to be updated to reflect the change in the 
record (or to display a newly created record).  So, I've got a situation where, 
when I save the record, in some cases I refresh the table (clearing the 
selection, if there was one), and then I walk the table to see if the current 
record is present in it, and then select it, so it's highlighted.  What I have 
is more or less like this:



ALG - Save Record

                AL - Push Record to Regular Form

                AL - Refresh Table if Necessary

                AL - Reselect Record



The Reselect Record AL simply loops over the table, incrementing a row counter 
along the way, and once it finds the matching row, it sets the row number to 
the table, something like this:



AL - Reselect Record

                Set Row Counter to 1

                Call Guide: Reselect Record



ALG - Reselect Record

AL - Select Current Record

AL - Increment Row Counter



AL - Select Current Row

Run If: 'Request ID Col' = 'Request ID'

Set Fields:

                Table = -$Row Count$ (Select the current row, but don't fire 
workflow)

Exit Guide



So, when I do active link logging, I can see it iterating over the table, 
finding the record and then setting the table to, say, -2, but the row in the 
table doesn't appear to get selected.



Am I missing something?



Thanks for your help,

Lyle Taylor




NOTICE: This email message is for the sole use of the intended recipient(s) and 
may contain confidential and privileged information. Any unauthorized review, 
use, disclosure or distribution is prohibited. If you are not the intended 
recipient, please contact the sender by reply email and destroy all copies of 
the original message.
_Platinum Sponsor: [email protected]<mailto:[email protected]> 
ARSlist: "Where the Answers Are"_

_Platinum Sponsor: [email protected] ARSlist: "Where the Answers Are"_

_______________________________________________________________________________
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
Platinum Sponsor:[email protected] ARSlist: "Where the Answers Are"

Reply via email to