User-Defined Enum Datatypes in Tulip Tables

[d.gonzales]

Hi all,

Currently, the Input Validation feature helps validate user data inputs at an app level. This has been very helpful and really streamline Tulip Citizen Development.

However, I would propose one more level of data validation. I would like to suggest a feature for users to be able to create enumerated data types on Tulip Tables.

while working with different levels of Tulip Citizen Developers asynchronously there is always a risk some developers may not follow the same table value structure.
For instance, we may want to ensure the only values possible for a work order status are “CREATED”, “RELEASED”, “CLOSED”, or “HOLD” and nothing more.

For this, I would like to suggest the idea of Enum Datatypes, similar to how Google Appsheet tables operate.

Example

[pgabrys]

This would be so incredibly helpful! Keeping the validation rules at the table level would eliminate the painful need to maintain the correct logic in all of the apps that write to the same table. It would really help in keeping the integrity of a data model stored in Tulip Tables.