# Tag Path dependent on System Name

**URL:** <https://forum.inductiveautomation.com/t/tag-path-dependent-on-system-name/54412>\
**Category:** Ignition\
**Tags:** ignition81\
**Created:** [December 22, 2021, 10:08pm UTC](https://forum.inductiveautomation.com/t/tag-path-dependent-on-system-name/54412 "2021-12-22T22:08:38Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Bryan\_Mason](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/bryan_mason/32/30612_2.png) [@Bryan\_Mason](https://forum.inductiveautomation.com/u/Bryan_Mason)\
**Post date:** [December 22, 2021, 10:08pm UTC](https://forum.inductiveautomation.com/t/tag-path-dependent-on-system-name/54412/1 "2021-12-22T22:08:38Z")

</div>

I was trying to export views from one gateway to another and discovered that my power chart was broken because the Tag Path (under Edit Pens) depends on the name of the gateway to find the correct OPC path. For example, the tag path is:

histprov:SQLSERVER\_WinAuth:/drv:my\_ignition\_server:default:/tag:mytags/mytag

![image](https://us1.discourse-cdn.com/inductiveautomation/original/3X/7/8/786a6105c01e691cc247a54f235ef67cbd46142f.png)

This dependency enforces that my Ignition System Name is the same for every environment in order for the project to be deployable. I’d like to have different system names between environments to distinguish them. Why does the tag depend on this information? Could the Ignition System Name be accessed through an environment variable instead?

Is this a feature for tag-sharing across gateways?

---

<div class="post-metadata">

**Author:** ![jespinmartin1](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/jespinmartin1/32/57175_2.png) [@jespinmartin1](https://forum.inductiveautomation.com/u/jespinmartin1)\
**Post date:** [December 23, 2021, 5:09am UTC](https://forum.inductiveautomation.com/t/tag-path-dependent-on-system-name/54412/2 "2021-12-23T05:09:49Z")

</div>

Update the name on DB table to match the name of new server name
