InfoPath Dev

This gets a little tricky with a hardcoded dropdown. If we put this data in a secondary data source instead, it gets a lot easier. I'd suggest you create a SharePoint List for this data - it would have two columns - one for email, one for name. Then you can add a data connection to that list, and use it for your dropdown, with the email for ...

Attaching your screenshot to this post, and closing the other thread - you can always just add a reply to your thread with each additional file.

 You may need to disable loopback check on the server - since we don't have server access on SharePoint online, that environment can't be modified in this way. This article describes two methods - disabling loopback check is less recommended in terms of security, but may be faster to verify that this is the root cause of the ...

Hide the submit button on the ribbon. Disable your form submit button if the field isn't filled out.... Then they can't submit unless the data is there. :)

You can fix that by resetting the "Set" node. So, for all your rules that run to set values, run those only if set is equal to one or go or whatever you are setting it to. Then for your last rule, set the field back to blank - that way it is ready to go again when something changes and it needs to re-fire. Make sense?

Wonderful, glad you have it working. I used InfoPath for ages before I realized I could add a rule to a repeating node. :)

I think you should just add the same rule to the repeating group. Select the repeating table in the form and in the rules pane, you can add a rule that will fire when a new row is added. That rule will affect any new row, and only that row. Give it a try, and attach your latest template if you need a hand, ok?

Oh, I should add - you'll also likely need a rule on the repeating table so that this gets set when a user inserts additional rules after making their commercial / residential selection. And the rule on the deployment planner field itself needs to be tested carefully - you want to make sure that when you re-set the value of a field with a rule ...

You have different display and value options for your dropdown. Your rule instead needs to set to the value when Commercial Planner is selected - COMMInventory@xxxxxx.com (removed domain so no-one gets spammed).

 I'm wondering if you might be able to get around this using rules instead of defaults. For example, you could try adding a node to your main repeating data source (doesn't have to show on the form) called "Set" or something. When a new form is started, in the form load rules, or any time after your query for the correct ...