SubmitToSharePointList problem - InfoPath Dev
in

InfoPath Dev

SubmitToSharePointList problem

Last post 02-22-2013 11:19 AM by ErnestoM. 3 replies.
Page 1 of 1 (4 items)
Sort Posts: Previous Next
  • 02-22-2013 08:27 AM

    SubmitToSharePointList problem

    Hi all, I have a IP 2007 administrator approved browser form that I want to use to populate a SharePoint 2007 document library. The problem I have is that when I want to do the mapping, I don't see my library. I have tried to use a form library instead but I still cannot see it. Only when I use a custom list I can do the mapping. The problem with using a custom list is that when I try to add the form as a content type, I cannot see any of my infopath content types. Can anybody please tell me what I'm doing wrong? Thanks in advance, Gus
  • 02-22-2013 09:42 AM In reply to

    Re: SubmitToSharePointList problem

    Hi Gus,

    The command SubmitToSharePointList submits only to SharePoint lists.

    SharePoint document libraries are used for storing documents, while SharePoint form libraries are used for storing xml forms.

    SharePoint allows you to create an InfoPath form (a SharePoint list form), bound to a specific list, and you can send data into that list via that form. The schema for that type of form is locked to the list columns.

    What qRules allows you to do is send data to a SharePoint list, but without being bound by that list. For example, your form can submit (itself) to a Form Library but also map some data to a SharePoint list.

    You can't publish a "regular" InfoPath form to a SharePoint list, only to a form library.

    What's your scenario and what would you like to accomplish? Maybe we can provide some advice on how to best achieve your goal.

    Thanks.

    Ernesto Machado
    Qdabra® Software/ InfoPathDev.com
    The InfoPath Experts – Streamline data gathering to turn process into knowledge.™


  • 02-22-2013 11:03 AM In reply to

    Re: SubmitToSharePointList problem

    Hi Ernesto, What I'm trying to accomplish is the following: I created an IP 2007 and I want to promote all fields to store them in a SharePoint list for reporting purposes. I want the users to be able to fill new forms (browser) right from the SP list. I have done it before by publishing the form directly to a SP list but in this case I added qRules to filter a cascading drop down so I must publish the form as admin approved. Please advise, Gus
  • 02-22-2013 11:19 AM In reply to

    Re: SubmitToSharePointList problem

    Thanks Gus.

    The form you created in the past was most likely a SharePoint List form. That's the form with a locked schema, which maps its data directly into the list. That is, the user goes to the list, clicks Add item, fills out the form, and the data entered creates a new list item.

    qRules is not meant to be used in SharePoint List forms. (Actually, no code can be used in these forms.)

    What you've most likely created now is not a SharePoint List form, but a regular, blank, InfoPath form template. This type of form template can be admin deployed or can be published directly to a form library (on ShP 2010), but cannot be published to a SharePoint list.

    You could do the following:

    1. Admin deploy the form.

    2. Provide the link to the form to the users.

    3. Users access that URL to access the form and fill it out.

    4. The form uses SubmitToSharePointList to map data to the SharePoint List.

    Hope this helps. In addition, Hilary has a fantastic set of blog posts walking thru the possible scenarios, available here:

    http://www.infopathdev.com/blogs/hilary/archive/2012/07/05/qrules-refreshsharepointlistitems-walkthrough-for-v4-2.aspx

    The free qRules training is also available, here:

    http://www.infopathdev.com/files/folders/qrulestraining/entry78317.aspx

    Good luck!

    Ernesto Machado
    Qdabra® Software/ InfoPathDev.com
    The InfoPath Experts – Streamline data gathering to turn process into knowledge.™


Page 1 of 1 (4 items)
Copyright © 2003-2019 Qdabra Software. All rights reserved.
View our Terms of Use.