QField Feature Requests

As Qfield user, I would like to suggest a new feature to improve the workflow when editing layers with value-relation fields. Currently, when filling out linked forms (e.g., parent-child relationships), we have to manually save and close each individual form one after the other. I really appreciate that the forms stay open during editing—this is useful—but it would be much more efficient to have an additional button that allows us to "Save and Close All" related forms in one click. Attached is an example of how it could look like. Thank you for your attention. Bye

The feature will allow users to manually type in new values in a field, the most recently entered value will be recalled on the next entry, and a lookup function will auto-fill suggestions of prior values that match characters as users type. Optionally, suggestions will be tied to values in another field. Steps which explain the enhancement User manually enters a value, which is stored with that record User creates a new record, the last value is already entered using the Recall last entered value function User taps in the field and the full text is highlighted to be efficiently overwritten As the user types, other previously entered values are suggested that match initial characters Optionally, value suggestions could be tied to value map entries in another field. Current and suggested behavior Currently in a manual text entry, the last value can be recalled, but previously entered values before the last record cannot be recalled as the user types. An example of workflow for suggested behavior: --In a value map field called "Material", 'andesite' is chosen from the dropdown --In a "Color" field, 'red' is manually typed, and after some other fields are entered the record is saved --In the next record, "Material" is 'chert' and in "Color," 'blue' is manually typed --In the next record, "Material" is 'andesite' again and "Color" auto-fills with 'red', but when the user taps in the color field, 'red' is highlighted and as the user begins typing bl... 'blue' is automatically suggested. Why would the enhancement be useful to most users For data entry in forms, where field technicians must enter a lot of data and a prefilled dropdown value list is not feasible due to the potential uniqueness of observations, the current workflow of manually retyping previously entered values is cumbersome. This suggestion will allow rapid data entry where unique values are needed, and it will also reduce replication error. QField Version: 3.5.5 Fangorn OS and Version: 3.40.6 Bratislava LTR

### Feature Request: Fixed Map Scale and Printing Layout Support in QField #### Summary It would be very helpful if QField supported fixed map scale (e.g. 1:5000, 1.2000,...) display and allowed exporting or printing map images with accurate scale directly from the device. This feature is essential for forestry, surveying, and land-use planning professionals working in the field. #### Problem Currently, QField allows navigation and data collection, but: It does not show the current map scale clearly. It does not allow locking or fixing the map scale (like QGIS layout mode). There is no built-in functionality to export a map layout or screenshot at a known scale for reporting or printing. As a result, users must return to QGIS desktop to generate any printable, scaled map – which reduces QField’s field autonomy. #### Proposed Solution Add an option to display the current map scale on the interface (e.g. 1:5000). Allow locking a map scale so that users can pan without zooming, maintaining scale integrity. Option to export the current view as a scaled image (PDF or PNG) with metadata or a small layout frame (optional). #### Use Case In forestry projects, field users need to capture maps at fixed scale (e.g. 1:5000 or 1:10000) to: Verify boundaries Document fieldwork Submit reports to authorities Having this directly in QField reduces office work and increases data accuracy and efficiency. #### Environment QField version: [ 3.2.0] Android version: [Android 12] Thank you for this amazing app! Looking forward to your feedback.

Basically, this idea explains exactly what I'm looking for, but is only works for Value Map: https://ideas.qfield.org/app-feature-requests/p/radiobutton-instead-of-dropdown-list I would like it to apply to Value Relations. We use hundreds of those and they provide a more robust way to create standardized forms, and this would help accelerate field work!

In QGIS, you can select a number of column to which the multiples selections in a form can be divided. While this works decently in QGIS, it simply doesn't translate in QField. It would be interesting to have this, especially for large choices selection.

I would like to request a new feature in QField where, after each synchronization with QFC, a notification popup appears. This popup should display important notes from the previous user, such as anomalies, special observations, or instructions for the next person working on the project. The message should be editable directly within QField, without requiring a separate sync with the local QGIS project via QFieldCloud. This would greatly enhance team communication and streamline the workflow.

Currently Qfield requires files to be copied to 'imported projects'. My group have large base maps which chew up a lot of iPhone storage. Qfield can open files from the cloud when online, why can't it open them from a USB stick offline? Being able to specify any folder kept anywhere on the phone or on an external drive, would allow us to use old iPads with limited storage for example.

Add function of setting up user-agent.

Add function of setting up user-agent.

I would like to request a feature that allows adding a watermark to photos taken within QField. Specifically, the watermark text should be dynamically sourced from a field in a selected layer. For example, when collecting a point feature and manually entering a sample name in a designated field, the photo taken at that point should automatically include the sample name as a watermark. This feature would be highly useful for field data collection, ensuring that captured images are clearly associated with their respective data entries. Would this be possible to implement? Thank you for considering this request!