-
this problem occurs only when you have not populate any of the values (TO, CC, BCC). you need atleast one field to be populated
-
add a text box say concat values and in the set its default value to eval(eval( repeatingsectiongroup,`concat("my:dropdownfield",";")`),"..")
-
open your infopath template go to tools -> form option -> security and trust and set the security level to Domain and publish again.
-
Thanks Hilary. I Got it working already. I hope you guys don't get tired helping us newbies. :)
-
Ah, I see now. The issue is that using built in InfoPath functionality, you can't filter the target of a rule.
You have several options. You can use qRules to set a filtered field's value. You can manually modify the manifest file. You can use the conditional double eval method. I suppose, also you could use code.
-
Can you share your template? There is a spot under the Options tab where you can attach a file. I can try publishing to one of my test SharePoint sites and see if I get the same error -- we'd at least know if it was the form the SharePoint set up....
-
-
You'll probably need to use some string functions to split up your original query and put it back together so that you can put your WHERE clause before your ORDER BY clause. Holler if you get stuck.
-
a logicless workaround could be to possibly put in a dummy email account to the "to"
eg "formrecipients@yourcompany.com" so that it gets a TO address, even if it goes nowhere
-
You, are brilliant. That is exactly what the issue was. I relinked the docs and they all had their info back.
Thanks so much!