Filter loops are in my experience ok when used to pull a table off a form that isn't too thick and would not return a large number of results within the table..
Else in my experience, you could have a problem with them.. On the other hand if you can do the same thing without using a filter loop within a filter guide, I would opt for the option without a server side table. It's definitely way faster. But thats through my experience, I'm not quite sure what Remedy's reccomendation on this would be...
I've also noticed that you can do without a server side table in most cases.
I would generally use a table field only for client side viewing purposes where you have no choice but use a table field to dislay information to the user. But if you need a table specifically for the purpose of workflow, to process the contents of the table and do not need it to be visible to the user, I would generally try to find a possibility to avoid building that table field in the first place and try to achieve everything through workflow, and if I see no other way, then go for the table field approach..
My 2 cents..
Cheers
Joe D'Souza
Remedy Developer / Consultant,
BearingPoint,
Virginia.
----- Original Message ----
From: Jason Miller <[EMAIL PROTECTED]>
To: [email protected]
Sent: Tuesday, August 22, 2006 1:38:07 PM
Subject: OT: Why oh why oh why won't this work.....
** A bit off topic regarding server-side tables...
I had the same performance concerns that Joe mentioned before I created my first server-side filter loop. Since then I have used them in a number of places (where appropriate, not the right tool for every job). I have found them to be surprisingly fast. I remember reading some place that they are a good choice for performance because of the way they work at the DB level. Now granted we are not a very large implementation compared to number of you out there. Has anybody noticed any performance issues with server-side filter loops? If so how many records are involved in your process?
Jason
From: Jason Miller <[EMAIL PROTECTED]>
To: [email protected]
Sent: Tuesday, August 22, 2006 1:38:07 PM
Subject: OT: Why oh why oh why won't this work.....
** A bit off topic regarding server-side tables...
I had the same performance concerns that Joe mentioned before I created my first server-side filter loop. Since then I have used them in a number of places (where appropriate, not the right tool for every job). I have found them to be surprisingly fast. I remember reading some place that they are a good choice for performance because of the way they work at the DB level. Now granted we are not a very large implementation compared to number of you out there. Has anybody noticed any performance issues with server-side filter loops? If so how many records are involved in your process?
Jason
On 8/22/06, Joe DeSouza <[EMAIL PROTECTED]> wrote:
**Stephen,I did something very similar.. in fact mine might be even more complicated since I had to build a External filter qualification to check for database values of fields against transactional...My requirement instead of making the field required was to audit fields that were contained on form 2.. Whenever there was a change on form 1, on any of the fields contained on form 2, to audit those fields by pushing the changes into form 3...I even did this without the use of a table field :-) to run the loop over by running a filter loop since I HATE server side Table fields because of possibile performance concerns...So where is it failing for you?? What I have done here works perfect for me.. maybe I might be able to throw in a clue as to where you might be going wrong...Cheers
Joe D'SouzaRemedy Developer / Consultant,BearingPoint,Virginia.
----- Original Message ----
From: Stephen Earl < [EMAIL PROTECTED]>
To: [email protected]
Sent: Tuesday, August 22, 2006 10:25:08 AM
Subject: Why oh why oh why won't this work.....
I have 2 forms.... data form and form containing a list of required fields for the data form, lets call the form 1 (data) and form 2 (required fields)
Form 2 contains 2 fields 'form name' and 'field name' on form 1 we have a table field containing 2 columns from form 2 showing records where form name equals the form name of form 1
What I want to achieve is an AL guide that runs across the table and checks the field name listed in the table and tests for it being NULL however it appears there isn't a way with remedy workflow to achieve this 'simple' operation.
so basically what I have is a field name in another field and I want to test if that field's content is null or not, should be simple appears it isn't unless I'm missing something REALLY obvious....
All help and suggestions welcomed :-)
Stephen
