v3 is evaluating constraints on fields that are not relevant yet

85
1
08-16-2018 10:38 AM
Highlighted
Frequent Contributor II

I have a form that was in use for 6+ months now without issue.  I updated to v3, made a small change and republished.  The form then suddenly starting stopping submissions giving a error that a constraint was being broken, on a field that was not even relevant at the time and the user cannot even see.  I had to add "" empty string now to the constraint to get around it.  Always worked as designed before.

Is this a new bug?  Why would a constraint be checked on a non-relevant field?

thanks

Reply
0 Kudos
1 Reply
Highlighted
Esri Regular Contributor

Hi Doug

Are you able to share your survey xls? I'll take a look.

Thanks

John

Reply
0 Kudos