InfoPath Dev

Hi, and thanks for your interest in qRules. qRules will allow you to map your form data into a SharePoint list. If you want the form to be stored in a form library as well, simply add a form library submit to your form. Let me know if you need any links to qRules documentation and tutorials.

Thanks for checking. When thinking about the site, those are the two things we typically look for: the user being a Site Collection Admin and the Sandbox service enabled. As far as the form itself, please check that the form template is an InfoPath 2013 browser form, and that it is injected with the 2013 Browser option in the qRules ...

Could you check to see if you are a site collection admin?

Thank you for reporting this. qRules v6.1 will be updated to fix this issue.

Here is a blog post that explains the options available to map data into SharePoint lists: http://www.infopathdev.com/blogs/alyssa/archive/2013/07/23/how-do-i-map-infopath-form-data-to-a-sharepoint-list.aspx Hope this helps.

I know we've resolved this via email, but to anyone interested. The issue was in the nesting of the parent-child tables in the Database Mapping tab. Correcting the relationships seems to have resolved this. The indentation in the mapping is the key, since it shows the relationship between the tables.

Hi Barry, When using qRules' SubmitToSharePointList command, the presence or absence of the list ID is what determines if the list item is overwritten or a new one created. So this means: if your form has the List ID (and it's included in the mapping file), then the command looks for that list ID and overwrites it. If there's no ...

Hi Rommel, Unfortunately the command does not support this feature. Sorry for the bad news! I've added this as a feature request for a future version. Thanks.

I think there are some options for DBXL if you don't want the form(s) to submit to the web service. In DBXL v2.8, the forms submit directly to the form library, and the DBXL Event Receiver maps the data to DBXL. Then, DBXL can map the data to SQL for reporting. The Deployment Guide (and other DBXL v2.8 documents) can be found here for more ...