-
That would depend on how your data source is structured. Could you attach a screenshot of enough to give us an idea of how you've organized it?
-
I think you have it almost right here:
Hide when Organization does not equal BREC
In the left dropdown box, pick Select field or group, select Organization and then from the dropdown at the bottom of that selection dialog, pick All instances of so you wind up with:
Hide when All instances of Organization are not equal to BREC
I believe that ...
-
Depending on your data source is organized, there may be a simpler way, but generally for disparate fields, the way to count how many have a certain value is:count((firstField | secondField | ... | lastField)[. = 'pass'])
-
It appears that that particular format is indeed not available in the control properties dialog. If thi is a filler form, you can use the formatDate() function in a Calculated Value box, though this doesn't seem to work in browser forms:msxsl:format-date(my:field2, "ddd, d MMM yyyy")If you do use qRules' FormatDate and ...
-
In the repeating table case, where is the datepicker that has the rules on it located? If it's in the repeating table, you should be able to use an ordinary Set a field's value rule for step 3, if it's not in the repeating table, what are your criteria for deciding which row gets set?
Is there a particular reason you are ...
-
Don't worry about it. There's so much available in InfoPath that it's easy to overlook some things. I don't think I noticed that particular button until a while after I had started using it. :-)
-
Now that you mention it, our documentation doesn't seem to have a section that explains the command syntax in detail. It certainly is something we should have in our user guide. We will take a note to improve it in the near future.
-
This probably has to do with the postback settings on the control. Could you open the control's property dialog and ensure that it is set to always postback?
-
It appears that you're missing spaces before every slash.
-
I'm not sure that default value formulas that use userName() are able to detect that the formula value has changed when someone opens the form. As an alternative, how about adding a Form Load rule that sets the field to the value of userName()? That should definitely do what you are looking to do.