# Cannot export UDT tags V7.6.6

**URL:** <https://forum.inductiveautomation.com/t/cannot-export-udt-tags-v7-6-6/8307>\
**Category:** Ignition\
**Created:** [April 14, 2014, 9:09pm UTC](https://forum.inductiveautomation.com/t/cannot-export-udt-tags-v7-6-6/8307 "2014-04-14T21:09:08Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![Curlyandshemp](https://avatars.discourse-cdn.com/v4/letter/c/bcef8e/32.png) [@Curlyandshemp](https://forum.inductiveautomation.com/u/Curlyandshemp)\
**Post date:** [April 14, 2014, 9:09pm UTC](https://forum.inductiveautomation.com/t/cannot-export-udt-tags-v7-6-6/8307/1 "2014-04-14T21:09:08Z")

</div>

Just upgraded to 64bit V7.6.6, and as part of ongoing project, I export tags and UDTs to CSV to create additional tags.

Exporting SQL tags work.

[attachment=2]ScreenHunter\_150 Apr. 14 17.03.jpg[/attachment]

Now I get the following error:  
[attachment=1]ScreenHunter\_152 Apr. 14 17.03.jpg[/attachment]  
[attachment=0]ScreenHunter\_151 Apr. 14 17.03.jpg[/attachment]

---

<div class="post-metadata">

**Author:** ![greg.simpson](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/greg.simpson/32/3135_2.png) [@greg.simpson](https://forum.inductiveautomation.com/u/greg.simpson)\
**Post date:** [April 14, 2014, 11:49pm UTC](https://forum.inductiveautomation.com/t/cannot-export-udt-tags-v7-6-6/8307/2 "2014-04-14T23:49:04Z")

</div>

This is a known issue and has been fixed for Ignition 7.6.7

---

<div class="post-metadata">

**Author:** ![Curlyandshemp](https://avatars.discourse-cdn.com/v4/letter/c/bcef8e/32.png) [@Curlyandshemp](https://forum.inductiveautomation.com/u/Curlyandshemp)\
**Post date:** [April 15, 2014, 12:30pm UTC](https://forum.inductiveautomation.com/t/cannot-export-udt-tags-v7-6-6/8307/3 "2014-04-15T12:30:42Z")

</div>

OK thanks,  
but let me rant for a bit.  
  
I upgraded to V7.6.6 because of an issue with the Clgx driver in V7.6.4. That was fixed n V7.6.5, but as soon as V7.6.5 was released, immediately it was pulled from circulation because of an alarm journal issue.  
I love the product and the support is amazing, BUT it is frustrating when something that worked before gets broken on a new release.
