DCSIMG
The following expression could not be parsed because of a syntax error or because it uses an undefined namespace prefix or unsupported - Adlai Maschiach

Adlai Maschiach

" You have to show in order to be seen "

News

Favorite Links

news

CardSpace

Books

Other InfoCards Proj

Virtual Earth

WSS / Sharepoint

SOA , Biztalk & ESB

CLR / .NET

The following expression could not be parsed because of a syntax error or because it uses an undefined namespace prefix or unsupported

The following expression could not be parsed because of a syntax error or because it uses an undefined namespace prefix or unsupported

Problem:

The following error occurs when you try to upload a browser based InfoPath 2007 Form which has .NET “code behind”

ServerError

Form Verification Status

Failure

Btn The following expression could not be parsed because of a syntax error or because it uses an undefined namespace prefix or unsupported function: /dfs:myFields/dfs:dataFields/tns:SetValue/s1:fd manifest.xsf


Cause:

For now, it seems that you have built one web service that uses a lot of different complex types ( which have different namespaces ) as a messages to serve different InfoPath forms

Solution:

In short – Just like the joke goes “close everything and re-open”, well it worked for me – or in other words :

  1. Remove the Data Connection to the “Set” [WebMethod]
  2. Save the form
  3. Re-open it
  4. Add a new Data Connection to the “Set” [WebMethod]
  5. .. and walla ;)

and now you’d get this

DataConnectionDefinition

The ohh so needed “my” namespace instead of “s1” , “s2” , “s3” …. namespaces

Comments

nick_pasors said:

# June 30, 2009 4:49 AM

Melissa said:

Thank you so much!  Worked for me, too!  I thought I was going to have to rewrite my webservice.  <Phew>!

# August 17, 2011 5:54 PM

Ventrazza said:

Thanks so much !

# October 7, 2011 6:23 PM
Leave a Comment

(required) 

(required) 

(optional)

(required) 


Enter the numbers above: