-
It appears you do have a default value in Manager. Remove the default. It does appear you have form load rules to set the value. Since you query these data connections in your form load rules, you may wish to set those data connections to not query on load - that is an option in the last screen of the data connection wizard.
-
Your condition in your form load rules is incorrect. It is checking the account name field in the secondary data connection - on form load, that will always be blank. Instead check the account ID field in the main data connection.
-
You can add rules to the field that the drop down is bound to that set your other fields. You'll need to add a filter - http://brian-horning.com/filtering-sharepoint-form-data-using-infopath/ might help you.
-
Please see my reply to your other post. In short - this shouldn't be happening unless there is an issue with your form load rules or you are using default values.
-
Can I see a copy of your form? You can attach it under the Options tab like you did your screenshot.
-
A quick trick I use in the browser to check if the issue is postback (as long as the ribbon is on the form) - hit the Close button, then cancel closing. That forces a post back and you'll see your command has "magically" executed. In general, in browser forms, all controls that execute a command should have postback sent to always, ...
-
You need to set postback to always on the control executing the command. PS > if your mapping data connection is named mapping, you don't have to include the /mapping param, and can just use SubmitToSharePointList /submit=Submit
-
I do see a rule on your "submit" button that appears to set a field's value after you submit and close the form - so that will be an issue. I don't know what this means: "form getting refresh not saving in form library". I think you are saying that when you re-submit an existing XML, the file isn't overwritten? But ...
-
No - you can use secondary data connections to lists, web services, etc. in forms with custom code & qRules.
-
Your "Value" node didn't have a namespace prefix. My "field2" node did - the "my:" prefix. That's why I asked for your exact XPath - so the XPath to the preceding sibling was correct.