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.
Town of Queensbury, NY