# Importing Disorganized Tags/Direct Tag Import

**URL:** <https://forum.inductiveautomation.com/t/importing-disorganized-tags-direct-tag-import/92005>\
**Category:** Ignition\
**Tags:** vision\
**Created:** [June 18, 2024, 11:17am UTC](https://forum.inductiveautomation.com/t/importing-disorganized-tags-direct-tag-import/92005 "2024-06-18T11:17:01Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Caleb\_Iwen](https://avatars.discourse-cdn.com/v4/letter/c/82dd89/32.png) [@Caleb\_Iwen](https://forum.inductiveautomation.com/u/Caleb_Iwen)\
**Post date:** [June 18, 2024, 11:17am UTC](https://forum.inductiveautomation.com/t/importing-disorganized-tags-direct-tag-import/92005/1 "2024-06-18T11:17:01Z")

</div>

Is there any way to import tags in a more specific way than just a .csv/.json etc? I need to add a bunch of individual tags from a UDT inside the PLC and the individual tag names have absolutely no commonality or structure besides their hierarchy, which doesn't get translated to an export file. Is there any way to more directly access the tags from PLC code, specifically Logix designer?

---

<div class="post-metadata">

**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:** [June 18, 2024, 11:51am UTC](https://forum.inductiveautomation.com/t/importing-disorganized-tags-direct-tag-import/92005/2 "2024-06-18T11:51:13Z")

</div>

Have you tried my alternate driver's JSON files? (Generated UDTs and tags from Logix browse information.)

If you avoid the "Compact" forms, the rest should be supported by the IA driver at runtime.

> [@Automation Professionals' EtherNet/IP Communication Suite V2](https://forum.inductiveautomation.com/t/automation-professionals-ethernet-ip-communication-suite-v2/68190/35):
>
> Well, it wasn't simple. But it wasn't quite as bad as I feared. So, another beta: v2.0.2.230462332 Now I have to go back through all of my QC files before I'll call it an RC. I also switched the JSON exports to not use array tags by default. "Compact" versions of the JSON files are placed in the driver home folder if you'd like the original format.

With that, you can make just one Ignition tag (udt instance) for that entire UDT in the PLC.