Choose the data operation
| Requirement | Configure |
|---|---|
| Populate a dropdown | A SQL prevalue/options source |
| Browse existing records | An external submission/data source |
| Insert submitted answers | A database insert binding |
| Multiple dependent writes | A reviewed workflow or server integration |
Connect and map
- Configure a named connection in the server's connection registry. Keep credentials on the server.
- Inspect/probe the real table and its key, column types, defaults and required columns.
- In Form Settings → Data & storage, map stable field keys to the insertable columns.
- Decide how an external write failure should be handled. Review the binding's failure policy.
- Submit fictional data and verify both the MegaForm entry and the destination row.
Do not assume a read-only external table supports Add new entry. Inserts need an explicit, authorised write mapping. MegaForm must not silently migrate or delete an application-owned table.
Cascading choices
For Customer → Order, the second query uses a parameter based on customer_id. Configure dependency reload and verify that changing Customer does not leave an Order from the previous customer.
Run the local example
The SQL demo reads workshop choices from App_MegaFormDemoWorkshops and inserts a booking into App_MegaFormDemoBookings. This host uses SQLite; SQL Server schema qualifiers and conversion functions are not interchangeable with SQLite syntax.
The demo's public summary exposes aggregate counts only. Raw submitted values stay in the authorised submissions workspace.
Use idempotency or a unique business key for external operations that may be retried. A successful canonical submission and a successful external insert are distinct outcomes.