I've the same problem
Now I set up transactions groups for eacht instance of an UDT manually.
However this will log it to the database, it is not the way it is supposed to be.
I wasn't able to get a whole UDT in a transaction group (i did it manually for each instance now)
this isn't actual historic data, it will not be shown at a tree browse when having historical tags enabled.
my situation:
i have 2 tags:
Tag A
Tag B
Both are historic tags and both are only have to log when Tag A changes.
This is what "DB pens" are for -- data in wide tables from transaction groups or external sources. Since there's no standardized format for such data, you have to implement your own tag drop event handlers that understand your DB structure.