issues with subtypes in Geoform

2869
1
Jump to solution
03-04-2016 12:23 PM
FrankPrice
New Contributor III

I need to create a geoform with subtypes and default values for some fields.  I have a problem with fields with default values assigned.  Any field with a default value will not be visible until the subtype is picked and then it shows up in the wrong order.  If I remove the default value for this field or don’t use subtypes everything works fine.  This seems to be a reproducible problem.

Here is an example: http://arcg.is/1Ys1wYJ

There is a field (titled “Field that moves”)  that doesn’t show up until you select the subtype (first field) and then it shows up in the wrong order (this field is set up to be last in the list).

Any insight?

Tags (2)
0 Kudos
1 Solution

Accepted Solutions
FrankPrice
New Contributor III

In case anyone else runs into this issue, ESRI says this is intended functionality:

The reasoning for this is so the user doesn't have to see anything they can't fill out yet.

The order is not honored because users will fill out a form from top to bottom. If a field suddenly showed up above, they would likely miss seeing it because they would have to scroll back up and then back down to continue filling out the form. That's why its placed the way it is, to avoid inserting fields into areas that the user already completed or skipped past. Having them grayed out would still be an issue.

Be sure to check the github page for geoform issues: GitHub - Esri/geoform-template-js: GeoForm is a configurable template for form based data editing of...

View solution in original post

1 Reply
FrankPrice
New Contributor III

In case anyone else runs into this issue, ESRI says this is intended functionality:

The reasoning for this is so the user doesn't have to see anything they can't fill out yet.

The order is not honored because users will fill out a form from top to bottom. If a field suddenly showed up above, they would likely miss seeing it because they would have to scroll back up and then back down to continue filling out the form. That's why its placed the way it is, to avoid inserting fields into areas that the user already completed or skipped past. Having them grayed out would still be an issue.

Be sure to check the github page for geoform issues: GitHub - Esri/geoform-template-js: GeoForm is a configurable template for form based data editing of...