nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Hosted CSV choice list for Field Maps

LayerItOn

Based on a question from @EvanR and my own experience- (related question here) it would be wonderful to have a single hosted list of choice options that can be used in Field Maps. For example, my team uses FM for drawing polygons or points at farm locations and record what trees are being planted and tree counts while using FM offline. I have over 20 combo boxes that use the same choice list. However, this list is often updated with additional species. It would be great to have one hosted list to update rather than dragging and dropping a .csv for each combo box for each form (form for point and form for polygon), ultimately requiring me to update over 40 combo boxes lists.

I know that survery123 can be used in field maps- but I have heard that others have experienced problems while using FM offline + survery123 with survery123 hosted choice lists. It would be great to cut out survey123 and have this feature natively in fieldmaps.

Find more posts tagged with

Web App

Mobile App

Smart forms

offline

Status: Open

Comments

AndrewPadilla

I support this Idea. My current workflow uses hosted csv (thousands of choices) in Survey123, which works great to update regularly. However, we are usingFieldMaps with the same list. The list changes hourly and needs to be updated as such. Changing the list manually is not practical for such large lists needing to change hourly.

LindsayRaabe_FPCWA

Agreed! A simpler way of managing domains in ArcGIS Online & Field Maps is desperately needed. We would love to be able to centrally host a list "somewhere" which we could update via python or other programming from something like AD groups, database queries, etc, which end up in Field Maps. Having to manually find the layer and then the field to update lists (many of which apply across layers) is super frustrating.