Dear Smartsuite Team,

I ran into following Sitiations and came up with an idea that could present a solution

For example: if you had a solution that acts as an adress-book with each entry representing a person. You might want to link those persons to a lot of other tables in different solutions. In doing so the table containing the persons is blown up exponentially with backlink-fields, that are not really needed (from the users point of view. I know they are necessary for the database to work).

But all of them have a table that takes care of tasks. It is not possible to create another table that links to all of those task-tables without creating a colmn for each one of those.

The Question:

Would it be possible to implement some kind of Data-Classes?

Following the examples above you could setup a Data class called "task" ( or "contact" following the first example)

by defining which data fields are required to qualify (due Date, assignement, etc.)

In the next step you can tell a table that all of its entries are of the class "task".

This would only be possible if the table meets the criteria and has at least the data fields required by the class.

Other tables can now have a field that links to classes in multiple solutions. (authorisation inherited by the solutions). Since the necessary data-fields for a class are defined. There would be no wildcards in lookup fields. The Name of the Solution the entry originates from could be passed as an aditional property for lokups or formulas.