nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Change order of capture fields in Quick Capture

EricaNova

I've created a Quick Capture project from the "Rapid Wildlife Reporter" template. When a user clicks on a button to report that they've seen a particular animal - e.g., a moose - there are 2 more fields for users to fill out, "Animals count" and "Field Notes":

The fields are in the same order in the data view of my hosted feature layer view:

But when I go into the mobile app and press the "Moose" button, the user sees "Enter field notes" before "Count". This happened after I updated to the beta version of the app (1.18.85). I think 1.18 stable release comes out tonight, so I'll try again with that release... but... does anyone have any idea how to change the order of these capture fields?

Find more posts tagged with

ArcGIS QuickCapture Mobile App

ArcGIS QuickCapture Designer

Accepted answers

IsmaelChivite

@EricaNova Starting with version 1.18, the order of user inputs is defined by the order in the project JSON. At this moment in time, you need to go into the JSON and reorder things as you see fit manually. Early in 2024 we want to make it possible to change the order visually (no manual JSON editing needed) in the QuickCapture designer. Our intent here is to provide more flexibility: changing the order of fields in existing layers can be problematic. Having the order come from the JSON will simplify things.

More details in this announcement: https://www.esri.com/arcgis-blog/products/quickcapture/announcements/whats-new-in-arcgis-quickcapture-november-2023/

JohnHasthorpe

In the JSON editor, you will need to re-order the user inputs in the userInputs [] array.

Each user input will look like something like this:

{
"autoCompleteMaxEntries": 5,
"id": "001",
"label": "Observer",
"fieldType": "esriFieldTypeString",
"required": true,
"showEvent": "onEnd",
"domain": {
"allowOther": false,
"dateTime": {
"defaultValue": null,
"displayTime": true,
"maxValue": null,
"minValue": null
},
"dynamicList": {
"dataSourceId": null,
"outFields": null,
"where": null,
"orderByFields": null,
"parameters": null,
"updateMode": "automatic"
},
"type": "userDefined",
"name": null,
"inputMask": null,
"multiline": false,
"hint": null,
"codedValues": [],
"range": [],
"showScanner": false
},
"mode": "button"
},

Note that the last user input does not have a comma after its last bracket.

I would use save as in the designer to create a test version of your project, and use a JSON editor to validate the entire project JSON, before saving.

All comments

IsmaelChivite

More details in this announcement: https://www.esri.com/arcgis-blog/products/quickcapture/announcements/whats-new-in-arcgis-quickcapture-november-2023/

JohnHasthorpe

In the JSON editor, you will need to re-order the user inputs in the userInputs [] array.

Each user input will look like something like this:

Note that the last user input does not have a comma after its last bracket.

I would use save as in the designer to create a test version of your project, and use a JSON editor to validate the entire project JSON, before saving.

EricaNova

Thanks @JohnathanHasthorpe and @IsmaelChivite ! To me it seems odd that the update changed the order of my fields from the default (the order in the layer) but looking forward to the next release where this can be edited by users. In the meantime, editing the JSON worked for me. Thanks for the hint, JH - that was perfect.

SamiHammer

Just to clarify: If I want to change the order in which the various user inputs appear in the user inputs array, or is it the actual userInput id number that matters? (Can I leave all the userInput id numbers the same and just reorder the array and that will fix it? That would certainly be simpler than changing all the userInput id numbers and the references to those numbers.)

{

"autoCompleteMaxEntries": 5,

"id": "0018",

"label": "Veg Cover (%) - Floating",

"fieldType": "esriFieldTypeSmallInteger",

"required": false,

"showEvent": "onEnd",

"domain": {

"allowOther": false,

"dateTime": {

"defaultValue": null,

"displayTime": true,

"maxValue": null,

"minValue": null

"dynamicList": {

"dataSourceId": null,

"outFields": null,

"where": null,

"orderByFields": null,

"parameters": null,

"updateMode": null

"type": "userDefined",

"name": null,

"inputMask": null,

"multiline": false,

"hint": null,

"codedValues": [],

"range": [],

"showScanner": false

"mode": "button"

EricaNova

In the newest version of QuickCapture (if you update it), you don't have to fix the JSON - see this post!

https://community.esri.com/t5/arcgis-quickcapture-ideas/implemented-manually-order-button-user-input/idc-p/1408156#M289

"This has been implemented in 1.19. In the QuickCapture designer there is a new option under the more (...) setting called Button user inputs. "

SamiHammer

Thanks! I found it!

MJHEMA

@IsmaelChivite @You mentioned making a product enhancement in early 2024. Has the team implemented this enhancement?

EricaNova

@MJHEMA keep reading, it's implemented 🙂 more info below in URL

Join the Conversation

Signed in members can post, follow updates, and more. New here? Register a free account.

Quick Links

Community Help
Find useful guides, FAQs, and documents to help you navigate and make the most of Esri Community.