Select to view content in your preferred language

Form breaks when contingent value fields are required

80
0
Tuesday
SCVOSAGIS_Program
Occasional Contributor

I have layers with contingent values that I want to make required in Field Maps. It works perfectly when the fields are not required. When I change them to required, I don't see anything different in the Web Designer, but in the app it wont let me create a new feature with error "The form contains unsupported data".

Is this expected behavior? What about contingent values would inhibit the use of required fields?

Edit to add: Form only breaks when fields within the Field Group are required. Its ok when non-contingent fields are required.

0 Kudos
0 Replies