InfoPath Dev

 Hey everyone,

  I have a IP 2013 filler form, injected with Qdabra, integrated with SQL. It contains a nested repeating group structure. e.g.:

 IG - First Repeating Group

  Phase - Second Repeating group within the First

     Task - Third Repeating group within the second, within the first

        Org  - Fourth Repeating group within the third, within the second, within the first

I have a field in the myFields for a project entry. At this "Project" field I have a rule that first acquires my data from SQL then deletes and inserts the IG groups. At the IG group it inserts the Phases and at the Phase it inserts the Task and Task it inserts the Orgs.   All of this is a beautiful thing..... in preview.... It works great all my rows are inserted as I wanted and all the data is exactly as is should be within its correct groupings.

Now the problem.  I published my form into a SharePoint library and I created a quick URL link to the form template in excel. The "Project" parameter is passing through yet when it attempts to open the form and insert the groups, It gives me 6 errors, Operation Aborted. When the form opens we have almost all the data in the groups except for the last 3 tasks and last 3 orgs.  When I check the data view to see if the data coming from SQL was broken or missing, it's all there.  If I goto the SharePoint library and open a "New Document" then type in the project into the "Project" field, it queries and inserts all the rows properly just as it did in preview. 

 I have created many forms in the past passing a parameter into it and querying against SQL databases for the data. All have never performed in this manner when accessed through a URL. I am unsure as to what could cause it to fail when trying to access the form through a URL.

Quick reminder: IP2013 Filler Form. SP2010 library set to open in client and not in browser.

Any help is appreciated and I will happily answer any questions I may not have covered.  

What version of qRules are you using? In later versions there is an execution history group in the Qdabra Rules data source, you could drag that onto your form to at least see what commands are being executed and if there are any errors.

 5.1.4913 June 2013

Hey Hilary,

 I just spoke with my boss and he updated me on our account info with Qdabra. He asked that I call you and see if you have any insight to our current form issue. If you are not available for support/discussion, we ask if you could look at our form template? I can upload it here if you wish. 

 I have done some more troubleshooting and when I disable the insert Org rows rule I then get no errors and all my IG, Phase and Task groups insert properly. I am currently going field by field to assess what exactly is breaking it when accessed through a URL.  

Please let me know if you are available for discussion or if you have any advice that may help. Thank you. 

Hi CCBSFranco,

You could use qRules to do this but a better practice may be to use our DBXL Web service suite. Then the form wouldn't have to have code and you could use the same SQL logic to submit from a web page.

Please email Support (at) Qdabra (dot) com and ask Heidi to schedule something for Friday or next week.

Thanks!

Hi Patrick,

 Thanks for your reply. I don't believe DBXL would help me in this scenario as we need it to work in Filler and not browser based. My problem isn't the SQL side of things as I can easily pull all the data I need and submit back to all 3 three tables with no problem at all.  Everything works in preview and it works when I open a "New Document" in the SharePoint library and enter the project manually. 

It only fails to insert when I attempt to open the form through a URL to the template in the SharePoint or Fileserver and pass the project via parameter.   Since my original post I have disabled the counter at the Org repeating group and placed the formula in the default value or my org_row field in the Org repeating group. Once I did this all the rows insert correctly through the URL but now my data isn't being copied across correctly. Some come across while others fail to copy from the secondary data source. Ideally of course this wouldn't be a problem if the counter was setting the value of the org_row for me at the Org repeating group. 

I know that the nested repeating groups can be rather complex at times. But I have another form I designed using the same structure and it works without a problem at all. 

I will schedule a meeting with Heidi as soon as I can. Thank you again for the information and if you have any advice please don't hesitate to let me know.