Hi folks,
We have a UDT defined in ignition with certain fields. I'm writing an Ignition SDK module that will work with these UDTs. The goal is to be able to read the full UDT into the module, make some changes to it if need be, then write the updated values back to ignition. We'll have a bunch of these UDTs with an ObjectID as the identifier in the path.
My hope was to import the UDT as a java class where fields map to the udt's values. Then I can work with it natively in Java and then "write" the instance back (similar to a database ORM).
Is this a sensible pattern for Ignition UDTs, or am I missing a different best practice? Is there any build in automation to generate a java class from a UDT, or would I need to do it manually?
And if I'm doing it manually are there any examples? I found this Read and Write Tags example, but I can't find some of the imported fields in the documentation so I wonder if the example is for an older version of Ignition? We're using 8.1
