@Anonymous User
@JeffShaner
@ColinLawrence
@FMBAdmin
@Anonymous User
@RyanSellman
Hello All:
My organization is having performance issues with Field Maps:
Our field crews are editing a large work order dataset using Field Maps Version 22.3.0 and editing a hosted feature layer published from ArcServer ArcMap version 10.6.1 Advanced License. When the feature layer was originally published in 2016, it was blank. Now it has over 735 points and is 1.758 MB with 1,619.908 MB worth of attachments. The feature layer is configured with conditional visibilities, and prior to last week, I had the same feature layer in 3 different maps with filters established on each one (it is a work order layer and different users need to see different "status" fields).
They are sporadically reporting issues of "lost data" when trying to submit edits and new points. Where it takes very long to submit a new point or make edits to the layer with additional attachments. And in some cases, our field crews claim they submitted a point, and when reviewing the edits at the end of the day, they say points are missing.
I originally thought it was issues or concerns with different editing account types (which was not the case after much testing), then I opened a customer support ticket with ESRI because I thought we did not have the correct service definition settings - specifically with "maxrecordcount" (this theory was debunked because our feature count is below this threshold and they recommended working offline - which is not an option for us). I then called ESRI customer support a second time and they did not help any except for providing known bugs and enhancements.
My mindset then went to the editing issues coming from bad cell service in our city, however the issue is only occurring with Field Maps, and no other app on their devices runs poorly. I spoke with our I.T. department and they said we do not have unlimited, high speed data plan so this might have something to do with it.
I ended up noticing the size of the dataset the field crews were editing and optimized our data by disabling autosync, lowered the attachment size when collected in Field Maps from "LARGE" to "MEDIUM", I rebuilt the spatial indices, and I created hosted feature views instead of filters. This is working since the layer in question is a work order map, and I was able to narrow the points with a filter on the hosted feature view.
**The question I am proposing is this: we still have 5 other ASSET INVENTORY layers whose attachments range from 1-5 GB that are continuously growing. IF ESRI IS PROMOTING THAT THEIR SOFTWARE CAN HANDLE INVENTORY DATA COLLECTION, WHAT IS THE BEST WAY TO MANAGE THE LARGE DATASET SIZE SO THAT THE LAYERS DRAW CORRECTLY, AND MOST IMPORTANTLY THAT WE STOP LOSING DATA? Our field crews have said on multiple occasions that it takes an incredibly long time to submit when editing existing/adding new assets to these inventory layers (admittedly sporadic). I cannot create hosted feature views to these inventory layers because all assets need to be visible.
Any insight with managing large inventory datasets is extremely appreciated as I cannot find any proper documentation online, even in "Big Data" forums. Thank you for your time.