InfoPath Dev

The today function just returns the date. You can test these things with calculated values. The syntax will be different for a condition - I didn't know that's what you were doing, and thought you'd be pasting this into the function editor for a rule. For a condition, change the first dropdown to "the expression" and use: ...

Oh, I'd probably use a translate formula and just turn the date into numbers: translate(today(), "-", "") > 20201204

Right - so that's the trouble with a repeating structure. But you are constrained by the limits of SharePoint - you can't have as many columns as they want. If you used a form that submits to SQL, you'd be ok - Or, I imagine some reporting tools could read the XML file data into a report that could be exported. Do you use on-prem or ...

Here's a sample form I had in my files - right click the linked file, save locally. Right click the saved file and select design, then you can preview. In this sample there is only one "answer" field, using option buttons, but you could easily extend that to add all 7 of your fields. I use default data to include rows by default, and ...

:) I think you won't be able to use a list form for this, I'm afraid. Have you considered using a library form? And you'll probably want to use a repeating structure (which means you won't have your data flat in a list for reporting either).

Yeah - this is just the nature of a multi-select. The control is bound to a repeating field. When you make a selection in the control, it adds another instance of the repeating field and sets the value to the selected value. When you de-select an option in the control, the associated node is deleted. Because InfoPath has no rule-based way to add ...

So - just opening them should update the field. You shouldn't even have to click Save. As I mentioned in your other thread, if you could open the library in File Explorer and copy the files out, that would update them. I wonder if you copied the files out via PowerShell if that would do the same thing? It may be worth a try rather than having ...

Do you have the same issue if you set a variable to the value you'd like in the email body? Just thinking in terms of a work-around - i.e., try setting a variable to the current item value you want and using that in the email body.....Do the other steps have values from the same field you are using in the email body that causes the issue?

Do you get any additional details in the error message on this? This is published to an on-prem SharePoint server, correct? When you say you have several steps that are working fine - are these also sending emails with values from the current item in the body? Do you have access to the SharePoint ULS logs, or would your SharePoint admin be willing ...

Doc library or form library? How many files? I don't recall if you see that if the library is over the list threshold and try to open in explorer....