Hello,
I have a hosted feature layer used with the Survey123 app. Users click on dots on the map to open and submit a survey. However, I want to prevent surveys from being submitted for dots that are not eligible. How can I achieve this?
Give this a shot.
EDIT: Just so we're clear, I modelled a few items off the example you sent for the sake of familiarity (since you seem to be aiming for that). The ${my_dropdown} is a placeholder though, and not something intended to be in the final product.
You can pull that value into S123 via URL parameters (if not doing so already), and use it in a calculate field. If you dynamically make fields Read_Only = Yes and they are required, form cannot be submitted. I do something similar in a form where I lock users without accounts from collecting from the app directly.
I am using Experience Builder and the Survey Widget within that. Aiming for something like this.
https://experience.arcgis.com/experience/4299aff15d8a47a69a9a352aa5ce3049/page/Page/#data_s=id%3AdataSource_1-185cb2af2f7-layer-7%3A10264
I 've configured everything to my liking, except that I want the Survey to be non-submittable if the Road for example is "Not Eligible"
Yep, that is pretty easy. Just pull that "Not Eligible" value into a hidden field.
In this example, I the field ${launch_l_yes} is testing for the word "Link". If the field ${launch_type} = "Link, then the result is "yes". ${launch_l_yes} is used in the readonly column for a bunch of fields.
The end result is that when "Link" is detected, all those fields become readonly = yes.
I've attached an example that may work for you.
I did this but unfortunately the Survey still accepts the response and allows submission.
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.
