Are there plans to enable us to do unique indexing on Multi Selects?
We have a use case for it currently.
What do you mean by Unique indexing on Multi Selects? Could you provide an example perhaps?
I think I get it now - does the following example make sense?
You have a menu table with a Multiple Select List Lookup field on it that has options Hamburger, Fries and Coke. You want the menu table to allow all combinations of those selections for that field, but not to repeat any combination so that the menu doesn’t contain redundant duplicates.
This isn’t possible using a unique index on that multiple select list lookup field right now in Nextworld, as Nextworld errors with Error - A unique index can not be created for fields of type Multiple Select. Remove field xxx.
@ian.p is right about the current state of the system.
As for your question:
No, not that I know of. Unique indexing on Multi Selects is interesting because today in the system, [Fries, Coke] is distinct from [Coke, Fries]. In other words, ordering matters. For some use cases, this is preferred. In others, it is not. We have thus far shied away from the complexity of supporting both use cases, which would be a prerequisite to unique index support.
That said, it may still be possible. If you are a Nextworld customer or partner, you can work with your system administrator to submit an official enhancement request with customer support. Include a link to this post in the support ticket. If you’re not a Nextworld customer, keep an eye on release notes. We’re always making improvements.
1 Like