# \[Bug-11682\]Vision Client Tag Export (json or xml) outputs a blank file

**URL:** <https://forum.inductiveautomation.com/t/bug-11682-vision-client-tag-export-json-or-xml-outputs-a-blank-file/22191>\
**Category:** Ignition Early Access\
**Created:** [January 29, 2019, 3:29pm UTC](https://forum.inductiveautomation.com/t/bug-11682-vision-client-tag-export-json-or-xml-outputs-a-blank-file/22191 "2019-01-29T15:29:33Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![bfeas](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/bfeas/32/3783_2.png) [@bfeas](https://forum.inductiveautomation.com/u/bfeas)\
**Post date:** [January 29, 2019, 3:29pm UTC](https://forum.inductiveautomation.com/t/bug-11682-vision-client-tag-export-json-or-xml-outputs-a-blank-file/22191/1 "2019-01-29T15:29:33Z")

</div>

Vision Client Tag Export (both json and xml) outputs a blank file.  
Using standard right click and select export on tag to be exported.  
Is there a fix for this? I’m not seeing any other posts for this issue, maybe I’m using the wrong right click button…

---

<div class="post-metadata">

**Author:** ![ggross](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/ggross/32/12668_2.png) [@ggross](https://forum.inductiveautomation.com/u/ggross)\
**Post date:** [January 29, 2019, 5:20pm UTC](https://forum.inductiveautomation.com/t/bug-11682-vision-client-tag-export-json-or-xml-outputs-a-blank-file/22191/2 "2019-01-29T17:20:27Z")

</div>

This is an issue we are aware of. Importing and Exporting Vision Client tags do not currently work.

Garth

---

<div class="post-metadata">

**Author:** ![awalker](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/awalker/32/6874_2.png) [@awalker](https://forum.inductiveautomation.com/u/awalker)\
**Post date:** [February 4, 2019, 4:41pm UTC](https://forum.inductiveautomation.com/t/bug-11682-vision-client-tag-export-json-or-xml-outputs-a-blank-file/22191/3 "2019-02-04T16:41:43Z")

</div>

This issue was fixed in the build that was uploaded today (2/4).  
Please let us know if you continue to see this behavior after upgrading.