Hey @Mark - I put together an app to illustrate the challenges, redundancies, and extra processing that can be eliminated by having an array column for the choice component.
The app is a simple list of products in 3 different sizes: https://arraycolumn.glideapp.io/
Two scenarios. The first speaks to the current state of affairs. The second borrows from a workaround introduced by @Jeff_Hager and @ThinhDinh. It may be suitable for a vendor with a limited product catalog but doesn’t scale.
Time/effort spent working around this simple limitation is rather high and it has cascading effects. If there’s a way to achieve that workaround within the data editor, I’d like to know. Otherwise, can you suggest something more efficient if an array column for choice is not a feature Glide would consider valuable?