Re: Transaction Diary - Change Flag

[Brien Dieterle]

** Or, more likely, you'll need the filter to fire specifically for each field that you want to monitor- something like: Field1 != DB.Field1 OR Field2 !=DB.Field2 and so on.  You won't be able to just say "don't fire if only this one field is modified" because what if there are other fields modified too? Or, better yet, forget the whole diary thing and use an audit form.  The audit functions are more closely aligned to what you are doing-- you can set the field you are talking about to "Copy" and leave the others as Audit and Copy.  Then replace the Diary button with a button that queries the audit form and you have nearly the same thing as a Diary, but better. Brien On 11/4/2011 8:14 AM, LJ LongWing wrote: ** Andy, The change flag has little to do with the entry in the diary.  The diary is being updated by the Filter.  If you have situations where you don’t want the diary updated, you will need to update the run-if qualification of your filter to have it not fire in those situations.   From: Action Request System discussion list(ARSList) [mailto:arslist@ARSLIST.ORG] On Behalf Of Mayfield, Andy L. Sent: Friday, November 04, 2011 8:58 AM To: arslist@ARSLIST.ORG Subject: Transaction Diary - Change Flag   ** We have a filter that creates an entry in the transaction diary anytime the form is modified.   Would disabling the “change flag” on a field not keep this from running?   I seem to be generating entries in the transaction diary even though I have the “Disable Change Flag” set on the field that’s changing.   Andy L. Mayfield Alabama Power Company Protection & Control Technician Sr. Linc # 10*19140 Cell # 205-288-9140 Office # 205-226-1805   _attend WWRUG12 www.wwrug.com ARSlist: "Where the Answers Are"_ _attend WWRUG12 www.wwrug.com ARSlist: "Where the Answers Are"_ _attend WWRUG12 www.wwrug.com ARSlist: "Where the Answers Are"_