Querying an SharePoint InfoPath 2010 Forms Document Library by Repeating Table Field - InfoPath Dev
in

InfoPath Dev

Use our Google Custom Search for best site search results.

Querying an SharePoint InfoPath 2010 Forms Document Library by Repeating Table Field

Last post 04-18-2018 08:19 AM by Hilary Stoupa. 1 replies.
Page 1 of 1 (2 items)
Sort Posts: Previous Next
  • 04-16-2018 06:43 AM

    Querying an SharePoint InfoPath 2010 Forms Document Library by Repeating Table Field

    Hi all, I was wondering if it would be possible to query a SharePoint 2010 InfoPath form library by a value in a repeating table. My application is as follows - we have one group of workers submitting InfoPath records, and one of the fields being submitted (basically a list of production orders) is an InfoPath repeating table. We also have another group of workers submitting a different form, where one of the (singular) fields is a production order. It would be useful to query the 1st form library's repeating table by the 2nd form library's single value, in order to return other values that were contained in the 1st form library's matched record. I've attempted to do this, but so far have been unsuccessful. I've set lookup values and queried for data before using singular fields, but am unable to get it to work for a repeating table. Would something like this be possible? Thanks for your time, and any and all help is appreciated. Thanks, Jeremy
  • 04-18-2018 08:19 AM In reply to

    Re: Querying an SharePoint InfoPath 2010 Forms Document Library by Repeating Table Field

     Unfortunately, there isn't an easy out of the box way to do this - I believe if you promote the data as merged, it won't be available in your query fields in your secondary data connection. If the merged data was instead submitted separately to a SharePoint list (using code, qRules or CAML) you could then query that list - same if you submitted it to SQL.

    Hilary Stoupa

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