Is there any way to restrict potential values from being populated on-the-fly using the floor filter functionality in Field Maps?
We are starting to map indoor assets and we have a floor-aware web map published that will be used to do so. Our field crews will be populating the room number as they collect new points since it doesn't sound possible to automatically calculate that via attribute rule (issues with stacked polygons).
However, we have over 100,000 rooms and would like to restrict the potential values our crews can populate by building and floor as the user changes the floor filter in Field Maps. Does anybody know of a way to do that or have a workaround idea? Thanks!
