When you want to create Offline Areas in Field Maps Designer and get the Failed message, it would be really handy to get some detail in a viewable error list to help diagnose any issues.
Further to this, to pre-emp any errors, please add a Sanity Check tool in the Designer so we can do a 'dry run' to check if any of the settings in a map or form may confuse AGOL during the creation of a full fat offline pack.
The dry run would check everything except the geometry, and highlight the typical oversights such as duplicate layers, missing item.json files (no idea why they keep getting lost unless it has to do with the June 2025 Update bugs features).
Hi @RTPL_AU have you seen the offline validation options within Field Maps Designer today?
You can access these by opening the map in Field Maps Designer and Opening the Offline options from the side menu. Here it will make you aware of configuration conflicts with going offline for example including the same layer twice in a webmap.
@SarahSaint-Ruth
Yes.
We still find at times that the Offline Areas process fails for some obscure reason even when the Content shows nothing is wrong.
This also ties to the Ideas of having clear AGOL status indicators in AGOL & Pro so that we can be informed when you are having issues; failures in processes are then likely not to have originated at the client side. That would've saved me hours on Saturday.
The error message of "Failed" is a bit lacking, don't you think?
Hi @RTPL_AU thanks for getting back to me so quickly, and glad to hear you make use of the offline validations already. Sorry that you experienced difficulties going offline last week. We are in agreement regarding messaging and improving the experience of taking data offline.
Could you share what method your teams in the field use to take data offline? Do you leverage pre-planned areas or do users define the areas they wish to take offline in the mobile app?
@SarahSaint-Ruth I'm referring to creating Offline Areas in Designer. Idea edited to clarify.
In the mobile app you can extract the logs - wish we can get to the same in AGOL.
I agree with this. We should be able to ascertain exactly which layers are causing issues within Field maps designer, if an offline areas fails, we should be able to tell exactly which layer is causing the issues within the desktop interface without having to launch field maps on a mobile device and view troubleshooting logs. It would be great if we could access logs from here.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.