I often DMT data into UD tables temporarily so I can use that data in BAQs or SQL Server updates. I noticed today that the version of DMT we have now is missing most of the UD tables:
We’ve had this happen in our environment as well. We solved it by creating a menu in the environment you’re trying to import to and assigning the relevant UD entry screen application to that menu. So in your case, that would be UD34.
Its quite annoying, to have to add a menu item, especially, if you are using a UD table as a child table.
Vote!
Updated link KIN-I-4637 since Epicor changed the URL of Aha.
While that might be a good work around, in my environment if I did that, someone would find it and be calling and asking what it is 
It wasn’t as easy, but I imported it into a different database on the same SQL server. Then used SQL to update the tables I wanted. Not ideal, but a work around where people aren’t interrupting me while it exists.
You can always just restrict it to yourself or security managers. So that no one can see it.
I’m a security manager already, but the ones that will be calling me are also security managers. They just don’t do DMT.
Maybe if I stuck them in an out of the way place like we did with embedded dashboards. (in a submenu called ‘Place to Store Embedded Dashboards’ )
That’s not as effective in the Kinetic menu, most people aren’t using the tree browser there, I’d have to come up with some naming convention for the entries that groups them together like ‘Do Not Use - UD34’, ‘Do Not Use - UD35’ etc. Then make the underlying screens that we don’t want anyone to use, read only.
