This blog post will show you how to create an expression box in an InfoPath 2007 form whose value is based on the result of an conditional sum. Consider the following InfoPath form template:
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:
| Expression Box | Expression | XPath Expression |
| Expense Total | sum(expensevalue) | sum(my:accounting/my:expensevalue) |
| Food Expense Total | sum(accounting[expensetype = “Food”]/expensevalue) | sum(my:accounting[my:expensetype = “Food”]/my:expensevalue) |
| Land Travel Expense Total | sum(accounting[expensetype = “Land Travel”]/expensevalue) | sum(my:accounting[my:expensetype = “Land Travel”]/my:expensevalue) |
| Air Travel Expense Total | sum(accounting[expensetype = “Air Travel”]/expensevalue) | sum(my:accounting[my:expensetype = “Air Travel”]/my:expensevalue) |
| Parking Expense Total | sum(accounting[expensetype = “Parking”]/expensevalue) | sum(my:accounting[my:expensetype = “Parking”]/my:expensevalue) |
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!
