Cognito-forms – Repeating sections auto numbering

There are a couple of ways to handle calculating subtotals for repeating sections:

1. If the form represents a true invoice and the subtotals represent money and nothing else, you can set the form up to use the built in payment features of Cognito Forms. When you mark fields as Collect Payment, they will automatically appear on receipt/invoice grouped by repeating section item. Choice, Currency, Yes/No and Price fields can all appear on this "invoice" and the Price field gives you complete control with the ability to calculate both the amounts and the description of each line item if you need this power. In this case you would not be collecting payment from them, so mark the form via Payment Settings as never requiring payment.

2. The other option is to use the powerful calculation capabilities in Cognito Forms to quickly calculate the subtotals. In the example above, you could add a Calculation field at the bottom of the form and use a calculation like =MyOrder.Sum(ItemTotal) or even =MyOrder.Sum(Product_Amount * Quantity) to calculate the total for the My Order repeating section. Remember set the Type to Currency for the Calculation field so it will be formatted correctly and allow you to use the value of this field in other calculations. You can learn more about these capabilities in our help documentation at: https://www.cognitoforms.com/support/51/calculations/repeating-sectionstables. Take a look at the section on Working with Repeating Sections.

Please mark this as the answer if it helps you make this work, or add a comment if it is not quite what you were looking for.

Cognito Forms allows you to post a JSON document to webhooks when new entries are submitted that accurately reflects the data being collected. Forms can be hierarchical with multiple repeating sections and even nested repeating sections, so it naturally lends itself to being expressed using JSON. Repeating sections are not stored in a single field--they are actually arrays of child entities that have their own fields and children.

For example, the form you described might look like this:

And the corresponding JSON looks like this:

As you can see, the Children repeating section is represented correctly in JSON as an array of child entities, each of which have Name and Gender fields.