We recently launched a data collection and asset management project, and are seeing that assets seem to not draw on some user's maps where they are working, while still showing up on others. For example, multiple users in the field have contacted us saying that they no longer can see a road line feature, or other point/line features along said road that were visible the day before, while other users can still see them.
This is proving to be a serious issue, as the field users are ending up collecting new data where they do not see a loaded feature, instead of updating the existing feature (since they cannot see it to update it) and creating duplicate data.
Update: had a field team that has two iPads, one working offline, one online, and are seeing their features show up in the offline map, but not in the online map.
Solved! Go to Solution.
This was logged as a bug:
Opening a web map and start to panning and zoom in/out, after more than 15 minutes some features may not show up in the map in ArcGIS Field Maps mobile app.
Status: Under Consideration
Reload the map.
Hi @jtmouw_NCDOT ,
Are you seeing issues across multiple feature services/maps? When did you start to notice this behavior? Perhaps you can give an overview of your data setup. Some of the things I would be curious about are:
- Are you using Feature Layer Views?
- Do you have filters set up (or View definitions if "yes" above)
- Rough estimate of the amount of features in the problematic layers
We are seeing the issue across multiple feature services/maps yes, there are 14 different feature services that we have for this particular project (identical structure, 1 hosted service for each division). We noticed around a month ago (though this was when really started migrating one of our larger projects to field maps, unsure if it was happening before on a smaller scale that we did not notice, and only when having many more users in Field Maps did it become apparent).
-We have hosted feature layers, with views set up to control access/capabilities for field users.
-We do not have any filters set up
-Layers in our hosted services range from around 10-30k features.
Just recently we noticed behavior in a feature service (view) for another unrelated project that only has ~9.5k features. In this case the user had the feature show up again once he re-loaded the map.
This issue was solved by updating the maxRecordCount, but since those have been capped recently, we are having the problem again. Per post below, changing the refresh interval does not seem to solve anything.
Has there been a resolution to this? If it's what it seems like you are describing, we might be having the same issue. Intermittently, points that are there are NOT showing up on the map...and will appear ONLY after the related parent feature (a polygon in our case) is selected.
There is a point right here that is not showing:
Then, only after we select it's parent polygon, and select the related point layer...it appears.
Similarly...this is causing major issues due to duplication of work in areas where crews are dropping points when there are already points there.
Any information on this would be greatly appreciated. Thanks!
No solution yet, and we continue to see it periodically. It seems like bumping up the maxRecordCount of the feature helps, though anecdotally several of our crews are still experiencing the issue from time to time.
Interesting about the maxRecordCount...we are definitely over. I will try that. Also, I put a refresh interval of 30 seconds on that layer and you can see points appear out of nowhere when zoomed in to an area with the known issue. We JUST did that so more testing is necessary, but seemed to help right off the bat. Thanks for the response, I have also submitted a case with Esri (03274735) so I'll keep this chat updated if we solve anything.
Have you found that the refresh interval solved your issue? It seems that ESRI recently cranked down the allowable max record counts, and I have started to have the issue again. Wondering if just changing the refresh interval will make this a non-issue since I no longer can implement the maxRecordCount workaround.
No, users are still having this issue. No solution has been found and our assumption is that maxRecordCount is not an option as we have so much data, it would eat up too much processing.
I have recently set up two projects accessing different data in field maps and both are having this issue. I see this post is a bit older, but would be interested if anyone has found solutions since this was last discussed.