InfoPath Dev

  Hi, I created an InfoPath 2010 form and wanted to limit users' input into a field call "Nurses Initials", so I added a validation rule with conditions (if) .!="ACS" and .!="ABC".......(70 of them)..and.!="VNH" then screen tip "Incorrect Initials" ..  Those conditions work fine on the InfoPath preview, however, when I published the form to the SharePoint site, I kept getting error msg saying my coding expression could not be parsed because of a syntax error or because it uses undefined namespace prefix or unsupported  function. Can you tell me what happened and how can I fix it? Is it because of the InfoPath rule limit? If so, how can I walk around it? Thanks so much..

First, I'd make sure that it is this rule causing the issue if you haven't already. Save a copy of your form. Remove the validation rule. Does the form publish? If it does, well, at least you know for sure the problem is this specific rule... If it is this specific rule, I'd copy the expression out and split in about half - does the publish work with half as many conditions?

 

 Thanks for your quick reply, Hilary! Yes, it was successfully published when I split in about half.  Also, if I split them about 16 conditions on each expression and make it up to the limit 5 expressions in total, it was published successfully as well. like:

The expression . != "LMI" and . != "LMK" and....16 of them

The expression . != "ABC" and . != "LOK" and....16 of them

The expression . != "POL" and . != "LIK" and....16 of them

The expression . != "RGI" and . != "LTK" and....16 of them

The expression . != "LYU" and . != "JKL" and....6 of them 

In the past, I pasted 70 conditions on one expression, and it caused error. So for my future information, do you know the limit number of conditions on one expression? Thank you, thank you!  

 

I don't! Apparently this was just too complex for IPFS. I'm glad you have a work around.