You are viewing limited content. For full access, please sign in.

Question

Question

Form required field message

asked on February 18, 2016 Show version history

We have various forms with required fields.  Some are lookup fields and others are not.  However on a few lookup fields for example, when the form is launched it immediatly seems to warn about putting in an option.  As if the user has clicked in it but not selected anything.  For example:

Is a lookup dropdown menu.  This is what it looks like when the form is launched.

However on another form we have this field.  It is not the first field in the form just like Document Type.  When the form is launched it shows like this:

We have other lookup fields on forms and some of them do this and others do not.  Is there a reason why some of them immediatly throw this "error" while other lookup lists do not?

 

Thanks

0 0

Replies

replied on February 18, 2016

For your lookup fields are you getting the data from table or stored procedure. Could be that data your field is retrieving data in multiple times and form thinks that user clicked but not selected anything.  

0 0
replied on February 18, 2016

We are getting it just from a lookup table.  I am wondering if it is the first emtpy required field or something that focus is landing on.

0 0
replied on February 18, 2016

Could be. You said for some lookups fields it doesnt happen. If i were you i would find a difference between those fields and fields where error is showing up. 

0 0
You are not allowed to follow up in this post.

Sign in to reply to this post.