InfoPath Dev

pardon my first time using the tool, reading the documentation explicitly, where do you get the xml file for import forms?

 

	Solution Version: 1.0.0.663
Copyright © 2009 Qdabra Software. All rights reserved. Qdabra and the Qdabra logo are trademarks of Autonomy Systems LLC. www.qdabra.com

 

1) completed defined mapping flawlessly. Source xsn, target sharepoint site url, get sharepoint list, extract shemas, mapped only one field, no mapping of repeating field data, then import forms. Click here to attach file, the xml file. where is this generated. I mistakenly tried creating an XML file from the save as qrules mapping but at the end of the documntation it said NOT TO if you are using qrules 2.0. I am using 2.3. So where does the xml file come from? thanks.

Hello,

The first question to clarify is your goal in using the InfoPath to SharePoint List tool. It can be used as a standalone tool to import xml into SharePoint, or it can be used with qRules to create InfoPath to SharePoint list mappings (here's another blog post on this)

I have added links above; hopefully these explain the dual nature of the tool. You mention that you are following documentation. Can you clarify which one?

Thanks!

Thanks for the additional info.

One of the tools requirements is that you have your own (pre-existing) xml files (which contain the data) that you wish to transfer over to SharePoint. I'm sorry if the documentation isn't clear on this point.

Hi!

I've read through this thread, and I'm pretty confused. I'd like to help you though, so I need to ask some questions first so that I can understand what you are trying to do.

First, so you know, the InfoPath To SharePoint List tool has 2 distinct and separate purposes. One is to take existing XML files (the saved files after a person fills out an InfoPath template, or XSN) and upload specific data to a SharePoint list. The other possible use would be to create what we call a mapping file for use with qRules SubmitToSharePointList command....Which leads us to my questions:

1. What are you trying to do -- import existing XML files to a SharePoint list? Or set up a form template to use qRules SubmitToSharePointList command?
2. If you are trying to import existing XML files to a SharePoint list, we assume that those XML files already exist someplace (maybe submitted to a SharePoint form library?). You also do not need to create a mapping file if you intend to import existing -- so you don't need to use the button that saves the qRules mapping
3. If you are trying to use qRules SubmitToSharePointList command, you don't need to do anything with the Import tab -- once you generate your mapping file, you can close the InfoPath To SharePoint List tool, and proceed working on the XSN where you wish to add the command.

So, if you can get me a bit more info on what, precisely, you are trying to accomplish, I should be able to help you with some detailed steps. Thanks!

as well as I am since I am completely new to your software and I am digligently following the directions in the documentation.

 1) i have infopath form that I want to associate with a custom list so that when a person goes new document ( just like a forms libray ), a browseable infopath form pops up. The person inputs the data and it populates the custom list.

I was told that I had to use the InfoPath To SharePoint List tool. Is that correct?

Well, if you are using qRules to submit items to a SharePoint list, you will need to use the InfoPath To SharePoint List tool to create the mapping file for the submit in your form (here's a blog post of mine with more info on setting up the qRules SubmitToSharePointList command).

However, I'm thinking that may not be what you want to do -- since the form template will not be available from the "New Item" menu in the list.... unless you are using SharePoint 2010? With SharePoint 2010, there is some built in functionality that may do what you want.

If I am intepreting your post correctly and I am using Moss 2007, you are saying that I cannot have and infopath form come up when a person selects "new item" in the custom list webpart.

And you are saying that I have to use Qrules first and then follow the rest of the steps in your blog.

If this is so, and the only way to get an infopath form into the custom list is to save it into the custom list. How to deliver the infopath form to the thousands of people that will have to submit it?

When using the forms list, you choose "new document" and the infopath form comes up. you fill it in and then when you select submit the data and the form goes into the form webpart.

When using the custom list webpart, where does a person who does not have infopath get ahold of the form to use? I am confused.

Hi Doug,

Perhaps I can help out here.

Documents in SharePoint are associated with a document library - so when you publish a form template in a document library there is a document to fill out and the user creates a form.

In a SharePoint list there is no "document" but an item, and the user can edit the item.

With qRules you can submit a row in a repeating (or non repeating) section in InfoPath to a sharepoint list and it will create an item there but not a document.  You can configure your form though to save to a document library AND submit to a sharepoint list at the same time.  The user would then open up that document to edit rather than the sharepoint list item (although you can configure your InfoPath form to get updates from a sharepoint list item of that item is updated outside of InfoPath).

So users in your case would interact with the document library and then reporting would be done off the SharePoint list items.

You can have different web parts on a page in which case you could have the document library web part on a page along with the SharePoint list web part and filter for the current user, this way users would see all their documents and sharepoint list items - althoug that my confuse some of hte users.

Hope that helps

Ted

Hi, yes, you can do it without qRules - you would need to write your own code to do it thougth.

We created qRules so that you don't have to write and maintain your own code.