Skip to main content
Version: 1.28 (Current)

Save Report in the Database (Obsolete)

Audience: Low-code Engineers

Skill Prerequisites: Actions, Forms

Saves the current form data as a form report entry in the database. If an entry is already loaded in the form, that entry is updated. Otherwise, a new one is created. The actions after it keep running.

This action is only available in Forms.

caution

This action is obsolete. Form reports, including the Enable Reports form setting and the Save to Report field setting, were marked obsolete in version 1.27. Existing forms still work, but new applications shouldn't rely on form reports. As a suggestion, save the data to your own database table instead, for example with Run SQL Query.

When reports are saved​

You often don't need this action, because forms can save reports on their own. When the form's Enable Reports (Obsolete) setting is on, a button click that passes validation:

  1. Creates a draft report entry before the button's actions run, if none is loaded yet.
  2. Saves the entry again after the button's actions finish.

Add Save Report in the Database (Obsolete) when you need the entry saved at a specific point. For example:

  • In the form's On Validation Failed event, to keep the data even when validation fails
  • In the middle of a button's actions, so later actions can use [_ReportEntryId]

The action saves the entry even if Enable Reports (Obsolete) is off.

Typical Use Cases​

  • Maintain existing forms that already rely on form reports
  • Save a report entry when validation fails, from the On Validation Failed event
  • Get the entry ID in [_ReportEntryId] before the end of the button's actions, for example to add it to an email

Don't use it to​

  • Save data for a new application. Save it to your own table, for example with Run SQL Query.
  • Save fields that don't have Save to Report (Obsolete) turned on. They're skipped.
Action NameDescription
Load Entry (by ID) (Obsolete)Loads a saved report entry into the form.
Load Entry (by User ID) (Obsolete)Loads the most recent entry a user submitted in this form.
Run SQL QuerySaves data to your own table, the suggested alternative.

Input Parameter Reference​

This action has no parameters. Use the action's Condition to control when it runs. See Common Parameters.

Output Parameters Reference​

TokenDescription
[_ReportEntryId]The numeric ID of the saved report entry.
[_ReportKey]The key (a GUID) of the saved report entry. Load Entry (by ID) (Obsolete) uses this key.

What's saved​

  • Fields that have Save to Report (Obsolete) turned on. This setting is off by default.
  • Fields from connected forms that have Save to Report (Obsolete) turned on.
  • Internal values whose names start with __.
  • Details about the submission: the date (UTC), status, the user's IP address, browser and referrer. The IP address, browser and referrer of an existing entry are kept.
  • The user, if someone is logged in and the form isn't editing an existing entry.

Colons (:) in field names are saved as underscores (_).

Considerations​

  • Updates, doesn't duplicate. If [_ReportEntryId] or [_ReportKey] already points to an entry, for example after a Load Entry (by ID) (Obsolete) or an earlier save, the same entry is updated.
  • Status is Submitted. The action always saves the entry with the Submitted status.
  • Check field settings. If a field is missing from the report, turn on its Save to Report (Obsolete) setting.

Examples​

tip

To understand how to use the below examples, please see Running Examples.

1. Save the report entry​

This action saves the form data as a report entry. Later actions can use [_ReportEntryId].

{
    "Title": "Save Report in the Database (Obsolete)",
    "ActionType": "SaveReportDb",
    "Description": "Save the entry before sending the confirmation email",
    "Parameters": {}
}

Revised 09/26/2026