How does InfoPath store data?
All the InfoPath data is stored in an XML file within the Forms Library. This means that all the data for the form (field names, values, etc) is stored in the same XML, both fields that are visible only within the form, as well as those that are “promoted” (“shared” or “exposed”) to SharePoint.
How do InfoPath forms work?
When a user opens a form that connects to a data connection file, InfoPath uses the settings in that file to connect to the external data source. In this way, multiple form templates can use the same data connection file, so there is no need to manually create the same data connection for each form template.
How to create a conditionally required field in InfoPath?
Here are the steps to creating a conditionally required field in InfoPath (I am using InfoPath 2010 so the exact directions may need to be tweaked for 2007 users): Select the field that should be conditionally required. In the Rules pane, select New > Validation. Name the rule. Under Condition, click on the None link.
Which is the best way to organize InfoPath fields?
After: At one glance, it’s easy to see the structure and function of much of the form. InfoPath makes it so easy to bang out a form in just a few clicks, but the cost of this is lack of enforcing any kind of structure or rules to that will help you and others in the future to remember how the form is structured and what it’s actually doing.
What should the name of an InfoPath rule be?
Much like fields, by default InfoPath gives the rule a name like ‘Rule#’. I use a descriptive name that includes a verb, which describes the action the rule is actually doing.
When to use CamelCase to name sections in InfoPath?
Use CamelCase to name sections and fields to make the names more legible. Since InfoPath does not allow spaces in field and section names, using CamelCase can make it much easier to distinguish distinct words for field names. For example: producttype becomes ProductType. 3. Use Sections Sections aren’t just for conditional displays.