Latest Contributions by ZhifangWang

Hi @SFM_TravisBott , If I understand correctly, this should be available in the feature report, as long as all layers are in the same service. Using the above example: When you iterating records in a child layer (the current data context is a feature in the child layer), you can reference any attribute/geometry of its parent feature by specifying the parent layer name. For example,  ${#layerB} This is an attribute of layerB ${field1inLayerB} This is an attribute of its parent feature in layerA ${layerA.field1inLayerA} ${/} When you iterating records in the parent layer (the current data context is a feature in the parent layer), you can also access all child features by opening an inner iterations. For example: ${#layerA} This is the feature which object ID=${objectid} Below are child features in layerC: ${#layerC} (this iteration is under the context of the current parent feature) child feature, objectid=${oidFieldInLayerC} ${/} ${/}   Please refer to the Repeats section in https://doc.arcgis.com/en/survey123/browser/analyze-results/featurereporttemplates.htm.  ... View more

Hi @wilcow , Thanks for sharing the XLSForm and report template files, these help us locate the cause of the issue.   It turns out that in your XLSForm, there are several image questions (~21 rows) are set bind::esri:fieldType=esriFieldTypeString by mistake. This is caught by the syntax checking enhancement in the latest release last week.   After fixing all bind::esri:fieldType errors in the XLSForm and republish your survey, the report should be able to print as expected.   Please let us know if you still observe any issues after the change.   Thanks, Zhifang ... View more