Custom System Tables disappearing from Test

Hey Frances,

I'm not entirely sure if the Live to Test copy would have caused this, but generally, UP_POPULATE_REFTABLES_TABLE will clear out those LT and LTX tables, as it only looks for LTR tables. There is a newer procedure UP_POPULATE_REFERENCE_METADATA which does accept a table name as a parameter, and you could possibly use that to redefine the local tables for System Tables.

Hope that helps!

Hi Frances,

Did you find a fix for this?  I'm experiencing the same issue and oddly enough the table also disappeared from Security.

Thanks,

Janelle

I've resigned myself to the naming limitation, and use "LTR_X_" for naming cross tables that I want to appear in the Systems Tables.

Hi Janelle - 

Yes, confirming what Gawain and earlier Paul said - I realized the reason they had disappeared from the application was because they were not prefaced with LTR.  Similar to Gawain, we changed them to "LTRX_" to avoid this problem and now they are back.

(Of course if you rename tables make sure you know what-all depends on them!)

Best,

Frannie

UP_POPULATE_REFERENCE_METADATA is the current procedure that is used for this, and as you mention it takes a table name parameter. But if there is no parameter supplied, it will run on ALL system tables. When designing a local table, you need to expect that this procedure could be run at any time, and make sure your local tables conform to the naming conventions that it expects.

As Gawain mentions, it requires that local tables begin with LTR_ (including the underscore).

One other note about UP_POPULATE_REFERENCE_METADATA is that if you manually (or with a script) alter the column type or editability for a column in your local table, the procedure will wipe out those changes if they are not manually reapplied after running. (And since various install processes can run the procedure with no argument, this may be difficult to catch.)

It's not REALLY supposed to do that, since it archives your table configuration and is supposed to restore from that archive, and I've submitted a code change that would allow it to respect local table configuration but it hasn't been rolled into a production release yet.