An update to this. We moved to a higher patch level (Jakarta Patch 3), and things look more normal from the update set point of view. Now when I add a new column to Configuration Item [cmdb_ci], instead of seeing literally hundreds of updates added to my update set, i.e. one per every child class, I know see just the usual 3 updates for a new field: Dictionary, Field Label, Field Layout.
Behind the scenes I believe it's still being added everywhere, but the evidence is hidden from us
* TOP TIP *
Something which doesn't work at all well under TPP, even under Jakarta Patch 3, is adding a new field up high in the CMDB hierarchy, e.g. at Configuration Item level, then placing the new field on the form at various lower level clases, e.g. Server. It will work fine on Dev, but when you transfer the update set, you will see lots of red errors at the Preview stage. I would suggest doing this in multiple update sets. Add the field up high to CMDB. Move update set. Then add to lower level classes. Move update set.
On the other hand, if you are faced with the screen full of preview errors something like this:
They are all about missing fields, i.e. the system cannot place the new field on the lower level tables because the field does not yet exist on the table. You can accept all remote updates. It doesn't feel good, but I've done it a few times and the end result works. This was also what a Hi support engineer advised, after all other avenues failed. Just can't guarantee it would work every time.
