Title. I have a GWBK that contains UDT definitions and instances that restores fine in 8.1, but in 8.3 the instances are pulled in fine but the definitions aren't. (So the instances fail to load because they're instances of an unknown definition)
From your DM, you were using 20250410-1744/ as the build. Probably the first thing to try is to get you on a newer build. The latest is yesterday's:
Sure, anything unusual about the install process there?
(I.e. when upgrading builds, should I just run the installer)
I would just make sure to do a 'fresh' install, or at least wipe out any existing config/internal db/project state before installing the new build over. Within the 8.3 EA period, we're not making any attempts to ensure clean "upgrades".
1 Like
Yep, repros on newest version.
udts.json imports properly in tag_definitions in config, but there's no imported file in tag_type_definitions and the unary resource.json is empty.
Migration logs show no errors.
Can you please DM me the tags you are using? I would like to try and replicate this locally.
Thanks,
Garth
1 Like
Done 
We ended up working through this issue via DM. Ultimately, a duplicate _types_ folder was being flagged because of a row we didn't expect to exist in the TagConfig table. A bug has been created internally and this situation should be fixed in the near future.
Garth
Great, thanks!
For future reference, does creation of udts always create a _types_ folder in the tagconfig db or no? It seemed like it did to our exploration
No. The _types_ folder is something that we implement in memory and it automatically gets provisioned in memory when a Tag Provider is started. Ignition creates a record with the FOLDERID column containing a value of _types_ without the folder record existing.
Example of a UDT I created to test this. These are the only records that exist for this provider:
1 Like