# Exported tag value doesn't match what gets exported to tags.json

**URL:** <https://forum.inductiveautomation.com/t/exported-tag-value-doesnt-match-what-gets-exported-to-tags-json/93092>\
**Category:** Ignition\
**Tags:** ignition81, scripting\
**Created:** [July 11, 2024, 3:18pm UTC](https://forum.inductiveautomation.com/t/exported-tag-value-doesnt-match-what-gets-exported-to-tags-json/93092 "2024-07-11T15:18:06Z")\
**Posts on this page:** 7\
**Page:** 1

<div class="post-metadata">

**Author:** ![bmeyers](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/bmeyers/32/37453_2.png) [@bmeyers](https://forum.inductiveautomation.com/u/bmeyers)\
**Post date:** [July 11, 2024, 3:18pm UTC](https://forum.inductiveautomation.com/t/exported-tag-value-doesnt-match-what-gets-exported-to-tags-json/93092/1 "2024-07-11T15:18:06Z")

</div>

A bit of a head scratcher here in version 8.1.17.

I have a folder of tags and UDTs that I am exporting to **tags.json**. I can see that a specific tag is set to _240_ in the designer tag browser. However, **tags.json** shows this tag is set to _183_.

Periodically, the UDT tag value will update itself to become _183_. Even if I change the value back to _240_ it will eventually revert to _183_.

I created a second UDT by copying the first UDT and renamed the instance of the UDT in this case to _myUDTname2_ to verify nobody else was writing to this tag and the problem still persists.

My questions are:

1. Why the discrepancy between what I visually see the tag is set to and what gets exported to **tags.json**?

2. How do I fix this problem?

---

<div class="post-metadata">

**Author:** ![michael.flagler](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/michael.flagler/32/26272_2.png) [@michael.flagler](https://forum.inductiveautomation.com/u/michael.flagler)\
**Post date:** [July 11, 2024, 3:20pm UTC](https://forum.inductiveautomation.com/t/exported-tag-value-doesnt-match-what-gets-exported-to-tags-json/93092/2 "2024-07-11T15:20:28Z")

</div>

So on the new tag, if you change it to 240 is it also switching back to 183? If so, how is that tag bound? Is it a memory tag? Are there any scripts inside the UDT that could be writing to it?

---

<div class="post-metadata">

**Author:** ![bmeyers](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/bmeyers/32/37453_2.png) [@bmeyers](https://forum.inductiveautomation.com/u/bmeyers)\
**Post date:** [July 11, 2024, 3:35pm UTC](https://forum.inductiveautomation.com/t/exported-tag-value-doesnt-match-what-gets-exported-to-tags-json/93092/3 "2024-07-11T15:35:06Z")

</div>

The new tag is switching back to 183. The new UDT is given a different name so I am pretty confident no external parties are interacting with it. The tag is a memory tag. There are scripts in the UDT but they do not write to it (as far as I can tell).

 ![image](https://us1.discourse-cdn.com/inductiveautomation/original/3X/6/3/63240a62881fa8b2da4973084c91bc7fd5f6108a.png)

What I did find is there is a reference tag inside a second UDT in the folder that references the memory tag in question.

 ![image](https://us1.discourse-cdn.com/inductiveautomation/original/3X/b/f/bf185b104e7ef3fcd8b97c7ba1af32a00abcfcfb.png)

If I disable the override on the value source I see the following:

 ![image](https://us1.discourse-cdn.com/inductiveautomation/original/3X/e/3/e326b336465f8ab638b5baae96bb659b2a4d7d41.png)

So I am wondering if Ignition is getting confused on all these overrides.

---

<div class="post-metadata">

**Author:** ![bmeyers](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/bmeyers/32/37453_2.png) [@bmeyers](https://forum.inductiveautomation.com/u/bmeyers)\
**Post date:** [July 11, 2024, 3:36pm UTC](https://forum.inductiveautomation.com/t/exported-tag-value-doesnt-match-what-gets-exported-to-tags-json/93092/4 "2024-07-11T15:36:54Z")

</div>

What is interesting is I have several of these machines setup the same style and they don't have this problem.

---

<div class="post-metadata">

**Author:** ![bmeyers](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/bmeyers/32/37453_2.png) [@bmeyers](https://forum.inductiveautomation.com/u/bmeyers)\
**Post date:** [July 11, 2024, 3:55pm UTC](https://forum.inductiveautomation.com/t/exported-tag-value-doesnt-match-what-gets-exported-to-tags-json/93092/5 "2024-07-11T15:55:08Z")

</div>

After some further investigation it seems that reference tags are bi-directional and once I got rid of the underlying override the export stopped producing a value property.

Problematic tag (I made it readOnly after the problem started)

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

Less problematic tag?

![image](https://us1.discourse-cdn.com/inductiveautomation/original/3X/a/e/aee1cb931dfc762a1c733a830dda5333e8f097c6.png)

---

<div class="post-metadata">

**Author:** ![michael.flagler](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/michael.flagler/32/26272_2.png) [@michael.flagler](https://forum.inductiveautomation.com/u/michael.flagler)\
**Post date:** [July 11, 2024, 5:44pm UTC](https://forum.inductiveautomation.com/t/exported-tag-value-doesnt-match-what-gets-exported-to-tags-json/93092/6 "2024-07-11T17:44:19Z")

</div>

So now with the reference tag removed, how are things reacting on your memory tag? Or am I getting things confused now?

---

<div class="post-metadata">

**Author:** ![bmeyers](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/bmeyers/32/37453_2.png) [@bmeyers](https://forum.inductiveautomation.com/u/bmeyers)\
**Post date:** [July 11, 2024, 8:11pm UTC](https://forum.inductiveautomation.com/t/exported-tag-value-doesnt-match-what-gets-exported-to-tags-json/93092/7 "2024-07-11T20:11:16Z")

</div>

So far the 183 has not returned. I think this is a case of Ignition doing something funky with my unexpected double override I had going on plus bidirectional references (which I didn't even know was a thing).
