InfoPath Dev

I have a calculated field that determines if a certain whole number is even, by dividing the number by two, then subtracting the rounded version of the result by a precise version of it. If I do this in a calculated column it comes out great; 0.5 if an odd number, 0 if an even number. This is not for display, however. I want another rule to ...

Bringing this thread back from the dead yet again! :) Can you use constants in a rule-based expression? I've tried this: (round(../my:TimesChangedResponsibility / "2")) - (. = ../my:TimesChangedResponsibility / "2") = "0" and several variations of it in the attempt of creating a "true" or ...

Update: I found this only applies to Chrome. It works in IE, but as my company is still on Win7 (and IE11 is ancient) everyone uses Chrome!

I have an Infopath form with several large plain text boxes for adding info. There is no need for formatting, which is why I selected "plain text," yet despite configuring it as "Multi-line" it does NOT automatically drop down to the next line when reaching the border of the box. Instead the text runs on and on the same line ...

Well, it appears to be a "kinda" solution. I didn't think about this but it seems the form needs to be open for a calculated field to, uh, calculate (makes sense). All list entries made after I added the field work fine, but the older ones do not. I supposes I could open them and save them, but there are tens of thousands, so I'd ...

Dang, that's a good idea and I hadn't thought of that! I use Views all the time, but making one with no ability to switch to it sounds like a great idea. Giving it a try now.

Is it possible to create a calculated field that is not bound to a text box but will still function? I have a need to do some complex math using a bunch of number entries in an InfoPath form, but the results are only used in a specific SharePoint list View. I do not need it to show in the form itself. My first thought was just adding a ...

Got it! I re-uploaded the form and it fixed that - but then I was getting a validation error even if I filled in the field, but that turned out to be a stupid typo. At any rate, I had never played with validation rules before, so thank you! It fixed my issue.

Hmm, seems simple enough, but I am missing something. I added the rule "validation" and the condition was the same as those which make that section visible, but I can still save and close the form with that field blank and I get no error.

Looking for ideas on this one. I have a form that has 8 "potential" sections, each with a field that needs to be mandatory, but only if that section is visible. For any given submission between 1 and 8 of the fields may be visible, with the remainder hidden. This is the normal use of the form, so obviously just marking the field ...