-
The schema I described for the secondary data source is just a list of names. If yours is different, please describe how it is different (please be more specific) and explain why the steps I listed don't work in your case.
-
I'm not sure what you mean by making an XSN programmatically. A form template needs to be visually designed and that requires human interaction. While it's not impossible to make an XSN programmatically, I wouldn't recommend it in most cases.
-
The first thing you can do to troubleshoot this is to display the username on the form and make sure it's showing the value you're expecting in all cases. It might be the case that the "username" field is set to the user who created the form for some reason or other.
-
Absolutely. Once you have used the schema to create your form template (XSN), when you open up one of your pre-existing XML forms, InfoPath will prompt you for the location of the template. If you check the "Always use this form template for this file" checkbox, InfoPath will inject a PI into the file so that the file will ...
-
Could you describe the set up of this table/the data sources with a bit more detail? InfoPath does not sort repeating tables, and if it is showing up sorted it is more than likely that's because that's how the data is being returned from the secondary data source.
-
Under what conditions/after what action do you want to add a new row to the table? Surely you don't want to add a new row every time someone makes any change within the table.
-
Fiddler2 will allow you to inspect web requests.
-
Have you tried using rules that execute when the form loads? You can find the option to set these in Tools→Form Options...→Open and Save. This should also enable you to conditionally query the data connection when the form is loading.
-
Sounds like the data source behind the dropdown box isn't populating with values when the form is re-opened, and so it has no recourse but to show the value that was stored in its bound field.
Could that be the issue?
-
This is an old post, but I ran into a similar issue myself today, and as the error suggests, the correct syntax is to not use parentheses:
XDocument.View.ExecuteAction "XCollection::Insert", "lotBreakdownRT_41"
alternatively, you can precede the statement with the Call keyword and use parentheses:
Call ...