Database Insert — Reference

Insert a record using explicitly mapped values.

Before you begin

• A working database connection and a disposable test table or records. Validate inputs and enforce access before private reads or writes.

Database Insert

Insert a record using explicitly mapped values.

Settings

Setting	Meaning
Name	The step name used by later server expressions and named action output. For example, a query named products is available to subsequent steps as products.
Output	Includes the named result in the action response. The result can be used by later server steps when Output is off. Several rules initialize Output on although their declared default is false; inspect the saved action.
Connection	The database connection definition to use. It must be available and correctly configured for the active target.
Insert Options	Select the destination table and map intended column values from literals or validated server data. Review generated/related-key configuration where used.

Worked example

In a disposable products table, map name to Notebook and price to numeric 12.5. Run the action and inspect the returned affected/identity information plus the stored row. Use the returned identity for a follow-up operation where supported by the configured database.

Result and safety boundaries

Validate input types and required fields before the write. Generated identity behavior depends on the table and driver. When inserting related data, review the relation mapping as well as the parent record. A successful insert does not authorize the caller to write arbitrary owner or role values.

Use the database workflow

Use Database Manager to define and inspect the underlying tables. Use Server Connect to control the data returned to the page, and verify the actual response shape before choosing an App Connect binding.

Check your result

You can configure the intended query/write scope and verify its result shape or database effect.