Hi !
We face a problem with hidden question from collect email and username
Even if they are not required, WebForms returns an error at the end of the form saving about two questions. When I delete those questions its ok.
Hi !
We face a problem with hidden question from collect email and username
Even if they are not required, WebForms returns an error at the end of the form saving about two questions. When I delete those questions its ok.
Can you give any more details about the email and username questions? Do they have constraint or required conditions? Does the error message give any more details about what's going wrong? Are you able to share the form itself, or a simple version that would help me work out what's going wrong?
Thanks!
Hi Gareth,
Thanks for your reply.
There are used to set default values of both email and username text question, using a coalesce() formula (between last-saved value and Collect metadata)
Here is the problematic header of the form :
Crabe_bleu_issue.xlsx (204,3 Ko)
We get no information but this one :
![]()
Very helpful, thanks!
I see what you mean about the coalesce. The last-saved won't work on first load, so then it tries to set the username and email based on the preload properties. In Collect these are configured in the app. But currently Web Forms doesn't have access to that data so they're blank which fails the required constraint.
How were you planning to use this form? For example, is this going to be shared as a public link, or will users be required to log in to Central first?
Hi Gareth,
This form is bith used in collect and enjeto/webforms (public link) since two years.
But we can drop the two collect question from that form.
It is just an help for us to get clean emails to identify data owners in more "important" core forms.
But I think we have core forms forms we would like to use on mobile and web.
@mathieubossaert could you update your calculation logic so that it returns a value for the name/email when username is blank perhaps via a fallback second coalesce so the form can still be used for Collect & WF now? And a constraint to block that value from being left as is.
eg (but in French!)
coalesce(coalesce(${last-saved#user_name},${username}) , 'enter your first & last name')
w/ constraint contains(.,' ') and . != 'enter your first & last name'
coalesce(coalesce(${last-saved#user_mail},${email_utilisateur}) , 'enter your email')
w/ constraint contains(.,'@') and . != 'enter your email'
Hi Andrew,
Good idea. I'll check in the morning ans I'll tell you.

Thank you so much Andrew !
Here's your clever and working solution :
Crabe_bleu_issue.xlsx (204,4 Ko)