Here's a quick overview of some of the great new features in InfoPath 2010. Stay tuned for upcoming posts with more details!
Microsoft InfoPath 2010 makes it easier than ever to design electronic forms. InfoPath now includes the Office Fluent UI and allows the creation of powerful, interactive forms, without having to write any code. With a few clicks, Office users can customize SharePoint list forms, add custom layouts and rules to validate the data, and take them offline in SharePoint Workspace.
IT professionals can create custom forms for document workflows and Office Business Applications that include managed code, digital signatures and that connect to line of business data.
In InfoPath 2010, we’ve made some big investments to make it much easier to build rich forms-based applications on top of the SharePoint Server 2010 platform.
Quickly Design Forms with Easy-to-Use ToolsNew features to help you quickly and easily create forms include our new Fluent UI, pre-built layout sections, out-of-the-box rules, improved rules management, and varied styles.
The New tab in the Designer Backstage presents you with the available form templates that you can choose from. Most templates start you off with a default layout table.
Stay tuned for more details on our new and improved form design features!
Layout your Forms Using Pre-built Page and Section LayoutsLaying out your form and making it look more attractive is now easier than ever. Insert one of our pre-built page layouts to give your form structure. Then, insert some section layouts into the page layout to start building your form.
Page and Section Layouts in InfoPath Designer:
New and Improved ControlsWe’ve added some new controls and narrowed the feature gap between client and browser forms, ensuring a more consistent form filling experience for all our users.
New controls in InfoPath 2010 include:
Controls and functionality that are now supported in browser forms include:
Add Rules to your FormsWith our new out-of-the-box rules (or quick rules) and improved rules management UI, you can easily add rules to validate data, format your form, or perform other actions with just a couple of clicks, and without any code.
Quick Rules in InfoPath Designer:
Publish Forms QuicklyOur new “quick” publish functionality allows you to publish forms in a single click (no more clicking through the Publishing Wizard every time you want to make an update to your forms!)
Create Forms for SharePoint ListsUsing InfoPath, you can now extend and enhance the forms used for creating, editing and viewing items in a SharePoint list. In a browser, simply navigate to a SharePoint list, and on the SharePoint Ribbon under List Tools, choose the Customize Form option. This will automatically generate a form which looks very similar to the default out-of-the-box SharePoint list form.
You can then customize and enhance this form by modifying the layout, creating additional views or pages, and adding rules to validate your data, show or hide sections of the form or set a fields value (to name just a few of the options).
Example of Customized SharePoint List Form:
Stay tuned for more details on SharePoint List Customization!
We recommend using a form associated with a SharePoint list when possible. This provides the most straightforward design and form management experience. However, there are more complex scenarios where using a form associated with a form library is preferred e.g. if your form has a complex schema or if you need to add code to your form.
Create SharePoint ApplicationsWith InfoPath 2010, SharePoint Server 2010, and SharePoint Designer 2010, you can easily create powerful team, departmental or enterprise applications on top of SharePoint Server.
Stay tuned for more details on creating SharePoint applications!
Create Mashups using the InfoPath Form Web PartNow, without writing a single line of code, you can host your InfoPath browser forms in Web pages by simply adding the InfoPath Form Web Part to a Web Part page. You can also connect it to other Web Parts on the page to send or receive data.
Stay tuned for more details on the InfoPath Form Web Part!Build Forms with CodeUsing Visual Studio Tools for Applications, you can add managed code to your forms.
Stay tuned for more details on programming with InfoPath!
InfoPath EditorThe InfoPath 2010 Editor Fluent user interface provides a much improved, simpler user experience for filling out forms.
Form opened in InfoPath 2010 Editor:
SharePoint WorkspaceInfoPath 2010 is the forms technology used by SharePoint Workspace 2010 for creating and filling out forms.
InfoPath Forms Services Administration and ManagementWe have invested in many improvements to make it easier to manage your InfoPath Forms Services as a component of Microsoft SharePoint Server 2010.
We hope you enjoy using InfoPath 2010 and look forward to getting your feedback!
The InfoPath Team
Heya. Can you tell me if there will be the capability to create custom controls for the web forms? E.g. click a map to confirm a location. We have a control to do this but want to integrate it with the form. Currently we have to create multiple forms (before and after the 'Confirm Location' control) which then makes editing the forms more painful, hence making InfoPath in SharePoint an inferior product compared to TKDialogs, AchieveForms.. etc.
We do not support creating custom controls in browser forms.
If you want to use custom controls in browser forms, we recommend that you create a custom aspx page, host the form in the XMLFormView control and add your custom control to the aspx page.
I hope that helps.
Hi great product infopath, I love it, and we are going to move our aprox 1200 application forms to infopath before 2015 and the 2010 release make infopath even easier to work with.
I want to create a template part, based on a number of XSD-schemas, so I can have a uniform layout for a company xsd-object “costumer” in a web enabled form, which I am going to use in almost all my application forms.
1. I open Infopath and pick a blank template part
2. I change the name of the root note
3. I add a new xml schema child group to the root note.
4. I then create my layout, based on my data source in the child group and save the template part
5. I then open a new form template and add the user template part, I just created to my costum controls library in infopath.
6. I then want to add the template part (costum control) to my root note, in my form template
7. I click on the costum control(template part), and nothing happens, not even an error message.
8. I add a child note to my root note and try to add the template part (costum control) again, same result.
9. I try to add the user defined control both in a web enabled and a only infopath enabled form template, but I get the same result.
xml schema used for the case: http://im.ferv.dk/kunde/2009/01/22/FERV_KundeStamkort.xsd
I don't have this problem if I create my data source inside the template part, only when I try to import a xsd to a group.
If I pick the design template part from XML schema I get another error.
When I try to add the costum control to my form template.
I get the error message "template part cannot be bound to the selected field or group",
no messsage about where I the can bind it, which would be nice.
I have both tried to add the template part at root level and in a child group, always same result.
When you add a complete XML schema or XML document node, it places a fixed schema into the data source. The whole schema is treated as fixed so it will not insert unless the data source of the solution that you're importing into has the exact structure of the schema contained in the template part. (Field names don't need to match but the structure and hierarchy must match).
This same behaviour is exhibited if the template part is designed from a schema (hence the error the user sees “template part cannot be bound to the selected field or group”) so that the template part can only be inserted when the template part schema matches the solution schema. To have the schema created on insertion, the schema in the template part needs to be created manually.
i have created a form in a list item for peple to enter details
i can use the form and post details fine. but any otheruser that tries to access the form has problems
the form is not found
please note that all test users are home owners
Thanks for your last answeer, Its not a nice an easy solution, but I managed to make it work.
I have another small problem that you might can help me with. We would like the users to be able to make a paper print of the form, to fill out by hand.
However a lot of my tables are expanding tables, are there any possible way to make a minimum number of lines in the print wiew.
I only want the number of lines the user enters in the data view. (lines that are filled out)and send to us.
I think this is a general problem many of us Infopath designers run into, since some people still only wants to send in a form, that they first print out and then fill in by hand, the alternative is to make a PDF of the form, to be printed out and an Infopath to be filled on the computer.
In response to Vkanta's question, please post it to the SharePoint 2010 forum on http://social.msdn.microsoft.com/Forums/en-US/sharepoint2010general/threads and we will respond.
Please also include more details on the problem. For example could the users access the list items before the form was customized in InfoPath? Is there any logic or data connections that run on form load?
In response to Jan Sohn's question. We have 2 suggestions:
1) In InfoPath Designer, click File, Info, Form Options, Advanced tab
2) Click the "Edit default values" button
3) In the Edit default values text box, expand the group repeating group nodes
4) click the dropdown arrow beside the repeating group node, and select Add another <groupname> below. Repeat this step for each row that you want to display in the table by default.
NOTE - this does not only apply to print views i.e. the blank rows will display in all views
1) Create a new view and add a static layout table with the number of required rows
2) In your default view properties, Print Settings tab, select the new view as the print view.
This view will only be used when printing the form.
I was rather hoping for a solution to viewing and filling in forms from Outlook without requiring an Infopath client installed.
Is it still not possible to use a web form directly from Outlook, especially as optional sections, multi-select-listboxes etc are now supported?
Outlook being ubiqitous and providing such rich viewing options would be an ideal platform for my forms.
An alternative *might* be Sharepoint hosted webforms, with the Sharepoint list synced to Outlook, but I don;t expect that will be a neat solution.
Our mail forms story requires the InfoPath client to be installed (we send an InfoPath XML file in mail, which can only be opened in the client). We don’t really have a mechanism to forward active browser forms in mail.
This is good feedback. It would be great to learn more about your scenario and why you want to send the forms in mail.
It looks like there are a great amount of improvements here from 2007. Does InfoPath 2010 now support rich text to SQL or SharePoint Lists?
In InfoPath 2010, we now support rich text fields in SharePoint lists.
Will IP 2010 have an easy method without code to save a final version of a form as a PDF?
If there is no way to have a separate install of filler and designer, is there a way to disable user machine to prevent them from designing infopath forms. We only want developers to do the designing of infopath forms and users just to fill-up forms.
Note that we are not getting form services.
The only new feature that I was excited about was the separation of the filler and designer but then I was extremely disappointed to find out that you cannot install and license separately...
I will give many reasons why they should be separate:
1) Usually the designer is never the filler.
2) You do not want the filler to be able to open any form in design view(maybe form design is proprietary)
3) Filler should be provided free (or low cost) so you can compete with adobe.
4) Form services will never reach the level of the filler in richness and performance.
5) If filler is provided free (or low cost) more companies will adopt InfoPath as their data collection tool.
Please give me intelligent reason, why you did not separate them.