Daniel,

I assume by "special items" you mean an item from the Special List? The reason why their values are not put into the Variable bound to the combo box is twofold: for one, the combobox Variable is often an identifier, and it makes sense not to allow non-existing identifiers; and two, you can have special items with a Value that's of a different datatype, that you can use for easy checking.

That said, the platform provides a Special Variable that can be used to assign the selected Special List's item's Value. I don't see why this should involve a "hacky work-around".

I ended up switching the data-type to text, and in the preperation concat the two lists (special list + aggregate data), that way I can maintain the logic with one variable instead of checking against two (and also have dynamic "special list" values instead of hardcodes). I get why the platform didn't want to bind an unknown-type to a strongly typed variable; I just found one dropdown binding to two variables a bit non-intuitive. Thanks for the reply!