Probably going to need some help from the IA guys here, but I want to create a backup of the config.idb to include in one of my tool scripts that bulk edits tags and their config. Before writing the bulk config, I want to backup the config.idb first in case someone stuffs up (read: someone stuffed up and added a whole bunch of custom props to lots and lots of UdtInstance tags instead of writing to the Udt instances' Parameters - they missed the "/Parameters" in the tagpath)
The config.idb gets auto backed up at various points, so I'm sure there's a backup function exposed via the gateway context somewhere...
Based on the ignition Java docs here you could use that class to backup the IDB file using the backupDatabase() function. Never used it before tho so take this with a grain of salt
I’d argue custom props (or preferably a single “document” tag - until nested items in a “document” custom prop can be accessed/written individually the same way via prop['nested']['item_or_index']) is the correct place for any “metadata” that isn’t explicitly used for indirection/dynamic purposes in UDT tag parameters (e.g. OPC item paths). I hate seeing “whole bunch” of static Parameters that aren’t actually referenced anywhere in the UDT itself.
I don't recall now what happened, but most of my UDT parameters are used in tags, except for a description param
1 Like