Just ballparking here... (I'm also not sure exactly what we want to end result to be? Do we just want a URL to sling over to Survey123 that has all the fields/values you need to start with?)
Create a calculated expression, so you can use it. It doesn't need to be applied, but that way we can use it in different places.
Perhaps, in this expression, you can first get the fields from the related table. Grab only the fields you need by excluding the ones you do not. In the code, I'm just getting the fields, but you could do the same and also grab the data along the way from the related FeatureSet. From there, you can build out your URL parameters if that is what you're trying to do. I know you're a pro, so I'm probably missing something here in the potential solution, but I figured this might be a possible way to save some typing. Annoying that you cannot simply access the fields names from the related FeatureSet (I think), so I figured "let's go get the fields a different way", then use that to mine through the related records with our favorite fields in hand.
I've done this in pop-ups where I just loop through the fields. Just be aware, I've seen some wonky things with FeatureSets only returning 1000 records in Field Maps where they return the full fset in the webmap viewer. (I think I can work around that possibly, but I thought that was odd, and I think I have to tackle it a slightly different way/)
var rel_records = FeatureSetByRelationshipName($feature, "BK_Sites_Activities_Tbl")
var tbl_fset_schema = First(FeatureSetById($map, "18c356a127f-layer-8"))
var fields_to_skip = ["CreationDate","Creator","EditDate","Editor","OBJECTID"]
var my_fields = []
for (var v in tbl_fset_schema) {
if(!(Includes(fields_to_skip,v))){
Push(my_fields,v)}
}
// get rel_records
// loop through them
// use your fields schema
// get values similar to above
// return rel_records or format URL for related records?
return Text(my_fields)
// Tested to make sure I can return this as a calculated value or using an info element
This is only about 20% of the code, because it gets very specific from here, but I've created long strings of field names and values by just looping through a FeatureSet that will show up in Field Maps, so I assume you could do the same and format your URL parameters along the way. The trick here I'm assuming is getting what field names you need from the related record schema, so you can use them in the relationship? If not, I'm missing what we're looking for, but I hope this was somehow helpful.
Mitchell Grafstein, Horticultural Inspector 1, NYS Dept. of Agriculture and Markets
