Hi there,
I have two enhancement requests for project user input:
1. Please respect domains in the same way you do for button user input
2. Please allow multiple project user input fields.
Thanks,
Marc
Ideas raised here:
Multiple project user inputs: https://community.esri.com/t5/arcgis-quickcapture-ideas/multiple-project-user-input-fields-in-quickcapture/idi-p/1027930/jump-to/first-unread-message
Project user inputs using feature service domains: https://community.esri.com/t5/arcgis-quickcapture-ideas/need-the-project-user-input-to-dynamically-utilize-the-field/idi-p/1014411/jump-to/first-unread-message
I concur with Item 1. We need the project user input field to recognize and utilize it's field domain. More, pointedly, it needs to recognize and utilize changes to the domain. We can't go in and manually update the choice list in the QC Designer every time there are new values added to the domain (which sometimes is often). I am going to put this request into the ArcGIS QuickCapture Ideas board.
In the meantime, I'm looking for a way to update the project JSON programmatically.
Hi Marc
From 1.7 you will be able to create lists for project user inputs. This means the user of the app will be able to select from the options yes and no. This is possible in 1.6, but you will need to edit the project JSON in the designer's JSON editor. See: Project JSON—ArcGIS QuickCapture | Documentation
The following project JSON example shows how a codedValue domain user input is defined:
<IMG class="image-1 jive-image" src="https://us.v-cdn.net/6038851/uploads/legacyfs/online/504932_pastedImage_1.png" /><BR /><BR />If the codes in the JSON match the codes in the feature layer field, then the app will be able to submit them.
<IMG class="image-1 jive-image" src="https://us.v-cdn.net/6038851/uploads/legacyfs/online/504932_pastedImage_1.png" /><BR /><BR />
Thanks
John
Hi Johnathan,
I would like to be able to tag every captured photo with either a yes or a no using a project user input field. This flows into two hosted feature layer views determined by whether the quickcapture points are class A or B. I guess a workaround is to have two groups in the quickcapture app, but it seems to me that if you can read domains for a button user input you should also read domains for a project user input.
I would like to have two project user input fields so the user can enter two different pieces of information for all points captured during the session. E.g. the above class A/B and a free text note field.
Hi Marc,
Can you please share your use case, what are you trying to do?
Signed in members can post, follow updates, and more. New here? Register a free account.
Find useful guides, FAQs, and documents to help you navigate and make the most of Esri Community.
