MerginMaps Complex Form Build
Budget: $2 – $8 AUD
I need the data collection workflow in my MerginMaps project tightened up with a set of brand-new data entry forms that feel effortless in the field yet capture every detail we need. The core form must include text fields, dropdown menus, and date pickers, plus the ability for users to attach photos on-site. Because each parent record can spawn multiple child records, I also need a subform that manages this relationship cleanly.
Beyond layout, the forms have to work intelligently: required fields should carry validation rules, certain sections must appear or hide through conditional logic, and several values should auto-populate from context or previous entries to speed users along and minimize errors.
Deliverables
• MerginMaps form template (or QGIS project ready for MerginMaps) with all forms and subforms configured
• Field validation rules, conditional logic, and auto-population fully tested on both desktop and mobile
• A brief hand-off note explaining where to tweak fields or rules in future
Acceptance criteria
• Forms sync to the MerginMaps mobile app with no schema warnings
• Photo attachments and child records save reliably offline and after sync
• All validation and conditional visibility behaves exactly as specified
If you know your way around MerginMaps designer, and the MerginMaps plugin, this should be straightforward. Let me know your estimated turnaround and any similar projects you’ve tackled—looking forward to getting this live.
Examples of the form to create are attached in the file
Beyond layout, the forms have to work intelligently: required fields should carry validation rules, certain sections must appear or hide through conditional logic, and several values should auto-populate from context or previous entries to speed users along and minimize errors.
Deliverables
• MerginMaps form template (or QGIS project ready for MerginMaps) with all forms and subforms configured
• Field validation rules, conditional logic, and auto-population fully tested on both desktop and mobile
• A brief hand-off note explaining where to tweak fields or rules in future
Acceptance criteria
• Forms sync to the MerginMaps mobile app with no schema warnings
• Photo attachments and child records save reliably offline and after sync
• All validation and conditional visibility behaves exactly as specified
If you know your way around MerginMaps designer, and the MerginMaps plugin, this should be straightforward. Let me know your estimated turnaround and any similar projects you’ve tackled—looking forward to getting this live.
Examples of the form to create are attached in the file