Controls

Re: Hide question in first repeating section

klc2009 — Wed, 15 Feb 2012 19:18:16 GMT

Nevermind, I found it. Thank you very much for your help!!!

Re: Hide question in first repeating section

klc2009 — Wed, 15 Feb 2012 19:16:42 GMT

That is the heart of the issue, yes. :) I apologize for my long-winded question but I find if I don't explain I get answers to a question I didn't mean to ask.

I am not a frequent user of this forum so again I apologize, but I do not see any attachments. What am I missing?

Re: Hide question in first repeating section

Hilary Stoupa — Wed, 15 Feb 2012 19:02:33 GMT

I should add, if this is a Filler (i.e., not a browser form) you could also use the position() function.

Re: Hide question in first repeating section

Hilary Stoupa — Wed, 15 Feb 2012 18:23:46 GMT

Well, at it's simplest, it sounds like you want to hide some stuff in the first instance of your repeating question. Is that the heart of the issue?

If so, you can put those controls in a section, and conditionally format the section to hide if this is the first instance of the repeating section.

One way to do that would be to count the preceding-siblings of your repeating node and hide the section if there are 0. I've attached a simple sample of this concept.

Hide question in first repeating section

klc2009 — Wed, 15 Feb 2012 17:46:52 GMT

I have a repeating section that contains a number of controls. In some cases, I would like to allow the form completer to refer me back to a previous section so that they don't have to enter the same data several times.

For instance, one part of the repeating section asks them to define their escalation tree, which is collected in a repeating table. There is a likelihood that the same escalation tree will apply to subsequent repeating sections. So I have checkbox control with the question "Use previously defined tree". If checked, the repeating table that collects the escalation tree fields would be hidden.

I don't want this question to be displayed in the initial repeating section however because at that point there is not a previously defined escalation tree.

How can I make this work?