Populate Controls in a UX Component with data from Tables
Populate the controls in a UX component with the data from Tables. (IMPORTANT: This action is intended for an event on a UX component).
Used with the UX component.
- Method for specifying primary key
- Primary key
Specify the primary key value of the record you want to use to populate the Dialog controls. If the primary key has multiple columns, enter the key value with 3 pipe characters (|||) separating the value for each column. For example, if the primary key is Firstname and Lastname, you could enter John|||Smith.
- Controls to read primary key from
Specify the control(s) on the Dialog that contain the primary key value for the record you want to retrieve
- Display debugging info
- Debugging information placeholder
Specify where debugging information should be shown. If you are working in an application that uses Panels, you will typically put a placeholder in the Panel to show debugging information in the appropriate panel. Set to <Default> for the default placement of debugging information.
- Error message placeholder
Specify where errors should be shown. If you are working in an application that uses Panels, you will typically put a placeholder in the Panel to show errors in the appropriate panel. Set to <Default> for the default placement of error information.
- Show wait message
Should a 'wait message' be shown while the callback to the server is executing?
- Wait message position
Specify where the wait message should be shown. 'page' puts the wait message over the entire screen. You can specify a specific Panel if you prefer. If you specify a specific Panel, be sure that the Panel is currently in view.
- Wait message text
(Optional) Specify the text message for the wait message. If you leave this blank a 'spinning icon' with no message is shown.
Creating a Button to Make a Callback to the Server and Populate the UX Component with Data for a Specified Record