Restricting data entry values

[Peter Norris]

Is there a way of restricting what values are entered into a database column?

For instance, in the webinar the example database had "Autumn", "Spring", "Summer" and "Winter" in a column - how do I enforce that someone entering a value in this "Season" column can only enter one of those four values?

Or am I missing the point?

[Philipp Sendek]

Hi @Peter Norris ,

you can do this by creating a new database (e.g. called "Season") that includes those values and then create a field of type "Entry Link" in your Webinar database.

In this field you select your "Season" database and whether only one or multiple options can be selected.

That way your users would only be able to select either of those values in the specific field.

Greetings
Philipp

[Jason Hills]

+1

I do this as well. Use one database to serve as entries in another, while adding additional information.

[Peter Norris]

Perfect! Thanks Philipp!

[Jason Hills]

The most obvious solution is to use a Tag column and disallow tag creation.

I use Confluence DBs to create ITIL service catalogs (what services do you offer that you must maintain), and I use mostly tags. Doc type, data source, pipeline, presentation layer, unit owner, owner, etc. are all tags.