# Auditing Setpoint Changes

**URL:** <https://forum.inductiveautomation.com/t/auditing-setpoint-changes/17844>\
**Category:** Ignition\
**Tags:** database, ignition79\
**Created:** [April 26, 2018, 8:33pm UTC](https://forum.inductiveautomation.com/t/auditing-setpoint-changes/17844 "2018-04-26T20:33:05Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![mbhagotra](https://avatars.discourse-cdn.com/v4/letter/m/b9e5f3/32.png) [@mbhagotra](https://forum.inductiveautomation.com/u/mbhagotra)\
**Post date:** [April 26, 2018, 8:33pm UTC](https://forum.inductiveautomation.com/t/auditing-setpoint-changes/17844/1 "2018-04-26T20:33:06Z")

</div>

Hello all,

I’m wondering if it was possible for Ignition’s built-in auditing tool to store a setpoint’s old value when it is changed? I see that it only stores the new value in the database at the moment.

I like the built-in auditing tool because it also stores information that I require like which client committed the action and the timestamp. I was thinking if there is nothing built in for the old value then I must add a script to the setpoint tags’ ‘Value Changed’ Tag Event script. Any input would be appreciated.

Thanks for reading!

---

<div class="post-metadata">

**Author:** ![mbhagotra](https://avatars.discourse-cdn.com/v4/letter/m/b9e5f3/32.png) [@mbhagotra](https://forum.inductiveautomation.com/u/mbhagotra)\
**Post date:** [April 26, 2018, 10:28pm UTC](https://forum.inductiveautomation.com/t/auditing-setpoint-changes/17844/2 "2018-04-26T22:28:11Z")

</div>

For anyone else looking into this this post is quite relevant: [Tag Event Script 'Value Changed' firing twice?](http://forum.inductiveautomation.com/t/tag-event-script-value-changed-firing-twice/17709)