If you want to build an application in traditional layers, there are things you don’t want to show as a form, some things only as lookup, for filters, etc.
It would be great to be able to define that something is not for user input, and hide it from the subject list.
+23Hi Daan,
We currently don't have a formal way of defining the reason of existence for a table.
Would the Table description be a fitting alternative to use? The Table description can be filtered on, so you could exclude tables using a certain keyword in the description. Alternatively, you can make use of Table tags and write Dynamic model code that uses this information to enrich the model.
+23+23Hi
I would like to have your take on it.
Would the Table description be a fitting alternative to use? The Table description can be filtered on, so you could exclude tables using a certain keyword in the description. Alternatively, you can make use of Table tags and write Dynamic model code that uses this information to enrich the model.
+23Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.
