# runNameQuerry in IGNITION **URL:** \ **Category:** Ignition\ **Tags:** ignition79, scripting\ **Created:** [April 16, 2020, 3:32am UTC](https://forum.inductiveautomation.com/t/runnamequerry-in-ignition/33971 "2020-04-16T03:32:19Z")\ **Posts on this page:** 1\ **Showing post:** 3
**Author:** ![pturmel](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/pturmel/32/3295_2.png) [@pturmel](https://forum.inductiveautomation.com/u/pturmel)\ **Post date:** [April 16, 2020, 11:44am UTC](https://forum.inductiveautomation.com/t/runnamequerry-in-ignition/33971/3 "2020-04-16T11:44:26Z")
> [@BryanB](#): > > setting up a tag event on the tag Or even better, set up a tag change event in the gateway event scripts of a project. Old rant here: > [@Error Running Project Script: "project not defined"](http://forum.inductiveautomation.com/t/error-running-project-script-project-not-defined/20272/5): > > When scripting across many tags, each gets its own copy of the code. To minimize per-tag code for maintainability, you must move it a shared script. But editing or adding a shared script restarts all gateway scripts across all projects, and causes every client to at least show an update (if not auto-updating). This is astonishingly disruptive. Shared scripts should be locked down to just the most common, best tested code, and placed under some kind of change management. Gateway tag change … Note that Ignition v8's global scripting project has addressed **one** of the downsides of tag events. I still strongly recommend gateway tag change events over any of the tag events. --- _[View the full topic](https://forum.inductiveautomation.com/t/runnamequerry-in-ignition/33971)._