Is there a way to have a choice_filter not be a field in the survey's feature service? For our survey, a user has to select a site location - of which there are over 1000. Each site has a 'category', for example "park", "residence", "business", etc. To make it easier to find the right site in the select list, I'd like to create a cascading select with a choice_filter built on the Category. But we don't need (or want) to track the category so we don't want it as a field in the feature service.
Is there a way to have a 'Site Category' select (which will filter the sites in the 'Site' select) but not include that field (Site Category) in the feature service?
Thanks.
