I'm looking for a solution that will allow us to efficiently collect indoor feature data. Our data is hosted in an Enterprise (11.1) gdb, with specific user permissions controlled with the use of Feature Layer Views, with the primary interaction being through WAB applications. Feature editing works great in WAB, but the need for field collection is increasing as we plan additional implementations, and I'd love to be able to use the mobile application for this.
My problem is that I'm able to get the floor filter to show up if I publish a web map directly from Pro, and then pull that web map into the Field Maps application, but any web map created in the enterprise portal, configured appropriately with floor aware layers etc., fails to show the floor filter in Field Maps when loaded. I've tested this with and without referencing a Feature Layer View of the data in the web map to determine if it's a limitation of using Feature Layer Views. It seems to be that the only web maps that have functional floor filtering capabilities in the Field Maps app are the ones directly published by pro. This is a problem because it doesn't allow us to utilize the controls offered through feature layer views. As soon as layers are removed/added in the directly published web map, the floor filter ceases to appear in the Field Maps app. I'm new to the Field Maps app, so I'm hoping that I'm missing something. If not, I simply cannot use field maps.
ESRI support simply stated that I should publish to a web map from Pro to have this functionality. As stated above, this means that we cannot use Feature Layer Views. I cannot be the only person needing to utilize feature layer views, swap and customize web map layers and still be able to use the Field Maps app. 🤔
Any help would be appreciated.
-J
Solved! Go to Solution.
This is a follow up reply to help others who may still be struggling with this.
Until today, this process had still not worked consistently, despite following the documentation in (what I assumed was) exactly the same workflow. While creating a new map today, I spent some more time struggling with it, going through the data, configurations etc. trying to repeat my success. I eventually figured out that in order for this to work properly, you must have floor filtering turned off entirely in the Map Properties of the web map before pulling the map into ArcGIS Pro to configure the floor aware layers. If "Enable floor filtering" is toggled on in the map properties (on the portal), the ESRI documented process will fail. This doesn't seem intuitive because I would expect that "Save Web Map" in Pro should completely overwrite the web map's configuration data, but it doesn't seem to behave that way (at least in Enterprise 11.3 that we're on).
My previous workflow had been to create and configure my web maps in the portal, so the requirement to pull them into Pro (to get the floor filtering to work in the Field Maps mobile app) was an afterthought. But that created a problem because my workflow in the portal usually included configuring the indoors layer properties, unknowingly sabotaging the subsequent configuration in ArcGIS Pro.
TLDR: If you create your floor aware web maps in the portal, and you need them to work in the Field Maps mobile app, DO NOT configure floor filtering in the map properties. Leave it toggled off and save. Then pull the map into ArcGIS Pro via the Catalog Pane / Portal tab, configure the indoor layer properties, and "Save Web Map" to overwrite the web map.
I find this a bit frustrating because the requirement to save the indoors configuration in ArcGIS Pro is only required for Field Maps mobile to function. Indoor layers configured in the portal work fine everywhere else. This extra step, which is so easily derailed by having this pre-configured in the portal, is clumsy and seems unnecessary.
*If you already do all of you web map configuration in Pro, then you may not ever encounter this problem.
-Jeremy
This worked in 10.9, I have not tried it in 11.x. The license for Indoors resides in ArcGIS Pro. Open your online map from your Portal location in Pro. Go to the map properties and set the FloorAware fields. The Floor picker should show up. Save the map.
This was one of the first things that I tried to do. I naturally assumed that since all of the necessary floor-aware fields were there, it should simply require me to configure the map properly. I have tried configuring these floor-aware fields both in Pro and Enterprise (new) Map Viewer. The map layers are configured identically to how Pro does them during a direct publish. Floor filtering works properly in the (new) Map Viewer itself, just not in Field Maps. We have an active Indoors license, and use these floor aware maps regularly...just not with Field Maps because floor filtering does not work.
-J
I looked at Feild maps requirements and I think the issue maybe the Feature Layer Views. Editable data in field maps states it must be a Hosted Feature Layer with editing and sync enabled. You might check with Tech Support on this. I know my Flooraware web maps using published from ArcGIS Pro using Hosted Feature Layers are working fine in Field Maps with the Floor picker widget.
It turns out that I was missing a step in the documentation that details your above advice, and following some further testing this afternoon, I now have floor filtering working in Field Maps, even while using Feature Layer Views...as I hoped was possible. Thank you for your willingness to help. 🙂
-J
This is a follow up reply to help others who may still be struggling with this.
Until today, this process had still not worked consistently, despite following the documentation in (what I assumed was) exactly the same workflow. While creating a new map today, I spent some more time struggling with it, going through the data, configurations etc. trying to repeat my success. I eventually figured out that in order for this to work properly, you must have floor filtering turned off entirely in the Map Properties of the web map before pulling the map into ArcGIS Pro to configure the floor aware layers. If "Enable floor filtering" is toggled on in the map properties (on the portal), the ESRI documented process will fail. This doesn't seem intuitive because I would expect that "Save Web Map" in Pro should completely overwrite the web map's configuration data, but it doesn't seem to behave that way (at least in Enterprise 11.3 that we're on).
My previous workflow had been to create and configure my web maps in the portal, so the requirement to pull them into Pro (to get the floor filtering to work in the Field Maps mobile app) was an afterthought. But that created a problem because my workflow in the portal usually included configuring the indoors layer properties, unknowingly sabotaging the subsequent configuration in ArcGIS Pro.
TLDR: If you create your floor aware web maps in the portal, and you need them to work in the Field Maps mobile app, DO NOT configure floor filtering in the map properties. Leave it toggled off and save. Then pull the map into ArcGIS Pro via the Catalog Pane / Portal tab, configure the indoor layer properties, and "Save Web Map" to overwrite the web map.
I find this a bit frustrating because the requirement to save the indoors configuration in ArcGIS Pro is only required for Field Maps mobile to function. Indoor layers configured in the portal work fine everywhere else. This extra step, which is so easily derailed by having this pre-configured in the portal, is clumsy and seems unnecessary.
*If you already do all of you web map configuration in Pro, then you may not ever encounter this problem.
-Jeremy