# Using JSON to import tags- there is an issue with OPC item path **URL:** \ **Category:** Ignition\ **Created:** [March 23, 2026, 2:56am UTC](https://forum.inductiveautomation.com/t/using-json-to-import-tags-there-is-an-issue-with-opc-item-path/114612 "2026-03-23T02:56:12Z")\ **Posts on this page:** 6\ **Page:** 1
**Author:** ![mehdi.sajjadi](https://avatars.discourse-cdn.com/v4/letter/m/ed655f/32.png) [@mehdi.sajjadi](https://forum.inductiveautomation.com/u/mehdi.sajjadi)\ **Post date:** [March 23, 2026, 2:56am UTC](https://forum.inductiveautomation.com/t/using-json-to-import-tags-there-is-an-issue-with-opc-item-path/114612/1 "2026-03-23T02:56:12Z")
Hi everyone, I’m trying to import tags into Ignition using a JSON file. These tags are structured as UDTs, and some of the IEDs use IEC 61850. As an example, here is one of the tags used inside a UDT: ![image](https://us1.discourse-cdn.com/inductiveautomation/original/3X/4/6/46c259d73ce4a1a13f46129133688ed8fe9c6ab5.png) After importing the JSON, all of the tag parameters look correct **except for the “OPC Item Path”** , which shows the following error: ![image](https://us1.discourse-cdn.com/inductiveautomation/original/3X/3/4/3444c8f17d664365f2bab2f56d761c5230d654ac.png) Here’s the strange part: ![image](https://us1.discourse-cdn.com/inductiveautomation/original/3X/6/0/607b7b4986291bf06d825a4332126a184e212dc0.png) If I click at the end of the OPC Item Path field and simply press **Space** , the error disappears and the tag starts working normally. Has anyone seen this bizarre behavior before? Why would the OPC Item Path be invalid until I manually add a space at the end, even though the JSON value is identical? Thanks ---
**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:** [March 23, 2026, 3:25am UTC](https://forum.inductiveautomation.com/t/using-json-to-import-tags-there-is-an-issue-with-opc-item-path/114612/2 "2026-03-23T03:25:50Z")
Your OPC Item Path has an embedded parameter. In imports, you cannot just stick those into the string value of the tag property--there must be a nested JSON binding object. Interpreting the string value to create the binding is a feature of the designer tag editor, not the import machinery. Export and examine the JSON of a UDT member tag that has a working binding to see the structure your import needs. ---
**Author:** ![mehdi.sajjadi](https://avatars.discourse-cdn.com/v4/letter/m/ed655f/32.png) [@mehdi.sajjadi](https://forum.inductiveautomation.com/u/mehdi.sajjadi)\ **Post date:** [March 23, 2026, 10:46am UTC](https://forum.inductiveautomation.com/t/using-json-to-import-tags-there-is-an-issue-with-opc-item-path/114612/3 "2026-03-23T10:46:20Z")
Thanks @pturmel I have added the **“ns=1;s=[ACB]{IED}LD0/MMXU1.TotW.mag.f”** manually, and it is working with no issue, when I use exactly the same address using importing the JSON file, the error comes up. > **ACB** : is driver name > **IED:** the parameters used as STRING. **Error("CreateMonitoredItems failed: Bad\_NodeIdUnknown: The node id refers to a node that does not exist in the server address space.")** The confusing part is that addresses are identical but one is working (Manual insert) , JSON is not working. Shall I consider any thing that seems to be missed? Thanks ---
**Author:** ![David\_Stone](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/david_stone/32/79749_2.png) [@David\_Stone](https://forum.inductiveautomation.com/u/David_Stone)\ **Post date:** [March 23, 2026, 10:54am UTC](https://forum.inductiveautomation.com/t/using-json-to-import-tags-there-is-an-issue-with-opc-item-path/114612/4 "2026-03-23T10:54:31Z")
Stop posting AI slop and start reading the post. You were told exactly why this doesn't work in the previous post. ---
**Author:** ![Nol](https://avatars.discourse-cdn.com/v4/letter/n/8e8cbc/32.png) [@Nol](https://forum.inductiveautomation.com/u/Nol)\ **Post date:** [March 23, 2026, 2:34pm UTC](https://forum.inductiveautomation.com/t/using-json-to-import-tags-there-is-an-issue-with-opc-item-path/114612/5 "2026-03-23T14:34:23Z")
Phil gave you the answer, you're not building your json correctly. You can find this if you import your tag, do the space trick to fix it, re-export it and then edit it in a text editor and look for the difference. You'll find you're missing bindType line in your original ---
**Author:** ![mehdi.sajjadi](https://avatars.discourse-cdn.com/v4/letter/m/ed655f/32.png) [@mehdi.sajjadi](https://forum.inductiveautomation.com/u/mehdi.sajjadi)\ **Post date:** [March 25, 2026, 8:44am UTC](https://forum.inductiveautomation.com/t/using-json-to-import-tags-there-is-an-issue-with-opc-item-path/114612/6 "2026-03-25T08:44:37Z")
Thanks I have noted that OpcItemPath while transferring, change its form to STRING, while It must a Binding expression. It is fixed.