Maybe it’s a misuse of logic and of the component, but here’s the scenario: suppose we have a table representing items that, among other things, have a size measure; Now suppose we have another entity representing a carrier that, among other things, has an ordered set of size (say, a package).
The canonical solution would be to create an entity of size measures, which would be used both by the items and by the carrier (which would therefore have a collection of sizes)…
Partly to experiment, partly to limit the proliferation of anagraphics and entities, partly because the real situation is slightly more complicated and not all measures can be chosen by any carrier, and finally also because the “package” must be shown in many screens as a string like “12.5 | 10 | 10 | 13.5” (and have no other consequences), I preferred to create a custom java type (as explained in the documentation Data Types :: Jmix Documentation #custom-type), which saves a string in the db and retrieves the data for me as an ordered collection of numbers. At this point I was looking for a nice component that would allow the user to quickly choose between different alternatives, with the possibility of repeating the choice (having to compose the package): I liked the tagpicker and its ease of use… but I’m afraid it not could work because looking at its source I think I saw that at a certain point the data pass internally through a linkedHashSet, which as such does not allow repeated entries…