Ability to add form element that does not store any data

[ajevans429]

The idea is to allow the creation of “dummy” elements within the form that will prompt a user for information, but does not submit any data to be stored. These elements can be used to hide/show other fields, or can contain a value on which to base another field’s calculation.

I believe that survey 123 connect currently allows this, and what I’m proposing would be similar.

[JustinReynolds]

They could also be used to to show hyperlinks to other content (on portal/agol or external) or be used to embed documents inline like standard operating procedures or safety guidelines for field staff to reference. As @ajevans429 mentioned, helper form elements exterior to your schema would be very useful.

This seems like an easy to implement thing from within an edit context of INSERT, but seems like it could get a bit tricky in the context of an UPDATE given some scenarios; but either way I would use this concept extensively.  It would help our Map-Centric workflows compete better against our company's Form-Centric workflows... which exist outside of the ESRI ecosystem.

[Michael_Lowry]

I would find this to be very helpful. I'm designing a form with a couple dozen fields whose values will be copied into other fields and processed using calculations. It would be great to be able to exclude the unprocessed data from the attribute table instead of clogging it up.

[ahargreaves_FW]

Still being asked for. See here.

[MollyWalkner_1]

Curious why this isn't already an option in smart forms, considering it is possible in survey123. This is a critical feature for limiting data access in review/editing workflows for internal organization members (often non gis/data savy people) and making the process more user friendly.

This feature is super helpful in limiting the fields that the form user can see when editing. For example, current attributes (with stored values) of the feature can be shown in a simple text box. Then include a multiselect question showing all field names. The user selects only the field names for attributes that need to be altered (this info does not need to be stored). This controls visibility/relevancy for the actual editable fields. Limiting information on the form and simplifying the information make the user experience much less intimidating.

Overall, this really helps with data review workflows limiting the fields the user can click on.