Alan, As others pointed out, you aren't missing anything....but what you can do is have auditing turned on, this will capture the first modification of a field at submit. Then create a 'self join' of the audit form joining two subsequent entries of each other....the first entry will contain the 'old value', the second entry will contain the 'new value', and you won't need to create workflow to get this information. To create the self join you may need to use an SQL View...but the premise is basically the max(original request id) where original request id is < original request id....this gives you the last entry created for this record...
-----Original Message----- From: Action Request System discussion list(ARSList) [mailto:arsl...@arslist.org] On Behalf Of R. Alan Monroe Sent: Thursday, December 03, 2009 6:19 PM To: arslist@ARSLIST.ORG Subject: Am I not understanding auditing? I was experimenting with the built-in auditing for the first time on a test server, in log mode. Unless I'm missing something really obvious, it seems to just record the same thing in both the regular record and the log. For example, if I change a serial number from 123 to 123a, I see 123a recorded in both the record of the main form and the corresponding entry in the log form. This seems completely worthless to me since I very much want to record the FORMER value during audit, not the CURRENT value. What am I missing? Alan ____________________________________________________________________________ ___ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org Platinum Sponsor:rmisoluti...@verizon.net ARSlist: "Where the Answers Are" _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org Platinum Sponsor:rmisoluti...@verizon.net ARSlist: "Where the Answers Are"
