Add calculated fields and running totals

A total worked out for you

Take an expense or order form. Someone enters an item price and a delivery cost, and you want the GST and the total worked out for them, not left to a calculator on the desk. The calculations read like the arithmetic you would write down:

As soon as someone changes a figure, the totals update. When they submit, the calculated values save to the SharePoint list columns alongside the rest of the record, so a report reads the number straight from the list.

More than money

The same idea covers a lot of ground:

• A due date worked out from a start date and a number of days.
• A full name or reference built from a few separate fields.
• A field that becomes required only when another answer crosses a threshold, using cross-field validation.
• A flag that a submission needs review when two answers do not line up.

No code, and it runs in the browser

You build the calculation visually rather than writing script, and it runs in the browser while the form is open. Nothing is written to the list until the person saves, so they see the result first and the stored record matches what they saw. No-code calculated fields work this way in both the internal SharePoint designer and the public web builder.