Hi Brien What you are describing is definitely *not* a normalized data structure as you are storing and maintaining the linked data in your main form... but leaving that aside.
The suggestion from Fred would work for small data volumes, but as soon as you are updating larger volumes you will have performance problems and hit the AR server filter limit, so assuming you still need the scheduled escalation to sync your data... Create your own Modified Date and Last Modified By fields and set values in these fields through a filter when the record is created or modified where $USER$ != "AR_ESCALATOR". Then in your form display your custom fields instead of the core fields. HTH David Sanders Solution Architect Enterprise Service Suite @ Work / e-ServiceSuite tel +44 1494 468980 mobile +44 7710 377761 email david.sand...@westoverconsulting.co.uk web http://www.westoverconsulting.co.uk http://www.e-servicesuite.co.uk ITIL SaaS On Premise -----Original Message----- From: Action Request System discussion list(ARSList) [mailto:arslist@ARSLIST.ORG] On Behalf Of Grooms, Frederick W Sent: 10 February 2012 03:03 To: arslist@ARSLIST.ORG Subject: Re: Escalation trigger filters without modifying records? If your "normalization" happens on every save of the record then are you having to run thru them on a schedule to update them because something somewhere else changed? i.e. If you are setting a Name field in Form AAA on save, are you trying to keep that Name field in sync with a Name somewhere else (like on Form BBB)? I would look at trying to detect when the source of Name (Form BBB) is changed and force the related records (Form AAA) to update at that time. Fred -----Original Message----- From: Action Request System discussion list(ARSList) [mailto:arslist@ARSLIST.ORG] On Behalf Of Brien Dieterle Sent: Thursday, February 09, 2012 6:13 PM To: arslist@ARSLIST.ORG Subject: Escalation trigger filters without modifying records? I've got a lot of filters that do some "normalization" by setting some key fields via a lookup. This might be a bad idea, but I generally create escalations that do some tidying up-- they just blast through all the records and update a trigger field to trigger the modify filters. Having all the records "last modified by AR_ESCALATOR" is starting to irritate some of my colleagues, so I'd like to stop doing this. Any thoughts? I've tried several ways to get an escalation to trigger the modify actions without actually modifying the record-- without any success. I also definitely do not want to duplicate the code in the modify actions and copy them into the escalation. Thanks! Brien ____________________________________________________________________________ ___ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org attend wwrug12 www.wwrug12.com ARSList: "Where the Answers Are" _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org attend wwrug12 www.wwrug12.com ARSList: "Where the Answers Are"
