Bug
Adding workflow automators such as Microsoft Flow and Integromat as WebHooks to surveys created in the Survey123 for ArcGIS website do not recognize the field or choice names designed in the survey. Instead, the generic field names, not the aliases, are displayed in the flow designer and in any resulting actions.
| Bug ID Number | BUG-000115734 |
|---|---|
| Submitted | July 30, 2018 |
| Last Modified | June 5, 2024 |
| Applies to | ArcGIS Survey123 |
| Version found | 3 |
| Operating System | Windows OS |
| Operating System Version | 10.0 64 Bit |
| Status | Known Limit |
Additional Information
This is a known limitation of webhooks in Survey123 for ArcGIS. A webhook payload contains field and choice names only, not labels. This is by design; fields and domains are preserved but labels might be modified after publishing. For surveys published in Survey123 Connect for ArcGIS, field and choice names can be specified in the XLSForm. For surveys published on the web, the web designer allows the modification of field and choice names when publishing the survey through the Modify Schema dialog. In Survey123 Connect for ArcGIS 3.3, the names that are automatically generated in web designer, more closely match the labels entered by the user; previously these are assigned generic names such as field_0, field_1, etc. These choice names can be further refined if required in the Modify Schema dialog. To utilize the field or choice labels, a label lookup could be used in the flow itself. Alternatively, the survey could include a calculate question using the jr:choice-name function to return the label for a select question.Workaround
Use the Survey123 Connect for ArcGISÂ application to create a survey to use with WebHooks.Steps to Reproduce
Bug ID: BUG-000115734
Software:
- ArcGIS Survey123
Get notified when the status of a bug changes
Discover more on this topic
Search for related information
Find training related to this topic
Explore ideas and give feedback
Get help from ArcGIS experts
Download the Esri Support App