Cascading Repeating Sections - InfoPath Dev
in

InfoPath Dev

Cascading Repeating Sections

Last post 02-06-2007 04:23 PM by Greg Collins. 5 replies.
Page 1 of 1 (6 items)
Sort Posts: Previous Next
  • 01-26-2007 01:58 PM

    • dpsavy
    • Not Ranked
    • Joined on 01-26-2007
    • USA
    • Posts 13

    Cascading Repeating Sections

    Hello All,

    I have a secondary datasource (access database) that I am using to query data from tables and populate the data into a repeating section to create a item type layout like so:
    <repeating section>
    <row 1>
    label field 1: Label Field 2:
    [Field 1] [Field 2]
    Label Field 3: [Field 3]
    </row>
    <row 2>
    ...
    </row 2>
    </repeating section>
    All is great there. What I need to do though is add a few fields(Date and Signature) from my main data source directly underneath Field 3 for each row. I got it to work by inserting the main data source section inside the repeating secondary data source section but once I enter a value in one of the main data source controls it copies it to all of them. Any ideas. Thanks.
  • 01-26-2007 10:03 PM In reply to

    Re: Cascading Repeating Sections

    Hi Dpsavy and welcome to our forum!
    I'm guessing that you essentially have a relational structure in your form and you want to somehow tie Date and Signature to each of the rows returned from Access. You will need a reference id to map them together. We have done this several times before and I don't remember the exact details but it's tricky and may require some XSL hacks. I will ask Greg or Agni to respond since I think they may remember how to do this. If not, please ping me in e-mail and I'll dig through some of our forms.
    Patrick Halstead
    Project Manager at Qdabra
  • 01-27-2007 01:17 PM In reply to

    • dpsavy
    • Not Ranked
    • Joined on 01-26-2007
    • USA
    • Posts 13

    Re: Cascading Repeating Sections

    Hello Patrick and thank you for the quick response. Do you think it would make more since to filter the secondary data and then copy the group into a group in the main data source? That would put the entire data in one repeating section which I think would solve my problem. Can#%92t help but feel that is redundant though, especially since the user doesn't need to manipulate the data just read it and sign off on it. What do you think?
  • 01-29-2007 02:34 PM In reply to

    Re: Cascading Repeating Sections

    Your main data source signature section should also be repeating. Then you need to have some key value that maps between your 2DS database row and your main DOM signature row. This will allow you to filter to only show the correct signature fields.

    It will also require that when you first open the form (onload) that you populate the signature rows (i.e. make sure there is a 1-to-1 match of rows and key values).
  • 02-01-2007 08:06 AM In reply to

    • dpsavy
    • Not Ranked
    • Joined on 01-26-2007
    • USA
    • Posts 13

    Re: Cascading Repeating Sections

    Hello Greg,

    Sounds great. I have set a key field that populate the signature section every time a selection is made in a DDL. Then I set the conditonal formating for the signature section to "hide this control" if the keys don't match. However, this ends up hiding every field. Where am I going wrong? Thanks again.

    Here is the layout:
    <2DS Repeating section>
    Label1: Label2:
    [Field1] [Field2]
    Label3: [Field3]
    <PDS Signature Repeating Section>
    Label1: [Field1]
    </PDS Signature Repeating Section>
    </2DS Repeating section>
  • 02-06-2007 04:23 PM In reply to

    Re: Cascading Repeating Sections

    disable the conditional formatting for a time and make both key fields visible in the view. Then do some testing to verify that you are getting the values you are expecting to get in each of the key fields. If the key field values are correct, then double-check the conditional formatting.

    If that still doesn't work, let me know.
Page 1 of 1 (6 items)
Copyright © 2003-2019 Qdabra Software. All rights reserved.
View our Terms of Use.