Submit To Sharepoint - Parent\Child List Relationship - InfoPath Dev
in

InfoPath Dev

Submit To Sharepoint - Parent\Child List Relationship

Last post 01-05-2012 04:36 PM by Hilary Stoupa. 3 replies.
Page 1 of 1 (4 items)
Sort Posts: Previous Next
  • 01-05-2012 02:14 PM

    Submit To Sharepoint - Parent\Child List Relationship

    Hi,

    My first post here- evaluating the QRules tool for use on a big project. What I need to be able to do is to submit different repeating tables

    to different lists- and have them connected to entries in the main library submit. As an example, an Expense Report form that would have basic

    data such as expense date, person name, project name, etc. Then a different list that would show the 'items' submitted for that report. I see how

    to accomplish this with qrules, but there is no "hook" to the basic data that get submitted to the library. I would need to be able to have

    the list items submitted with an identifier back the the form data- such as "MainEntryID" or the like. Then I could use SSIS to build a connected DW

    from the list/library data. Does that make sense?

    If this is relatively easy to accomplish, consider the purchase done! :)

    Thanks for the help!

    Rick 

  • 01-05-2012 03:29 PM In reply to

    Re: Submit To Sharepoint - Parent\Child List Relationship

    Hi:

    This is easily done with SubmitToSharePoint list - you end up having to manually add to the mapping (or in the mapping tool, manually creating) the relative XPath back to that higher level node. I can help you with that - just attach your mapping file and a picture of your main data source to a reply (under the options tab - you can put them in a zip file) and I can show you what to do.

    Hilary Stoupa

  • 01-05-2012 03:46 PM In reply to

    Re: Submit To Sharepoint - Parent\Child List Relationship

    Hi Hilary,

    Thanks for the quick response. I think I know where you are headed. Once you try to add the other fields in the mapping tool, the red text

    tells you to add the mappings manually. I think I understand that..

    what I need is not to send ALL of the form data to the list- only the repeating table items, and an identifier to the main library submit. In the repeating

    table submit you should end up with an item ID, and a corresponding FormID. the form ID would duplicate, of course, depending on the number of repeating

    entries. I tried to map the "ID" field from the main data node, but since the form has yet to be submitted, no number exists and I get an error on the

    'id' part of the command.

    I could send you the form and mapping info- but I didn't want to create the big project until I knew how to do it :/

     

  • 01-05-2012 04:36 PM In reply to

    Re: Submit To Sharepoint - Parent\Child List Relationship

    HammerC3:

    I tried to map the "ID" field from the main data node, but since the form has yet to be submitted, no number exists and I get an error on the

    'id' part of the command.

    I'm sorry, I don't understand what that means. The /id parameter for the command should be the field you'd like the new list item's id returned to. So, that would be a field inside the repeating group. Don't map it. The /id parameter would be the relative path to that field, and when your command runs, it will populate that with the list item ID for the new list item you created.

    The main data node "ID" I'm guessing is a field you are setting to a specific value when the form itself is submitted? If so, you may need to submit to your library twice - submit once and get your value for that main "ID" node, then run your SubmitToSharePointList commands (which will populate the id's for the list items) and then, now that you have all the data, re-submit to your form library, overwriting your initial submit.

    If you need a hand with your test form, just attach it to a reply. Oh, and if you are getting an error in the Error node when you run a command, please include that info as well.

    Hilary Stoupa

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