This trips up a lot of people when they drag on a UDT from the OPC browser and create a new UDT type from it, copy json to notepad, find/replace the parts in the OPCItemPath (or others) prop values with "parameters" inside {...}
, then paste back in / import over the original UDT Type, and they wonder why their UDT instance tags don't pull in values. The issue is that the newly (faux) "parameterised" values are actually not converted to bindings when they're pasted/imported back into Ignition, so they're just statically set to literally that string value.
Unless there are conditions that would prevent it, my request is that UDT Type tag json be auto-converted to bindings if the values have braces in them.
E.g. Convert:
"opcItemPath": "ns\u003d1;s\u003d[{PLCName}]{DeviceName}.Speed"
to
"opcItemPath": {
"bindType": "parameter",
"binding": "ns\u003d1;s\u003d[{PLCName}]{DeviceName}.Speed"
}
Idea to vote: Auto-convert relevant UDT Type tag prop values with {..} in them to bindings | Voters | Inductive Automation