Provide an option to locally cache a response to a Field Maps smart form question

06-02-2022 02:24 PM
Status: Open
Occasional Contributor III

It would be great if it were possible to opt to locally cache responses to certain questions in a Field Maps smart form, just as we can in the Survey123 web app.

For example, if we want to use the same smart form at multiple project sites, we need to capture a project number for each record created. For each individual doing field work, that answer will be the same for every feature they create at that project site. It would be nice if they didn't have to enter it repeatedly.

Currently, we get around this by saving a new copy of our template map for each project and then adding an expression to calculate the project number field. If instead we could ask users to enter the project number once and then have it automatically populate (with the option to edit) for each subsequent feature, it could eliminate the map set-up step for each project.


Tags (2)

An alternative solution for you to consider. 

1. Create polygons that cover your project sites with the project number

2. If you don't want to see them, give them no symbol (no fill or outline)

3. Hide the layer from the legend

4. Create an expression that searches the above layer for intersecting features and returns the project number. 


We have recently implemented this to return plantation details from an invisible, underlying layer and seems to be working pretty good. Arcade expression below for reference (utilizes a search buffer distance for features that don't intersect directly)



#feature being created
var BufferedFeature = Buffer($feature, 100, 'meters')
#intersects the above feature with the layer containing the desired attribute
var intersectLayer = Intersects(FeatureSetByName($map, 'Plantations Layer'),BufferedFeature);
#returns the value from the "Plantation" field
for (var f in intersectLayer){
    return f.Plantation





@LindsayRaabe_FPCWA Thanks for the suggestion! That makes a lot of sense, especially if project areas are fairly permanent. We add new project areas all the time, so I think caching is the most flexible option for us, but your idea could be a workable solution for us until caching becomes available. Thanks for sharing the idea and the expression!


This is a great idea, a "retain last entry" checkbox when you configure a field in the Field Maps app* would help with a lot of focused workflows.

*the online/portal Field Maps configuration app needs a mild rebrand to avoid confusion but that's a tale for another time


I agree with David and Holley! Cached values with make our workflow much easier! Is that something we can expect in the upcoming versions?