I have an InfoPath 2010 form template where two views have a repeating table. The repeating table has formatting rules applied so that it will hide if another field is at its default value.

I've tried enclosing the repeating table in a section and hiding the section, but that also fails, though the technique works fine for other controls on the same form.

Unfortunately, the rules do not seem to work. The repeating table is always visible. Has anyone else ever encountered this? If so, is there a fix to make the rules work?


I don't have enough reputation on this site to post screen shots from InfoPath. But I'll attempt some text graphics:

This is the field/group set I pulled onto the template. InfoPath constructed a section holding a repeating table. I've edited the table contents to place the Attach_File_Panel section (with the File's file attachment control) and the Attachment URL into the first detail cell of the table. The AttachmentTitle has its textbox placed into the second detail cell of the table. The FileID is hidden and extra columns removed from the table.

Attachments (group)
└─ Attachment (group)
   ├─ Attach_File_Panel (group)
   │  └─ File (field - base64Binary)
   ├─ AttachmentURL (field - anyURI)
   ├─ AttachmentTitle (field - string)
   └─ FileID (field - integer)

I placed two formatting rules on the "Attachments" section and the same rules on the "Attachment" Repeating Table. The first rule checks the value of another field "SIPP" for a default value. The second rule tests whether the SIPP field is blank. In either case the section or repeating table should be hidden. (I check the "Hide this control" checkbox for the rule.)

The SIPP field's default value is

;#1;#tbExport Controlled Information (ECI);#;#00000000-0000-0000-0000-000000000000;#;#1;#tbThird Party Proprietary Information;#;#00000000-0000-0000-0000-000000000000;#;#1;#tbOrganizational Conflict of Interest (OCI);#;#00000000-0000-0000-0000-000000000000;#;#2;#Other;#;#00000000-0000-0000-0000-000000000000;#;#;#

I'm wondering if the complex value is messing up InfoPath's x-path rule engine.


Problem solved: The issue is that the value I was pasting into the rule dialog box was too long and InfoPath silently truncated the value. Switching from a simple field comparison to "The expression ..." and replacing the truncated value with the full value fixed the problem.

In the future, if pasting (or typing) long strings into an InfoPath rule, using "The expression" allows for much longer strings than choosing a field, a comparison operation, and a value.

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.