The designer interaction blocks are user interfaces that are used to display information or gather feedback (e.g., input dialogs, quantity dialogs, message boxes, etc.). The interface layout cannot be modified and may display differently depending on the operating system running Warehouse Insight.

The following table provides a summary of the available interactions. Select an interaction or scroll down to see more details about each interaction.

The following sections outline each available interaction and provide an example of how the interaction can be used.

The Ask for a Date block displays a dialog to the user asking for a date:

Block Configuration:

When executed, users see a dialog like this:

When closed, press OK again to accept the value previously selected.

After execution, the following variables are set:

• dialog_result: 0 if Cancel is pressed, 1 if OK is pressed.
• action_result: Contains the date entered as displayed.
• date_universal: Contains the date formatted to universal full date/time format.

Provided below is an example of an Application Designer block using Ask for a Date:

The Ask for a Number block displays a dialog to the user asking for a simple number value. The dialog does not factor in units of measure or have abilities to limit to integers specifically.

Block Configuration:

When executed, users see a dialog like this:

After execution, the following variables are set:

• dialog_result: Will be 0 if Cancel is pressed, 1 if OK is pressed.
• action_result: Will contain the value entered.

The Application Designer example below uses Ask for a Number:

Ask for Confirmation displays a dialog to the user asking for confirmation (yes/no).

Block Configuration:

After execution, the following variables are be set:

• dialog_result: Will be 7 if No is pressed, 6 if Yes is pressed.

The Application Designer example below uses Ask for Confirmation:

Ask for a Text displays a dialog to the user asking for a text value.

Block Configuration:

In addition to the published configuration options, there are a few variables that can be created/set to help further override the dialog behavior:

When executed, users see a dialog like this:

After execution, the following variables are set:

• dialog_result_int: 0 if Cancel is pressed, 1 if OK is pressed.
• action_result: Contains the value entered.

The Application Designer block below is an example of using Ask for Text:

Capture Signature displays a dialog to the user asking for a signature. The signature data must still be processed/handled in Business Central.

Block Configuration:

When executed, users see a dialog like this:

After execution, the following variables are set:

• dialog_result: Will be 0 if Cancel is pressed, 1 if OK is pressed.
• signature_name: Will contain the name typed in.
• Blob: The signature data.

The Application Designer block below is an example of a Capture Signature block. The first part indicates the minimal Application Designer block sequences required. The second part takes the signature and attaches the image to a Sales Order based on the signature name that was entered.

Business Central Code:

Choose From List displays a dialog to the user asking for selection from a dropdown/picker control.

Block Configuration:

When executed, users see a dialog like this:

Selecting the entry causes the list options to appear:

After execution, the following variables are set:

• dialog_result: 0 if Cancel is pressed, 1 if OK is pressed.
• Selection: Is the index of the selection made (0 being the first option).
• selection_text: Is the text of the selection made.

The Application Designer example below uses Choose From List:

Choose From Table displays a dialog to the user asking for a selection from grid.

Block Configuration:

When executed, users see a dialog like this:

After execution, the following variables are set:

• dialog_result: 0 if Cancel is pressed, 1 if OK is pressed.
• FieldName: Every field on the selected row is returned with the FieldName replaced as needed.

The Application Designer example below uses Choose From Table:

The Application Designer example below uses the Choose From Table block and a specified Event ID:

Business Central Code:

Device Columns:

Choose With Buttons displays a dialog to the user asking for selection from a series of buttons.

Block Configuration:

When executed, users see a dialog like this:

After execution, the following variables are set:

• dialog_result: 0 if Cancel is pressed, 1 if OK is pressed.
• Selection: The index of the selection made (0 being the first option).
• selection_text: The text of the selection made.

The Application Designer example below uses Choose With Buttons:

Display a Message displays a message to the user.

Block Configuration:

When executed, users see a dialog like this:

The Application Designer example below uses Display a Message:

Similar to Display a Message, Display an Error displays a message to the user. The block may be styled differently depending on the Operating System. The error message logs as a Warning to the log file.

Block Configuration:

When executed, users see a dialog like this:

The Application Designer example below uses Display an Error:

Display a Popup Message displays a message to the user that hides after a brief period.

Block Configuration:

When executed, users see a dialog like this:

The Application Designer example below uses Display a Popup Message:

Editable Panel allows users to modify a record in a dynamic fashion. When executed a dialog displays with various editable fields based on the dataset supplied.

Block Configuration:

When executed, users see a dialog like this:

• The control types and editable states of the panel are controlled via the column definition returned in the dataset.
• The field is editable if there is an Editor specified for the column (e.g., TextBox, ComboBox, CheckBox).
• The type of editor depends on the Data Type.
• Option fields use ComboBox.
• Text and Decimal fields use TextBox though decimal fields have a numeric entry.
• Boolean fields use CheckBox.
• If you do not want the label to be shown but just want the value, then set Show Caption to false.
• If you do not want the field to be shown at all, then set Column Visible property to false.

The Application Designer example below uses the Editable Panel block while using the automatic saving abilities. To make use of the automatic saving, Save Table View filter must be set.

Business Central Code:

Device Columns:

Example Output:

The Application Designer example below uses the Editable Panel block and manually saves the results. Manual saving occurs because of not specifying Save Table View.

Business Central Code:

Device Columns:

Enter Quantity is used to prompt the user to enter quantity (typically for a selected document line). The block is tightly tied to Scan Behaviors as well as the menu standard action Change Qty.

Block Configuration:

When the block is executed, it references the Scan Behaviors to determine the default unit of measure, default quantities and whether to allow excess.

The block also relies on Configure Fields to determine maximum values and reference field information.

There are a few variables that can be created/set to help further override the dialog behavior:

When executed, users see a dialog like this:

After execution, the following variables are set:

The Application Designer example below uses Enter Quantity:

Show Assign LP is a special purpose block to handle when a user scans/assigns a license plate to a document. This block displays a dialog indicating the current document requirements against the license plate contents.

Block Configuration:

When executed, users see a dialog like below. Pressing OK triggers the event defined in Event ID to be fired and the appropriate assignment actions to be taken.

The Application Designer example below uses Show Assign LP:

Show LP List displays a list of license plates with some additional built in functionality for managing the license plates.

Block Configuration:

When executed, users see a dialog like this:

After execution, the following variables are set:

• dialog_result: 0 if Cancel is pressed, 1 if OK is pressed.
• action_result: The license plate number selected.

The Application Designer example below uses Show LP List. Only the Application Designer blocks are shown as it is sufficient to illustrate the inputs and outputs.

Show Picture block displays a dialog to the user with an image. The Dialog closes after a specified period unless explicitly forced to stay open by the user.

Block Configuration:

When executed, users see a dialog like this:

The Application Designer example below uses Show Picture:

Show Reservations is used to prompt display the item tracking lines for a selected line. The dialog allows adding, modifying and deleting tracking lines. The block is tied to Scan Behaviors as well as the menu standard action Change Qty and requires the Item Reservation events to be defined. The quantity dialog displayed when required is the same as Enter Quantity and provides largely the same features and overrides.

Block Configuration:

When executed, users see a dialog like this:

See the events After Item Reservation is Added, After Item Reservation is Changed, and After Item Reservation is Deleted for expected outputs.

The Application Designer example below uses Show Reservations. The example is based on a manual quantity change of a transfer shipment line.

Inspect Context displays a list of all the current available variables and their values. The variables are not limited to those that are specifically defined in the Application but include things like selected line data, barcode results, and device configuration.

The block is not intended for end user use but serves as a helpful block while designing applications.

When executed, users see a dialog like this:

The Application Designer example below uses Inspect Context: