InfoPath Dev

It appears that it is not possible to filter a repeating table in the browser in Infopath 2010.  Is this a correct observation?

If so, what is the workaround. 

I just created a new IP 2010 browser form, added a repeating table and could add a filter to it in design mode (no errors in design checker). Can you provide more information about what you are experiencing?

Yes, in design mode it works great.  But once it's published it doesn't filter. 

What are the postback settings on the controls that may affect the filter? Could it be postback? Of course, it could just be that filters don't actually work in the browser -- I found this thread that suggests you aren't the only user to have some trouble, but it seems to be referring to filters on dropdowns inside tables, not tables themselves....

Let me mess with the postback settings.  I'll postback with my findings.

Nope, didn't change anything. 

 Maybe you can suggest another method to my madness . . .

I have a gear list broken down into about 7 categories (i mentioned this in the other thread about copytable taking a long time with a large table).  The idea of the repeating sections was to break the gear list down into categories when the user copies it over, that's why i set query fields, queried the list, then copied over.  That worked fine.  But it doesn't make any difference if the filter doesn't work.  Each section is showing every category regardless of the filter. 

Patrick had suggested using owwsvr to filter down child dropdowns, but that won't work in my case.  The users need to be able to tab through the table, and add the amount of gear they need ordered. 

I can't think of another way to approach this.  If the filter would work in the browser, it would be ideal.  I guess I could copy over everything in the table, but the users are only gonna order gear of a certain category. 

I am still unable to understand this scenario. I don't understand the need to copy all the options into the form's main data source? Which is, I guess what I'm assuming you are doing. Correct me if I'm mistaken.

To me it sounds liike you have categorized stuff you want users to be able to choose from -- they choose a category, then they choose some stuff based on the category. What I don't get is why you'd copy all the categories and all the stuff out of the secondary data source they are coming from? Perhaps you can attach a copy of your form and that will help me understand?

Well, I want to copy everything of a certain category, and then they tab through it like a checklist.  I want them to see every piece of gear of a certain category, so they can go through and order what they need (by entering a number in a "need" column.  I wanted to have a repeating section with the table, so that when a user needs more gear of a different category, it will be segregated from the other stuff.  That way, when the person that is going to pull this gear gets this form, it will be broken down into categories (i plan on having a delete command on submit to delete all the items that have a "0" in "need" column. 

 I use a category selector drop down list box in the repeating section to set the list query fields, and then only copy over that category into the repeating table.  Then if they need to add another category, they add another section and repeat.  But it sounds like copytable is not going to work this way. 

I attached the form.  I'm open to suggestions. 

BTW, ignore the "Get Gear" button.  I was using that to copy over the entire list.  The query and copy table rule is set on the category selector. 

Okay. The part I'd not seen in your other descriptions was this:

shniggens:

i plan on having a delete command on submit to delete all the items that have a "0" in "need" column

I just kept imagining this massive XML where you had all this data stored and thinking "ick".

I think you should try using Insert, since it will work with nested repeats, and the documentation I linked to in your other thread.

I'll give it whirl.  But to be honest, I've seen the doc, and I can think is "ick".

Y'know, when I think about it (and look over that insert/count doc), maybe I can get away with just a repeating table.  And as users choose gear category it appends the table.  I can still use the error condition if they try to pick a category that was previously entered.  It would be nice to have headings at each gear category change in the table, though.