In many cases, some columns of a lookup should adhere to a data type, for example:
Restricting the input for such a column to only valid values would greatly ease editing, and would open up editing those columns to a larger group of users.
I have considered this. See http://lukemurphey.net/issues/1551. The KV lookup editor does support some form of this in that it uses the types to indicate which editing widget to use (e.g. a checkbox for booleans).
That said, it doesn't support something richer such as defining a static list of possible values and it doesn't support CSV lookups.
I have also been considering adding the ability to define forms for lookups so that people could just use the form to insert entries into rows (see https://formbuilder.online/). That would likely be a phase two approach.
Feel free to make comments here or in http://lukemurphey.net/issues/1551 if you have more comments.
Good point, will poke Splunk with a separate feature request for an enum type in KV store collections.
When you create a KV store collection, you can assign data types to the fields, and they will be enforced. Not exactly your question, but related...
I have considered this. See http://lukemurphey.net/issues/1551. The KV lookup editor does support some form of this in that it uses the types to indicate which editing widget to use (e.g. a checkbox for booleans).
That said, it doesn't support something richer such as defining a static list of possible values and it doesn't support CSV lookups.
I have also been considering adding the ability to define forms for lookups so that people could just use the form to insert entries into rows (see https://formbuilder.online/). That would likely be a phase two approach.
Feel free to make comments here or in http://lukemurphey.net/issues/1551 if you have more comments.
Thanks, Luke!