Handling Multiple Hydrant Parts List in a Survey

Question

I'm currently working on a survey where users inspect hydrants.  One section of the survey needs to be presented as a parts list where the user will choose which parts are needed for the hydrant.  We have various models and specific parts for each model.  I'm trying to figure out the best way to handle this given that there may be over 170 different parts over the various lists.  I don't think it's a great practice to add 170+ fields to a table and I'm not sure if multiple related tables (each table would be a parts list for a specific model) in my feature service would be the way to go.

Any help or suggestions on how to approach this would be greatly appreciated.

Thanks,

George Hilton

Town of Queensbury, NY

dougbrowning · Answer

itemsets for for the list not for the data storage.  Just create a repeat and look at the schema you will see it.

GeorgeHilton__GISP · Answer

James,

External selects referenced in the link you sent might work for us.  My next question is: once an overall selection of needed parts is made during an inspection and is saved to itemsets.csv, is a separate itemsets.csv file created for each inspection or will it be grouped in one master csv file?  If they are all placed in the same csv file, how would I be able to extract the parts that were selected in each individual survey over time?

Hope this makes sense.

Thanks for all of your help!

claykitchens_fd_0-1718985219085.png

claykitchens_fd_1-1718985248415.png

dougbrowning · Answer

I am confused as to why you think you need 150 fields.  Just use a repeat as James and I say.  No need for 150 tables either.

I do this a lot here is an example.  This also gives and list and checks for dups.  I can add 1 or 100 species makes no diff.

Hope that makes more sense.