-
The message you are getting is not an error, but rather an informational message. It is quite okay to have 2 or more controls bound to the same data node. The warning is just so that you know that there is potential for a user to accidentally overwrite a value in one location in the view from another location.
In your case, both controls are in ...
-
When you call NewFromSolution() it returns you an XDocument object to the form just opened. Use this returned object to select the field in the newly opened form you want to update (just like you normally do in your code) and then set the value.
-
Look into the NewFromSolution and NewFromSolutionWithData methods.
-
Great! I'm glad to hear its working now. Keep up the good work!
-
Glad you got the issue resolved and that I was able to help out a bit.
-
If I recall the situation correctly, the correct structure was something like:
Main Repeating Section
-- Non-Repeating Section
---- Sub Repeating Section
-- Non-Repeating Section
---- Sub Repeating Section
-- Non-Repeating Section
---- Sub Repeating Section
-- Non-Repeating Section
---- Sub Repeating Section
I.e. each sub repeating section was ...
-
-
Yes - that is correct. Only a single submittable SQL connection. You will need to use a WS if you want multiple submittable connections.
-
Thanks for sharing this. Yes - you must ALWAYS remove the xsi:nil attribute before providing a value to a field. If you clear the value of a field, and it is marked as cannot be blank, then you must add back the xsi:nil attribute or else the field will show an error in InfoPath.
-
Did you add tree.xml as a form resource? See Tools menu.