Overview

Actionflows can be used to pass data between screens. This page will discuss how to pass an ID (primary key) of a contact from a grid to an edit form and display the contacts name as the header on the form.

This page assumes that the user has a grid of contact data with a primary key configured. See Understanding ERDs for more information.

A user has the following screen containing a contacts grid and no actions associated with the add, edit or delete buttons.

To create this screen either

Create a screen then select the attributes from the Contacts table and drag and drop them directly onto the screen. Display the attributes as a Grid.
Create a screen from the Contacts table in an ERD diagram. The attributes list will appear when the screen is created and the attributes can be dragged and dropped directly onto the screen. Display the attributes as a Grid.

A user also has the following edit screen containing form fields from the same Contacts table.

To create this screen either

Create a screen then select the attributes from the Contacts table and drag and drop them directly onto the screen. Display the attributes as Fields.
Create a screen from the Contacts table in an ERD diagram. The attributes list will appear when the screen is created and the attributes can be dragged and dropped directly onto the screen. Display the attributes as Fields.

Both routes automatically backs the form by the Contacts table and will display the first record by default.

Wiring data into the actionflow

To configure the edit button on the contacts to pass the selected user ID to a new screen

Right click on the edit button and select Add Actionflow
Name the actionflow Open Edit Form
Click Connect in the connections section
Select the Contacts Grid
On the mappings screen drag and drop the ContactID (primary key) to create a mapping into the actionflow. This ID is now available to be used within the actionflow.

HELPTRUNKR

Passing Data to a Screen

Overview

Wiring data into the actionflow