Controls

Re: "Insert item" command does not respect repeating table filter

memeticdrool — Thu, 18 Jul 2013 19:43:06 GMT

Thanks, Hilary! That works great! I appreciate the assist!

Simon

Re: "Insert item" command does not respect repeating table filter

Hilary Stoupa — Thu, 18 Jul 2013 19:23:37 GMT

Thanks - a mockup made it easier. I don't use filters on repeating tables usually - I don't like having to hunt for them later - I use conditional formatting. What I did was put your commitments inside a control bound to services, added conditional formatting to that, and it appears to work correctly now. Save the attached file locally, right click and select design to preview.

Re: "Insert item" command does not respect repeating table filter

memeticdrool — Thu, 18 Jul 2013 19:02:35 GMT

Attached is a mock-up of the form, Hilary. Thanks for taking a look.

Re: "Insert item" command does not respect repeating table filter

memeticdrool — Thu, 18 Jul 2013 18:27:43 GMT

Sure. I'm having a little difficulty connecting to my work computer at the moment and will have to scrub the form a bit. It is built with a secondary datasource connecting to a SharePoint list for the list of services that won't be accessible. So, I will build a quick and dirty simplified form that reproduces the problem and post that.

Re: "Insert item" command does not respect repeating table filter

Hilary Stoupa — Thu, 18 Jul 2013 17:34:07 GMT

Mind sharing your form? Under the Options tab... If I look at the template, I'll be able to understand your post a little better. :)

Re: "Insert item" command does not respect repeating table filter

memeticdrool — Thu, 18 Jul 2013 17:16:00 GMT

Fixed the formatting of original message. Simon

"Insert item" command does not respect repeating table filter

memeticdrool — Thu, 18 Jul 2013 16:54:51 GMT

I am working on a codeless solution in InfoPath 2010 (qRules is not an option) and I have a nested XML structure like the following:

root

services (group)

service (repeating group)

serviceId
serviceTitle
commitments (group)

commitment (repeating group)

commitmentTitle

...
elements (group)

serviceId

...etc.

I am displaying the commitment nodes using a filtered repeating table. The user selects the serviceTitle (value: serviceId) from a drop down list box bound to root/elements/serviceId, and the repeating table bound to the root/services/service/commitments/commitment filters the commitments displayed to just the select service with the following filter:

../../my:serviceId = ../../../../my:elements/my:serviceId

What I can't figure out is behavior that occurs when I select the 2nd service in the document (any service that is not the first) and start adding commitment records via the repeating table. If I insert records using the Insert Before and Insert After commands, the new commitment is created with the filtered service node. However, if I use the "Insert item" command at the bottom of the repeating table, InfoPath appends the new commitment element to the first service element. The new commitment displays on the filtered list, but then when I refresh the filter or switch services, the new record displays when the first service is selected.

The "Insert item" hyperlink is very useful because it is the next control in the tab order. So a user doing data entry can add records without mouse clicks, whereas the Insert before and after commands require mouse clicks. I have done a couple days worth of experimenting and web research and can provide more details of the behavior, if needed. However, I'm at the point where I'm thinking perhaps this is a well understood behavior of InfoPath. So, I'm wondering if someone on this forum can explain the fundamental behavior of "Insert item" and why it makes sense that the new commitment node is appended to the wrong service node?

Best, Simon