# Transactional Forms

## Overview

Transactional data is linked to your main UbiQuity database and is useful for storing related records against a contact, such as purchases or event bookings. If your account uses transactional data, you can add transactional fields to Subscribe, Update, and Subscribe/Update forms.

Each form submission can include up to 10 new transactions.

***

### Adding Transactional Fields

The Transactional Fields panel is available in the Edit Fields and Validation screen, below the Form Introduction section.

<figure><img src="/files/68tTWlZmKoC1iRvMbhou" alt="A screenshot of the Add Fields and Validation page showing the Add Transactional Fields option"><figcaption><p>The Add Fields and Validation page showing the Add Transactional Fields option</p></figcaption></figure>

Click **Add Transactional Fields** to open the setup dialog. From here you can:

* Select which transactional database to use
* Set the minimum and maximum number of transactions allowed per submission (between 0 and 10)
* Customise the Add and Delete button labels that contacts will see on the form

<figure><img src="/files/CRoxn5YjE0mbA8W00nqz" alt="A screenshot of the Add Transactional Fields dialog, where you select a transactional database and configure submission limits and button labels"><figcaption><p>The Add Transactional Fields dialog, where you select a transactional database and configure submission limits and button labels.</p></figcaption></figure>

Once confirmed, mandatory transactional fields are added to the form automatically. You can then add additional transactional fields from the dropdown, the same way you would add standard database fields.

You must have at least one standard database field on the form so that transactions can be linked to a database contact.

***

### Rules for Transactional Fields

All mandatory transactional fields without default values must be included before the form can be saved. Attempting to remove them will produce a validation error.

If your transactional database has unique fields and a submitted transaction fails the unique check, an error message will be displayed at the top of the form.

***

### Editing and Removing Transactional Fields

To change the number of transactions or button labels, click Edit Options at the bottom right of the transactional fields section.

To switch to a different transactional database, click Remove Transactional Fields and then Add Transactional Fields again.

You can remove individual transactional fields using the delete button next to each field, or remove all of them at once using Remove Transactional Fields.

***

### Filtering and Reporting

Once transactional fields are added to a form, you can use them as part of a matching transactions filter across UbiQuity. To see how many transactions have been submitted via a specific form, apply a filter using the form name as the source.

<figure><img src="/files/aTBScgwlaGYUVbe1qTf6" alt="A screenshot of a filter condition showing how to find contacts with matching transactions from a specific transactional form, filtered by a field value."><figcaption><p>A filter condition showing how to find contacts with matching transactions from a specific transactional form, filtered by a field value.</p></figcaption></figure>

<figure><img src="/files/Zu1hX7XrGojUAg8wEsRH" alt="A screenshot of the Manage Transactions screen with a filter applied to show only transactions submitted via a specific form."><figcaption><p>The Manage Transactions screen with a filter applied to show only transactions submitted via a specific form.</p></figcaption></figure>

***

### API Support

Transactional fields are supported through the UbiQuity API. The form submit and validate API calls include transactional data. See [API documentation](/documentation/data-and-integrations/api.md) for more detail.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.ubiquity.co.nz/documentation/data-capture/forms/transactional-forms.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.