From the sound of things, there are multiple inspections that need to happen for a single dam. Is the data set up that way, with a related table for inspections? Or *can* it be set up that way, if the schema isn't set in stone yet?
To answer your question, I believe you could do this with Field Maps and a dynamic URL. More information about the data structure would be helpful, but I'm going to make some assumptions here. For one, we'll assume there's a field to differentiate between routine and followup inspections. Two, we'll assume that the inspections happen in a related table connected to the dam features.
The Form
In our Survey123 Connect XLSX form, we create a series of hidden questions at the top of the form. Each of these corresponds to the recommendations in the survey itself. Be sure to set the field type to null, as we do not want these fields to actually exist in the layer. And the "inspection_type" form can default to "routine" and be hidden as well, though that one isn't null.
| question type | name | default | bind::esri:fieldType |
| hidden | recommendation1_relevant | N | null |
| hidden | recommendation2_relevant | N | null |
| hidden | inspection_type | routine | esriFieldTypeString |
Later in the form, we use the value of these fields to drive the visibility of the real questions.
| name | relevant |
| recommendation1 | ${recommendation1_relevant} = 'Y' or ${inspection_type} = 'routine' |
| recommendation2 | ${recommendation2_relevant} = 'Y' or ${inspection_type} = 'routine' |
Since these are hidden, null fields, they generally won't have an impact on the form, but that's where our URL comes in.
Survey Link from Popup
In our web map, we put use an Arcade popup element to generate a link. This link will use URL parameters to set "inspection_type" to "followup", and then set the various recommendationX_relevant fields to "Y" as needed.
// get the most recent inspection for the clicked feature
var insp = FeatureSetByRelationshipName(
$feature,
'dams_inspections'
)
var insp = OrderBy(
insp,
"inspection_date DESC"
)
latest = First(insp_sorted)
// start making survey link
var surveyURL = 'https://survey123.arcgis.com/share/your-survey-itemid?field:inspection_type=followup'
// list of recommendation field names
var recs = [
'recommendation1',
'recommendation2'
// and so on
]
// go through list of field names; check value of routine inspection recommendations, add to URL as needed
var followup_values = ['incomplete', 'ongoing']
for (var r in recs) {
if (Includes(followup_values, latest[recs[r]])) {
surveyURL += `&field:${recs[r]}_relevant=Y`
}
}
return surveyURL
This should spit out a URL, which will include a "&field:recommendationX_relevant=Y" parameter for each item set to "incomplete" or "ongoing" from the most recent inspection.
Clicking the link will open the form as usual, but because we've changed the inspection type and specified which relevant fields will be set to "Y", the form should hide all irrelevant fields, prompting only for those incomplete and ongoing items.
It's a lot to set up, and will need some tweaking to meet your data's particulars, but it's possible.
- Josh Carlson
Kendall County GIS
