Accepted Solutions
Correct, as of now it can only be done through editing the JSON. It's not too tricky if you make sure to follow the syntax. Here's how to do it:
- Click on the </> next to gear at the top of your QuickCapture project in the designer. Click Edit to edit the JSON.
- If you want, copy and paste all the JSON currently in the designer to Notepad to have a backup.
- Now you need to define the user input variable. Scroll all the way to the bottom of the JSON. There's a line that says
"userInputs": [],
our code is going to go inside the empty [ ]
- The main parts of the code are
1) ID (unique identifier, can be any text)
2) Label (shown above the input textbox in the mobile app)
3) Field Type (either esriFieldTypeString, esriFieldTypeDouble, or esriFieldTypeInteger)
4) Required (true or false; true means that the user must type in a value. It will exit the project if they try to hit Cancel to get past the prompt)
5) Domain (constrains which input is valid; value must be either range (numerical range), codedValue (predefined allowed values like Yes or No), or userDefined (can set an input mask, like 9999 would force user to input four digits))
(see screenshot below for what I did)
- Then you just have to tell QuickCapture which field will use this defined user input variable. Search for the field's name. In my layer it's called casenum. By default, it said:
{
"fieldName": "casenum",
"value": null
}
I changed the null to "${userInput:apple}" because apple was the unique id for the user input variable that was defined at the bottom of my JSON.
Here's the finished section of my JSON with what I changed in yellow. You can leave inputMask null if you don't want to use it. Let me know if you have specific case number syntax and I can try to help you with the masking. A common JSON mistake is to leave a comma at the end of the last line within brackets. Notice "range":[] doesn't have a comma at the end when "codedValues": [], does. "userInputs":[all our code here], does because "version":0.1 comes after it in the greater { }. If you get an invalid JSON error, check for these commas or for a missing " " on your label, fieldType, id, etc.
Note: I'm not using codedValues and range as I'm using userDefined as my type, however the JSON editor kept adding these lines back in automatically so I provided the full screenshot here so you wouldn't be confused. Since their brackets are empty [ ], this extra bit of code isn't hurting anything.
When I open the project in the app, I am immediately prompted to enter a case number. Here you can see that the label value shows over the text box and the hint shows below it in grey. Once entered, the value will show at the top of the project where it currently says N/A so you know what is currently set and you can click the pencil to edit it.
