Hello everyone,
I'm running into an issue with external selects in Connect. (Not an external choice list, I'm using select_one_external rather than select_one_from_file).
I'm using cascading selects to narrow down a long (~21k) list of plant IDs, where the choice_filter reduces the choice options based on plant species and location (Garden).
The issue is that the plant IDs are numbers and when they are brought into the survey from the itemsets.csv a decimal and zero are added to the end of every plant ID (6857 becomes 6857.0). This presents the plant IDs in the survey and stores the data in the results with the added .0. Since this information is stored as text in the data, it seems relatively simple to fix on the back end in excel by exporting as a csv or as an .xlsx file and converting back to number en masse, but it means that the plant IDs are displayed and stored incorrectly in the survey itself and in the analyze and data tabs on the website. Is there a way to fix this?
I've tried a few things (like bind::type and bind::esri::fieldType) but nothing has worked so far. I'm new to creating surveys so I'm hoping there's a solution that I haven't found or seen mentioned on the Community boards.
Thanks in advance!
Survey123 Connect version 3.16.110, Field app version 3.16.114
P.S. The plant IDs in this survey do unfortunately contain duplicates as certain plant ID tags were reused in some locations. I know there are limitations when using choice lists that contain duplicate names, but I'm not sure how they might impact this survey since the cascading select removes any duplicate options when filling out the survey. I'm mostly concerned with the potential for the choice to revert to the first duplicate in the list when opened from the inbox, drafts, sent, etc. Any more detailed info on this would be greatly appreciated.
