InfoPath Dev

Hey, wonderful, glad you figured it out!

I found following line after extracting the source files:  Should I remove the whole line? How them I able to put the source files into one xsn file? <div align="center"><span class="xdExpressionBox xdDataBindingUI" title="" tabIndex="-1" xd:xctname="ExpressionBox" ...

Thank you, that is what I needed to know. I just wanted to make sure my 'logic' wasn't flawed in how I was thinking about it. I figured out the problem. I had another rule that wasn't firing properly and so it was just overwriting the information in the initial section without creating a new one.

In the InfoPath data source, the form has a repeating node, and this repeating node has fields within it. The choice between a repeating table or a repeating section is up to the form designer, but it's just UI. That is, the InfoPath form schema (the data source) is the same, no matter if you're using a repeating table or a repeating ...

Yes, the People Picker only retrieves the single employee, but I have another field set to use the value of the People Picker field and I have a rule that queries the UserProfileService to obtain the manager of the employee listed in the People Picker. What I don't know is the easiest way to obtain the value of the next 2 higher managers and ...

So are you saying that the 'insert' command isn't the right command to use to generate a new instance of a repeating section? If not, what is I am not sure I got an error in the error node. I will go back and check. As for the other: If you have a repeating section with fields in it, then logically you have repeating data. However ...

Hi- As far as I know, People Picker just selects the one user (employee, from your description above). How will the form obtain the information to determine who are the "next two managers in the hierarchy"? Is this populated via a SharePoint list, via Active Directory? You would need this information available in a secondary data ...

Insert allows you to insert rows into a repeating table. For your Question 2, what are you getting in the Error node of the QdabraRules secondary data connection? This might tell us why it's not working. For your question 1, I guess I'm not understanding the scenario. If you have repeating data, then use a repeating table. If the data is ...

You've almost got it: you'll want the rule to exist on the yes/no choice box. When the user makes a selection, there will be a rule conditioned for yes and a rule conditioned for no. The action will be simple: just "Set a field's value" and you can use today() or now() as the formula. Good luck!

thanks for the response, Hilary.  I decided to "keep it simple" and have the repeating table from SP above an order form (showing item, description, and cost), created a drop down on order form based on the items in the SP, populate the description and cost based on that value.  The end user has to click on the repeating ...