I just verified this behavior, I think it doesn't make much sense just to skip to the next one if there is only one value. Even its bit confusing.
Tagging Michael in case he has some details on this -
Hi Guys - yes we have seen this - and I have reported it - however this is default, engine behavior.
Thanks for tagging me Digvijay!
The workaround I've seen is to add a null value to each field to make sure you always have "more than one". Not ldea, but works for now.
I will follow up with plu - to see what he thinks.
Thanks for the question and your community involvement.
When applicable please mark the appropriate replies as CORRECT. This will help community members and Qlik Employees know which discussions have already been addressed and have a possible known solution. Please mark threads as HELPFUL if the provided solution is helpful to the problem, but does not necessarily solve the indicated problem. You can mark multiple threads as HELPFUL if you feel additional info is useful to others.