-
Hi:
I recommend the double eval trick, as described here.
From what I see in your screenshot, the formula might end up looking like:
eval(eval(@nameTransmittal/Recipients/Recipient, "concat(@name, ';')"), "..")
-
Currently we do no have a build for qRules that will allow the injector to run on a 64 bit machine. We hope to fix that soon with a 64 bit build.
-
Is the rule on the field that you are modifying? What field is the rule on, and what field are you setting the value for? What field is being changed by the rules that add spaces and modify to upper case? Maybe you could attach a copy of your template (under the Options tab when you post)?
-
What field is the rule on? Is it a field INSIDE the repeating group? Or outside?
-
You don't get an error when you save it as an IP 2003 form? Nothing in design checker? You aren't using anything that is IP 2007 only, like combo boxes, right?
-
How odd! Can you attach your form so someone can take a look, see if it repros? Under the Options tab when you post, you can attach an .xsn file....
-
Hi, Ed:
Your rule is set on your text field in your repeating section? What's the rule look like? It sounds like the data isn't being filtered properly to select the correct value from the Access data source, if you are always getting the first row returned. I take it the values in the Access DB that you are comparing your form info to ...
-
I'm not sure I understand the issue. Are you saying that if more than one repeating section is entered into your form, the additional sections don't show in the email that is received, even if they are not conditionally formatted to hide? Can you attach your form?
-
Wow, I just don't have any good advice for you -- You may have gotten as much out of your original form as you can with the HTML to Word, then Word to InfoPath route. This Office Online article explains more about the Word to InfoPath import and may give you some insight as to what is happening with your fields....
-
Hi --
It sounds like you have step 1 complete -- your InfoPath form has a submit connection to your desired library?
For step 2, a dropdown would be fine. Think about how often those email addresses might change, and you may want to use a secondary data connection to populate your dropdown, so that you don't have to modify the form to ...