Accepted Solutions
Here's the break down on the Feature Set by Relationship Name function:
FeatureSet functions | ArcGIS Arcade | Esri Developer
'monitoring_notes' in mine is the relationship name between my point layer (parent) and the monitoring notes table (child) as set by the hosted feature service. To find it, open your hosted feature service, click the link to view the REST services, then click on the parent layer. Scroll through the REST data until you see Relationships.
point_guid is the GUID field name I set in the child layer, yours will need to be whatever your GUID field name is. The False parameter is True/False for bringing the geometry in with it.
For:
var glid = Text("&q:where=point_guid=" + "%27" + $feature.GlobalID + "%27");
This is a query where the attribute in the point_guid field (the GUID field in the child layer) matches the feature's GlobalID attribute. You would need to change point_guid to whatever your guid field name is, but everything else should be able to be left unchanged. Just check to make sure your parent layer's GlobalID field is formatted the same; e.g. globalid is different than GlobalID. If yours is different, change the arcade script to match.
That error code 400 could be from a couple things. The else section of the script is checking the inbox folder of the survey matches to the search criteria. Make sure your inbox is enabled on the survey and the send folder is disabled. Another thing is check your xlsform on the survey and make sure your repeat tables (related records) have the bind::esri:parameters column with query in it, that will allow it to search the repeats when you open an existing record in Survey123. If you need to edit the repeats you need to also include allowUpdates=true. Here's a link on how to set up Survey123 to view and edit existing records in the field app.
Check out this video, specifically the arcade section. It is going to help a lot to understand the concept. My features only have 1 related record per feature, so I didn't need to do any for loops for multiple related records.
What your script is currently doing is if there are 0 related records to a feature it formats a link to create a new record that will be related to the feature. Else, if there are not 0 related records it formats a link to open survey123 and edit the record. However, this script only accounts for 1 related record and not multiple records being returned. Since you say you might have multiple related records you'll need to use a for loop.
Since you also might want the status or date you'll need to add those to the list in the FeatureSetByRelationshipName. So instead of ['GUID'] you'll want ['GUID', 'Status', 'Inspct_Date'] or whatever those field names actually are. If you want to bring all fields in (a potential performance issue if there's a lot you could use ['*'] instead.
This is untested, but conceptually what I would try first to make it work with multiple relates where the link is showing the Status field as the link text. I moved var fullURL into the if and the else statement and then set an output that should hopefully pass the urls on to the return section, so you should get a list of URLs. If your Status field isn't exactly that change it in the list and the rec.Satus line to rec.whateveritactuallyis in the for loop.
var urlsource = 'arcgis-survey123://?';
var inspection = FeatureSetByRelationshipName($feature, 'SignalInspection',['GUID','Status'], false);
var insp_count = Count(inspection);
if (insp_count==0) {
var recmess = Text("Create New Record");
var glid = '';
var params = {
itemID: 'b5ad40b0c8014d7c92715d1fb65a2de1',
action: 'collect',
"field:GUID": $feature["GlobalID"]
};
var fullURL = urlsource + UrlEncode(params)+ glid;
output1 += text(fullURL)
}
else {
for (var rec in inspection){
var recmess = rec.Status;
var glid = Text("&q:where=GUID=" + "%27" + $feature.GlobalID + "%27");
var params = {
action: 'edit',
folder: 'inbox',
itemID: 'b5ad40b0c8014d7c92715d1fb65a2de1',
update: 'true'
};
var fullURL = urlsource + UrlEncode(params)+ glid;
output1 += text(fullURL)
};
}
return {
type: 'text',
text: `<p> <a href="${output1}" target="_blank">${recmess}</a></p>`,
}
