Zobrazují se příspěvky se štítkemInfoPath. Zobrazit všechny příspěvky
Zobrazují se příspěvky se štítkemInfoPath. Zobrazit všechny příspěvky

pátek 14. května 2010

Submit entire InfoPath form to web service

This post explains on a simple example how to submit the entire XML of the InfoPath form to a Web Service and process it.

During my last assignment, I needed to submit the content of Repeating Table of InfoPath form to Access Database.
The form had to be published on SharePoint Site - so I could not submit directly to the database, but I was forced to use the web service (because web enabled forms do not allow access directly to the database)

So I build a web service method which allowed me to submit one row of the Repeating Table to the database and I thought that I would be able to submit each row in some kind of a loop inside the InfoPath form. Well it did not work, I was just able to submit the first row all the time and nothing more.

So I decided to submit "the entire form" and than parse it on the web service side. Here is a short example of how to do this.

Preparing the InfoPath form


First let's create simple InfoPath form with one repeating table (eg. list of products)



Now what you have to do is rename the fields in the "Data sources" tab. Later you will use these names of the fields to get the values stored XML representing the InfoPath form.


Creating the Web Service


In the web service you will need a method which takes XmlDocument and will parse this XML document representing the InfoPath form and store it's values to the database.

[WebMethod]
public void SubmitDocument(XmlDocument doc)
{           
XmlNamespaceManager nsManager = new XmlNamespaceManager(doc.NameTable); 
nsManager .AddNamespace(formNamespace, formURI);
nsManager .AddNamespace("dfs",
"http://schemas.microsoft.com/office/infopath/2003/dataFormSolution");

XmlNode root = doc.DocumentElement;
XmlNodeList list = root.SelectNodes("/dfs:IPDocument/my:myFields/my:prodList/my:product", nsManager);

foreach (XmlNode node in list)
{
string name = node.SelectSingleNode("/dfs:IPDocument/my:myFields/my:prodList/my:product/my:name", nsManager).InnerText;
string price = node.SelectSingleNode("/dfs:IPDocument/my:myFields/my:prodList/my:product/my:price", nsManager).InnerText;
string amount = node.SelectSingleNode("/dfs:IPDocument/my:myFields/my:prodList/my:product/my:amount", nsManager).InnerText;

SubmitToDataBase(name,price, amount);
}
}


In this method first we initialize the XMLNamespaceManager. To this manager we will have to add 2 namespace. First one is the namespace of the data source of the InfoPath document. This one we can find out in InfoPath client by navigating to Properties -> Details.

Now when InfoPath submits the form to the Web Service, it adds another namespace to the document marked as: dfs with the url http://schemas.microsoft.com/office/infopath/2003/dataFormSolution" and you need to add the namespace to your namespace manager.

nsManager .AddNamespace("dfs", "http://schemas.microsoft.com/office/infopath/2003/dataFormSolution");


Then to get value of certain field in the XmlDocument we need to know the XPath which leads directly to the desired XmlNode. We can get the XPath by the Copy XPath option, which can be found in the context menu of desired field in the "Data Sources" tab in your InfoPath client.

For example to get the "amount" XmlNode and later the string representing a number inside this node we can use the following code:

XmlNode nAmount = node.SelectSingleNode("/dfs:IPDocument/my:myFields/my:prodList/my:product/my:amount", nsManager);

int amount = Convert.ToInt32(nAmount.InnerText);
Now in the following part I will just show a simple example of method which would store some data to the Access database.

Preparing the Accesss database connection


To connect to Access database you can use the OLE DB Provider, exactly the .NET Framework OLE DB provider, in the namespace System.Data.OleDB. First you need to specify the connection string to your database. Because we are using web service it is good idea to store it in the Web.config file. Add the following to the Web.config file.




Later, already in the code of your Web Service you can prepare yourself a property which will provide you this connection string (just not to write too long lines of code).
public String ConStr
{
get { return ConfigurationManager.ConnectionStrings["myDB"].ConnectionString; }
}

The following is a simple implementation of a method which stores the data in the database. You can made this method part of your Web Service directly or build yourself some data access class.
public void SubmitToDataBase(String name, String price, String amount)
{
OleDbConnection con = new OleDbConnection(ConStr);

String cmd = "INSERT INTO products(name,price,amount)values(?,?,?)";
OleDbCommand command = new OleDbCommand(cmd, con);

OleDbParameter pName = new OleDbParameter();
pName.Value = name;
command.Parameters.Add(pName);

OleDbParameter pPrice = new OleDbParameter();
pPrice.Value = Convert.ToInt32(price);
command.Parameters.Add(pName);

OleDbParameter pAmount = new OleDbParameter();
pAmount.Value = Convert.ToInt32(amount);
command.Parameters.Add(pAmount);

con.Open();
command.ExecuteNonQuery();
con.Close();

}

There is nothing too interesting here if you are familiar with some other ADO classes. Just notice that I am using parametrized queries. The SQL command contains question marks, which are later when the actual OleDbCommand substituted with provided parameters.
That is all about the Web Service now you need to go back and configure the InfoPath form to connect to the Web Service.

Connecting the InfoPath form to the Web Service


OK now lets go back to the InfoPath form design. To submit the document to this web service you will have to add new data source select submit data -> to Web Service. Than localize you web service and find the method that, you just created and than finally in the Data Connection Wizard select submit Entire form.



Now just to give you a complete idea, here is the XML which is submitted to the web service. However if the document is saved as XML later (eg. in the SharePoint document library), the dfs namespace is not presented.

<dfs:IPDocument xmlns:dfs="http://schemas.microsoft.com/office/infopath/2003/dataFormSolution"><?mso-infoPathSolution solutionVersion="1.0.0.4" productVersion="12.0.0" PIVersion="1.0.0.0" href="file:///C:\Users\fajfr\AppData\Local\Microsoft\InfoPath\Designer2\23fae1f325544a92\manifest.xsf" ?><?mso-application progid="InfoPath.Document" versionProgid="InfoPath.Document.2"?>
<my:myFields xmlns:my="http://schemas.microsoft.com/office/infopath/2003/myXSD/2010-05-18T07:21:28" xml:lang="en-us">
<my:prodList>
<my:product>
<my:name />
<my:price xsi:nil="true" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" />
<my:amout xsi:nil="true" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" />
</my:product>
</my:prodList>
</my:myFields>
</dfs:IPDocument>

pondělí 3. května 2010

SharePoint and InfoPath - Error while processing the form and Schema validation error

Lately I came across these 2 following errors:

Error 1 - There has been an error while processing the form. There is an unclosed literal string

If you will come across this issue try one of following solutions(or combination):

1) You have some secondary data sources in the form which are not used. If you need them there (maybe they get use only on click of button...) than just drag and drop this data source to form and hide it.

2) Check the names of secondary data sources for special characters ( 'ěšřž...')

3) There is a KB fix which might help:

http://support.microsoft.com/kb/949752

Error 2 - Schema validation found non-data type errors

There is a solution from MS for this issue, when you are editing InfoPath form CODE:

http://blogs.msdn.com/infopath/archive/2006/11/28/the-xsi-nil-attribute.aspx

However in my case helped just setting the PreserveWhiteSpaces property to TRUE on XmlDocument:


XmlDocument lDoc = new XmlDocument();
...
lDoc.PreserveWhitespace = true;
lDoc.Save(myOutStream);

čtvrtek 11. března 2010

System.IO.PathTooLongException while opening InfoPath forms in SharePoint

When opening a InfoPath form in SharePoint, you may get int he ULS log the following exception:

Unhandled exception when rendering form System.IO.PathTooLongException:
The specified file or folder name is too long. The URL path for all files and folders must be 260 characters or less (and no more than 128 characters for any single file or folder name in the URL). Please type a shorter file or folder name.

Some general info about the exception can be found here.

It is caused by the MSO-INFOPATHSOLUTION directive in the head of the xml definition of the form. The attribute HREF of this directive can not exceed the size of 260 characters.

Our InfoPath forms where designed as InfoPath 2003 forms, and the HREF attribute was really long:





but if you strip it down, you can see that a simple link to the file is enough.


href="http://intranet/teamwebs/informatics/Evidence%20poadavk%20WF/Forms/template.xsn"


The forms designed in InfoPath 2007 do not generate the href attribute that long. Also note if you just want the forms to open in the client application(InfoPath), you can set this on the advanced settings of the Document Library, in which the forms are contained. But even there, if there would be link to the file outside of this library, or if you will access the direct link, SharePoint will always try to open it in Web Browser.

This forum post had led me to the solution:
http://www.k2underground.com/forums/p/8709/26302.aspx#26302