-
Yes, pulling information from the template.xml or sampledata.xml is very useful depending on what you are trying to do. Just load the XML file in your code and then navigate it like you would any other DOM.
-
Manually editing any of the InfoPath template files can be a dangerous thing. Always keep a backup of your files before manually editing them. Be sure to edit only those portions that need to be edited, and make sure you make the edits across all related files... this could include:
* manifest.xsf
* template.xml
* sampledata.xml
* myschema.xsd
* ...
-
Perhaps your conditional formatting is the issue. Just having a section around the layout table should not cause it to disappear like that unless its set to not be inlcuded by default.
-
Sorry -- I should have posted a link to the example (assuming you wanted to try modifying the XSL):
Display Multiple Fields in a Drop-Down List Box
-
Glad to have helped. Keep up the good work!
-
Article: Disable a Button Until All Required Fields are Filled In
Figure: 3
Caption: The submit button is disabled until all required fields are filled in.
-
Article: Disable a Button Until All Required Fields are Filled In
Figure: 2
Caption: The conditions required to disable the button.
-
Article: Disable a Button Until All Required Fields are Filled In
Figure: 1
Caption: Custom validation requiring that a rich text field cannot be blank.
-
If you extract your form files (File menu) you can manually modify the XSL for your views.
-
Multiple views are supported (since the initial release). You can use buttons or code to navigate between the views, or the View menu works too.
You will always have a template. The template is just the design of the form and description of the initial state when a user first opens it. Think of it this way, you have a ''design mode'' and an ...