This session was an introduction to applications based on InfoPath 2010 and Forms Services 2010, and it was given by Peter Allenspach and Bojana Duke, from Microsoft. It was split in three parts, consisting of a demo each:

• Demo 1: Customizing SharePoint List Forms
• Demo 2: Creating Mashups with Forms Web Part
• Demo 3: Office Business Application

Here are the news about developing applications with InfoPath 2010:

• With SharePoint 2010 and InfoPath 2010 you have the possibility to customize a list’s forms with a single click. This allows you to create a new list form with InfoPath very easily, and you can even mix data from several lists and show it on the form.
• When designing a new InfoPath form for a list, you can add or remove fields from the list just by adding or removing them from the InfoPath form.
• Customized InfoPath List Forms are made available offline when you synchronize your list with SharePoint Workspace 2010.
• Forms Services in SharePoint 2010 supports FireFox and Safari browsers, besides IE.
• Forms Services in SharePoint 2010 supports WCAG 2.0 accessibility standard.
• InfoPath Forms with code-behind no longer requires an administrator to deploy them. They can be deployed with a one-click process and run as a Sandbox Solution without any security concerns.
• The InfoPath Form Web Part is now available to be placed anywhere, allowing any InfoPath form to be rendered. This Web Part also accepts connections from other Web Parts, allowing it to be used to create mashups easily.

The post SPC’09: Introduction to SharePoint Applications using InfoPath and Forms Services 2010 appeared first on Blog IT.

There are several options in biztalk to manipulate xml header processing in output messages:

• Set the header in orchestration using the message context properties

Example
message(XMLNORM.ProcessingInstructionOption) = 0 (append) or 1 (create new);
message(XMLNORM.ProcessingInstruction) = “xml processing header to add or append”;

Important: For the demoting process to occur, you must use the Xml assembler component or xml transmit pipeline in the output send port.

• Use xml transmit pipeline or a custom pipeline with the xml assembler component in the output send port

When you use the xml transmit pipeline, you must set the following properties:

ProcessingInstructionsOptions – 0 (append) or 1 (create new)
XmlAsmProcessingInstructions – “xml processing header to add or append”

• Use a custom pipeline component

When  you use a custom pipeline with xml assembler component, set the following properties:

Add Processing Instructions – Append or Create new
Add processing instructions text – “xml processing header to add or append”

This option is the most difficult to implement, you have to create a custom assembler component, get and change the output message.

Do not forget to set the the biztalk maps property “copy processing instructions (pis)” to “yes” when you want to copy the processing instructions from the input to output messages.

The post Biztalk xml header processing appeared first on Blog IT.

The previous image shows a simple expense report. To support the introduction of the expense information, a Repeating Table control is used with three columns:

• Expense – Expense Description. A simple Text Box control;
• Value – Expense value. A simple Text Box control;
• Expense Type – Drop-down List Box control that allows 4 expense types: Food, Land Travel, Air Travel and Parking.

Below the repeating table there are 5 expression boxes that show the total amount of the expense report and the total amount for each expense type. The total amount expression box is based on a simple sum expression and each of the expense type expression boxes are based on conditional sums filtered by the value of the expense type Drop-down List Box control. The expressions used for each expense type are the following:

As the previous table shows, the conditional sum expressions for each expense type are relatively simple and pretty straightforward for those who are familiarized with XPath, since XPath syntax is used for each expression. This comes as no surprise since the underlying data of the InfoPath form is stored in XML. The following image shows an expense report example filled with some sample values:

Related Articles

To learn why your business should migrate to SharePoint Online and Office 365, click here and here.

If you want to convert your tenant’s root classic site into a modern SharePoint site, click here.

If you are a SharePoint administrator or a SharePoint developer who wants to learn more about how to install a SharePoint farm in an automated way using PowerShell, I invite you to click here and here. The articles use AutoSPInstaller with a SharePoint 2016 farm but AutoSPInstaller support for SharePoint 2019 was already announced!

If you want to learn how to upgrade a SharePoint 2013 farm to SharePoint 2019, click here and here.

If you want to learn all the steps and precautions necessary to successfully keep your SharePoint farm updated and be ready to start your move to the cloud, click here.

If you learn how to greatly speed up your SharePoint farm update process to ensure your SharePoint farm keeps updated and you stay one step closer to start your move to the cloud, click here.

If you want to learn how to upgrade a SharePoint 2010 farm to SharePoint 2016, click here and here.

If you are new to SharePoint and Office 365 and want to learn all about it, take a look at these learning resources.

If you are work in a large organization who is using Office 365 or thinking to move to Office 365 and is considering between a single or multiple Office 365 tenants, I invite you to read this article.

If you or your customers are not ready to move entirely to the Cloud and Office 365, a hybrid scenario could be an interesting scenario and SharePoint 2019 RTM was recently announced with improved hybrid support! To learn all about SharePoint 2019 and all its features, click here.

If you want to know all about the latest SharePoint and Office 365 announcements from SharePoint Conference 2019, click here and here.

Happy SharePointing!

The post InfoPath 2007 – Conditional SUM appeared first on Blog IT.

The url inserted on InfoPath was http://SERVER/sites/xpto and InfoPath returned an error message alerting that there wasn't a SharePoint site on that url but on in IE it works just fine.

Then we discoverd the problem, the http://SERVER/ site didn't have a Site Collection created, when we've created the site collection InfoPath stardet working just fine :).

The post Strange problem when Publishing Infopath Forms to Microsoft Office SharePoint Server appeared first on Blog IT.

The post Enabling InfoPath IntelliSense Documentation in VSTA and Visual Studio appeared first on Blog IT.

The post InfoPath 2007 Resources appeared first on Blog IT.