Autocomplete with one column

EvanDarpini

I currently have a csv file attached to my survey that lists plant species. I have a select_one plant name with the calculation pulldata('USDA Plant Database common name', 'ScientificName', 'ScientificName', 'enter_name1') and appearance autocomplete

The Csv file contains an enormous amount of choices all from one column called scientific name. I want to avoid puttin each choice in the choices sheet of the Survey file. Is there anyway i can make the choices pulldata from the csv or do the choices have to be input into the survey?

All i want is as field tech input the name suggestions drop down for what they are looking for 

ex: Royal

autopopulates: Royal Palm, Royal Poinciena, ect.

dougbrowning

My species list is over 60,000 to get all 11 states.  Here is how I do it.

First I break it out by state since different plants may be woody or not for example and to only show plants that would be in that state.  These all go in the media folder.

In the form I have a State list that they can pick or it passes in from Field Maps.  I then do a calc field to create the csv name I need.
${SpeciesState} + 'LenticSpeciesList'

Then I use the newer search appearance to grab the correct state list like this in the appearance column.  This loads after they pick a state only so the form loads fast.

autocomplete search(${SpeciesListName}, "matches", "Plants", "Y")

In my CSV I have the code as the name and in the label I have Code   Scientific Name   Common Name (4 spaces in-between each).  This way a crew can search on anything they know and find the right plant.  Code, Scientific, Common are all interchangeable.  Each user knows plants differently so this is great.  

Also what is cool if they say know its a willow they can just type willow and it shows them the options for that state.

Each state is close to 12,000 in the list and it is lighting fast.

I can also do things like only show them the woody plants

autocomplete search(${SpeciesListName}, 'matches', 'Type', 'Woody')

We only store the code in the data then our backend SDE has a lookup table with all the above if anyone needs it.  This way we can adjust Indicators and all that by state with varying growth habits, etc.

I have species, LPI, Gap, forms and all of that if you want them DM me for the process to share.

Hope that helps it has been a big win for us.  In another project we have smaller lists so I have a image for each choice even.