I am not sure if this is the same issue we are seeing. It started with the new way lists are stored now. It is sorting by the filter instead of the order of the list now.
Does this sound the same? We have not found a way around it yet.
So we ran into an issue with Survy123 3.12.277. When filtering an external_choices list we are getting the results back in alphabetical order based on the filter. And further, capitalization counts – so NonWoody is not the same as Nonwoody. This is not the case for Survey123 Connect or we think older versions of Survey123.
Type (line 96):
select_one_external PlantsList
Choice_filter (line 96):
Type=${herb} or Type=${none} or Type =${unknown}
We set (lines 52…)
${woody} to “Woody”
${herb} to “NonWoody”
${none} to “None”
${unknown} to “Unknown”
It does not matter what order the items are in the choice_filter, we get the results back in alphabetical order by filter.
NonWoody
None
Unknown
Woody
What we want is for None to be first, since it is most often picked. Is there a way we can accomplish that? If we change “NonWoody” to “Nonwoody” then it would work. But that messes up all our workflows downstream. Plus, we don’t want to name filters just based on making sure they alphabetize correctly.
thanks