RE: Witango-Talk: Dynamic ResultSet Naming

2003-06-24 Thread Harpreet Matharu
try this   <@ASSIGN NAME="service" VALUE="<@VAR RESULTSET>" SCOPE="request">   in the search results html page. -Original Message-From: Bryan Hughes [mailto:[EMAIL PROTECTED]Sent: Tuesday, June 24, 2003 9:21 AMTo: [EMAIL PROTECTED]Subject: Witango-Talk: Dy

Re: Witango-Talk: Dynamic ResultSet Naming

2003-06-24 Thread Bryan Hughes
That works, but as I said in my first post I'd rather not have to create the name variable and I'd rather not have to give the resultSet a static name then rename it in a following action. On Tuesday, June 24, 2003, at 11:24 AM, Harpreet Matharu wrote: try this   <@ASSIGN NAME="service" VALUE

RE: Witango-Talk: Dynamic ResultSet Naming

2003-06-24 Thread Ben Johansen
Hi   Since the name option is hard coded to return request scope Have you tried it without the scope   Assign the var <@ASSIGN request$dynamicname VALUE=MyDynamicName>   in the output tab of the search action place @@dynamicname   Ben Johansen - http://www.pcforge.com Authoriz

Re: Witango-Talk: Dynamic ResultSet Naming

2003-06-24 Thread Eric Weidl
Although you say you don't want to "create the name variable", according to my reading of your message, you are. My understanding is that you want to name a resultSet according to the name in the variable <@VAR request$service>. Is that so? Eric At 09:31 AM 6/24/2003, you wrote: That works,

Re: Witango-Talk: Dynamic ResultSet Naming

2003-06-24 Thread Bryan Hughes
I started out by, and what I ultimately want to work, entering static and dynamic information in the Name field for the resultSet of my search action: ResultSet Name=staticinfo_<@VAR request$dynamicinfo[@@request$moredynamicinfo,1]> In my debugging and experimenting trying to get it to work

Re: Witango-Talk: Dynamic ResultSet Naming

2003-06-24 Thread Steve Smith
I have a question based on the discussion in this thread. It has been discussed many times that performing an operation using a meta tag is more efficient than performing the same operation using an action. For example, using <@ASSIGN NAME='foobar' VALUE='10' SCOPE=USER> is more efficient than usin

RE: Witango-Talk: Dynamic ResultSet Naming

2003-06-24 Thread Ben Johansen
Actually putting the <@assign> within the results of the search action adds overhead. the default of a search action is to place the results in into a variable called "resultSet" of scope Local/Request   adding the <@assign> was so that you could move the data in the resultSet variable into

RE: Witango-Talk: Dynamic ResultSet Naming II

2003-06-24 Thread Ben Johansen
emon Mail Server Reseller http://www.pcforge.com/AltN.htm -Original Message- From: Ben Johansen [mailto:[EMAIL PROTECTED]] Sent: Tuesday, June 24, 2003 10:16 AM To: [EMAIL PROTECTED] Subject: RE: Witango-Talk: Dynamic ResultSet Naming   Hi   Since the name option is hard coded to ret