Field validation failure on not required/blank drop-down box
I have a column in my list that is based on the records in another SharePoint list. When I try to edit a record in Datasheet View, I frequently get the following validation rule failure message: The text entered for Client Impacted isn't an item from the list. Select an item from the list, or enter text that matches one of the listed items. Even though the column appears to be blank to the naked eye, when you double click in the column, it selects what appears to be a space character and when you hit the delete key, it now passes the validation rule. So, my assumption is that the validation rule is saying something like "Space character isn't in the list, so you can't save the record..." Here's what's odd. I do NOT get the same validation rule warning when I edit in standard view and I know for sure that the column has not been erroneously filled with a space character. Anyone have any idea what might be going on here? Thanks in advance for your help. Dave
October 26th, 2010 12:01am

Sounds like you might have fill in the blank option turned on for that field.Brian Bedard, MCTS - - Twitter:@tigertoy
Free Windows Admin Tool Kit Click here and download it now
October 26th, 2010 9:04am

Hi Brian: Thanks for your response. I'm not sure where the "fill in the blank option" resides as I don't see it when I'm in the "Edit Column" screen. On this screen, I see 4 options: 1) Require that this column contains information: I have it set to No 2) Get information from: I have it set to a SharePoint list called Daily Issue Tracking Client List 3) In this column: I have it set to Client Name - i.e. one of the fields in the list mentioned in 2) above 4) Allow multiple values It is unchecked Any direction as to where that setting might reside would be appreciated. Thanks, Dave
October 26th, 2010 9:20am

The "fill in blank option" equates to your option one, it's just a case of semantics. Does the look-up list, Daily Issue Client List feed through a column that is set to require information be entered?
Free Windows Admin Tool Kit Click here and download it now
October 26th, 2010 11:24am

Hi Steve: If I understand your question correctly, yes, the Client Name field in the Daily Issue Client List is a required field in the Daily Issue Client List. But I don't understand why that matters when I'm able to create/modify a record when using the input form and create a record when using datasheet view without filling in the problematic fields. It's only when I attempt to modify in datasheet view that I seem to run into the challenge. Appreciate to know where you're going with this... Thanks, Dave
October 26th, 2010 11:51am

Hi, Did you use lookup column type? If yes, I think you also can select an option from dropdown list or input a value which is contained in the dropdown list. And this column can be blank if you don’t set it as required column. If the column of the source list has space character, the dropdown list in the target list will has this option, too. Hope it is helpful! Seven
Free Windows Admin Tool Kit Click here and download it now
October 27th, 2010 5:14am

Hi Seven: Thanks for your response. Yes, I used the lookup column type and I do NOT force the user to enter a value - but if they do - it must be in the lookup list. As the space character is not in the lookup list, I fail to see how SharePoint "thinks" there is a space in the field when the user does not have the ability to enter it in the first place. That is what is puzzling to me. Dave
October 27th, 2010 8:25am

Hi, I cannot reproduce your issue, please create a new list with a lookup column referring to the new source list and try again. I think sharepoint has not this logic in deed. Seven
Free Windows Admin Tool Kit Click here and download it now
October 27th, 2010 10:46pm

Hi Seven: Here's what I tried: Scenario 1 I set-up a brand new list with only 3 fields: Title Client 1 Client 2 I then linked it to the same client name list. I got the identical validation message that I got before. Scenario 2 I then created a new list of client names with a few entries in it. When I linked the new list to the new list of client names, all is fine. Scenario 3 Finally, I used the existing client name look-up list containing 2,000 client names to create a template - and then created a brand-new list using the template. I then created a brand new list and used the new client list as a look-up field. After doing so, I go the identical validation message I got before! It seems that SharePoint is having a challenge with the Look-Up field in certain situations. Any idea as to why that might be the case? Could it be a volume issue? Again, thanks for any direction you might be able to give. Dave
November 1st, 2010 11:09am

Hi, I have created a list with more than 2000 items and look up it in another list. Everything is working fine. So, I think your clients list has some issue. You can add more than 2000 items into the new source list through copy one column with 1,2,3~2000 from excel into the datasheet view of the source list and try again. Hope it is helpful!Seven
Free Windows Admin Tool Kit Click here and download it now
November 4th, 2010 1:50am

Thanks Seven. A couple of questions/clarifications: I would need to copy the 2,000 names from SharePoint into an Excel spreadsheet via copy and paste or I could use the export to Excel functionality. I think I should then copy and paste from Excel into something like Notepad to make sure I get any problematic characters out of the cells. I would then copy back to Excel and then paste into SharePoint. Does that sound like a good approach? If I do so, my presumption is that it would in no way affect the list I'm doing the look-up from as once the name is selected from the list, it is only using the client name list for validation purpose if the records are ever edited. Can you please confirm that this is the case? Thanks again for your assistance and let me know if my approach makes sense. Dave
November 4th, 2010 9:03am

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics