Enumerated properties (unique) - Select from a prefixed set of values

Feature requests
,
1

Use case or problem

Would like enumeration type properties in the new properties feature.

Proposed solution

Add two properties types:

  • enum value: Allows a single value from a limited set.
  • enum list: Allows multiple values from a limited set.
34 Likes
2

This gets a big +1 for me. Enum values add structure and enforce consistency without having to think about it, so I’d love to see them added to properties.

6 Likes
3

Does anyone have a workaround for the time being?

2 Likes
4

I would recommend changing the names of these properties types.

I really like what Notion calls these: Select and Multi-Select. Most non-programmers have never heard of enum. Plus, enum list would be confused with the existing List Property Type.

4 Likes
5

Yes, big +1 for this. This feature would be great to avoid honest mistakes

6

To me, several of the new Properties types are enumerated by definition.

What is missing is standard approaches in UI functionality around using them in an object oriented manner. This is why so many of us are having to go back and cleanup the use of fields and tags in the carnage we’ve left behind in our vaults.

Having properties in a now standardized yaml format will make for powerful stuff in the near future and I’d bet the creative and clever folks in this crowd are burning midnight oil on this as we speak.

8

+1 for this.

What we have now:

  • One field type, Text
  • Field behaves like a classic combo box - existing values can be selected but you can freely add a new one. Sometimes this results in mistyping. In my case, I think it more commonly results in failing to input a link, [[Blah]] vs. Blah.

What would be better:

  • Field type Text is free text and doesn’t autocomplete.
  • Field type Single Select where we explicitly maintain the list of valid values.

The bit I’m not too clear on is where those valid values would live in the notes.

Editing just to add: Similar deal with List and Multiple Select.

Also to add that I’m using Airtable naming here. I think Notion’s naming would be fine too. If it were me, I would have named things as Text, Multi Text, Select, Multi Select, Number, Multi Number, …

2 Likes
9

After Bases implementation, this problem seems even more relevant. I’ve accidently doubled this request - there’s my view on why I find this feature important:

Use case or problem

With the current possibilities of easily managing and summarizing property values from a lot of notes, in some cases it’s reasonable to have a property that has a custom value for every one. For example, I have a “wins” list property in every daily note and I want to glance over it through a base, showing the whole month of daily notes. Suggesting a value based on all previous values of this property wastes CPU power and just gets in the way.

Different case: in my daily notes I have a “habits&routines” list property, which I want to fill in with habits that I want to make stronger. Choosing it from a customizable list would be much easier, as now Obsidian suggests every habit I’ve placed here - even those, that are rooted and I don’t want to track anymore.

Proposed solution

Make a per property option to disable suggestions or prepare a list of possible values.

Current workaround (optional)

Typing fast and ignoring suggestions is good enough for the first case. The second one is rougher - I’ve prepared a base to list only “weak” and not present in current note’s “habits&routines” property list already to see which values are “left to consider”.

2 Likes