-
Are you per chance trying to switch views while a switch view is in progress? For example, you click the button, it switches the view, but the code behind the button tries to switch to another view?
This will cause the issue (or something similar to the one) you are seeing.
-
Sounds like there might be a difference in the returned XML structure... the schema has likely changed between then causing the issue.
-
The problem is most likely that there is an error in a different view. For example if you have 3 views and 3 required fields in your form template, and each view contains only one of each of the required fields... then no matter which view you are on, you are only seeing 1 of the required fields. Thus if you fill it out and try to sign/submit, ...
-
So what you are looking for is a way to build a dynamic form? It is possible to have a form design such that it pulls in a secondary data source (another xml file, etc) and constructs itself based on that. A valid example of this is a survey form. There would be the form that users open to fill out the survey, and the one that the admin uses to ...
-
InfoPath does include an attachment control. The attachment is stored directly in the document as a base-64 encoded string.
-
You basically have it. The one condition is that you must use code. There is an Errors collection--check to see whether there are zero errors. Errors occur because required fields (red asterisks) are not filled in or because of invalid data (text in a date picker field). This soundsl like all you need.
There is a way to call into code from ...
-
Your first question -- yes, those assumptions are correct.
Quotes are there to separate the code from the rest of the text.
The equal sign after field1 stands for "is defined as".
The ../ means to go to the parent node.
-
This is much more difficult. There is no concept of named anchor points as in HTML.
In InfoPath, hyperlinks only do one thing... link to a URL or URN. They don't get any fancier than that. However, you can format a button to look like a hyperlink by removing the border and background color and making the text underlined, etc. Then in the ...
-
2DS is my abbreviation for Secondary Data Source. Repeating tables bound to a 2DS are basically 2nd class citizens in InfoPath (unfortunately)--there are a lot of features turned off for them (as you've seen, inserting rows, filtering, etc).
Modifying the DOM of a 2DS is the same as working with your main DOM. If you are using the InfoPath ...
-
While you can set values with rules, the most useful method is using code. This will allow you to properly pinpoint the correct row and fields.
Using code you can also get by the limitation about adding/removing rows in a 2DS repeating table. In code you can simply insert a new row node, or remove one. Set up buttons that call into the code to ...