{relationships/0/FieldName} not working in Field Maps popup but works in the web map

Question

{relationships/0/FieldName} syntax is not working in Field Maps popup but works in the web map.  This was an issue back in the old map viewer for many, many years.  I talked to @JeffShaner about it a few times but it was punted to the new map viewer.  It still seems to not work.

I am testing moving to the new map viewer for our field projects.  Currently I must use 32 Arcade expressions with FeatureSet just to look up attributes from the parent that I then use in Survey123 Launch URLs.

DesignLat {expression/expr6}
var tbl = FeatureSetByRelationshipName($feature, "Points", ['DesignLat'], false);
return First(tbl).DesignLat

Then 
arcgis-survey123://?itemID=87ef1194dac&field:PointID={PointID}&field:DesignLat={expression/expr6}

In the popup I can add related fields using the syntax {relationships/0/FieldName} and it does work great in the browser and my URLs form properly

arcgis-survey123://?itemID=1b2594e&field:PointID={PointID}&field:CollectTurbidity={relationships/0/CollectTurbidity}

But in Field Maps it is not giving me any values for {relationships/0/CollectTurbidity} so my URL looks like  arcgis-survey123://?itemID=1b2594e&field:PointID=SomethingID&field:CollectTurbidity=  which means nothing is getting passed.

Is there some other syntax here to grab the related fields?  I am not seeing anything that says this does not work.  Is it a bug, not supported, or is there any timeline here?  It would be so nice not to have to manually add 32 Arcade expressions by hand.

thanks

dougbrowning · Answer

That is a bummer it would be way less work and it is already working great in the map viewer - it is only Field Maps where it does not work.  We seem to keep losing more and more functionality over time honestly.  Esp the new JS 4.0 tools.

thanks

ColinLawrence · Answer

Hi @DougBrowning sorry for the delay in seeing this one. I dont have the greatest answer for you but from what I have gathered it seems that Map Viewer is moving away from the /relationships/0/ syntax in favor of using arcade and for this reason runtime has decided not to address the issue you are pointing out with pulling in the relationship field values. By using arcade to generate these URLs you are already using the recommended practice.

dougbrowning · Answer

Bump to @JeffShaner or maybe @ColinLawrence   if any progress on this?  Is it on the list?  I have field season builds coming up and have to make 100 arcade expressions across my projects.  This fix would eliminate all of them.

It got posted again today in the 123 board  https://community.esri.com/t5/arcgis-survey123-questions/prepopulate-field-from-related-table/m-p/1572054#M60661

Thanks