At creation time of InfoPath forms, i never got this unwanted behaviour – until today. I created a InfoPath form with some standard columns /fields and then i added a lookup column to another list. I did it just as the many times before. But in this case the lookup column had to be mandatory.
What is makes the difference? A lookup column looks up the values from the other list and displays it in a dropdown list. Nothing special. But when you make it mandatory the form creates a nice message for the user when he put his mouse over the field:
only positive integers allowed
But normally this occurs, if you put the display value to the value field instead of the ID. In InfoPath you tell the lookup a display value for the dropdown and a normal value. The last one is normally for the id of the element.
What is the workaround?
The workaround tells you in the next minutes what to do:
Step 1: Open InfoPath and open the settings of your lookup field
Step 2: uncheck the checkbox that the field may not be empty
Step 3: Add a rule to this field (Open Manage Rules and add one of the type validation)
Step 4: Add a condition: If your lookup field is empty
Step 5: Add a Quickinfo: your message – Note there must be a message
Step 6: Deploy
Now your form and you lookup field does not show this user unfriendly message.
Maybe this helps.
..:: I LIKE SHAREPOINT ::..The article or information provided here represents completely my own personal view & thought. It is recommended to test the content or scripts of the site in the lab, before making use in the production environment & use it completely at your own risk. The articles, scripts, suggestions or tricks published on the site are provided AS-IS with no warranties or guarantees and confers no rights.