I was wondering if there are issues when creating a report using a field in Survey 123 that has the bind::esri:fieldType set to 'null'.
Does the report still capture the value even though the field is not created on the feature layer?
It will not, no. The report has access to all fields in the layer, but as the report service is separate from the survey itself, there's no way for it to know about those null fields.
What's the use case here? If it's worth including in the report, it's probably worth tracking as an attribute, isn't it?
The first version used integer driven fields through the report, new client had wanted choice driven fields in the survey to limit user error and visibility of distinct numbered answers. I was trying to determine which one to keep rather than have both a string and integer field for each question in the feature layer.
Signed in members can post, follow updates, and more. New here? Register a free account.
Find useful guides, FAQs, and documents to help you navigate and make the most of Esri Community.
